• To: Elliotte Rusty Harold <elharo@m...>, xml-dev <xml-dev@l...>
• Subject: Re: malfunctioning, evil adult as XML
• From: "Emmanuil Batsis (Manos)" <mbatsis@n...>
• Date: Sat, 01 Feb 2003 00:17:24 +0200
• In-reply-to: <p04330109ba603601fa5e@[192.168.254.4]>
• References: <9B9A5456AFE99E4181416B252F63BDA207C4BBDA@r... t.com> <001b01c2c925$0cbe3480$a800a8c0@SeairthA31> <3E3A719D.9030508@n...> <p04330104ba602536082a@[192.168.254.4]> <3E3A8005.5020502@n...> <p04330109ba603601fa5e@[192.168.254.4]>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130

Elliotte Rusty Harold wrote:

> Ultimately, it's only the text that counts, not whatever your local 
> process does or what API it uses. I only care about the text document 
> that comes in and the text document that goes out. Everything in between 
> is your business, not mine. However, if your business starts changing 
> the text documents that go in out in unepxxected ways that violate XML, 
> then I get worried.

I don't see how XML can get violated by what I suggested. In the case 
you imply where the XML is for consumption by multiple entities, there 
must be some agreement in the form of a schema anyway. What I suggest is 
a flexible model that does not break XML 1.0 and can be agreed upon. No 
reason to worry... just expect a simple type in the form of either an 
element or an attribute; but a simple type is just that.

No need to worry.

Manos

• References:
  • Re: malfunctioning, evil adult as XML
    • From: "Seairth Jacobs" <seairth@s...>
  • Re: malfunctioning, evil adult as XML
    • From: "m batsis" <mbatsis@n...>
  • Re: malfunctioning, evil adult as XML
    • From: Elliotte Rusty Harold <elharo@m...>

• Prev by Date: Re: Elliotte Rusty Harold on Web Services
• Next by Date: Re: SAX Parser and Attribute Normalization
• Previous by thread: Re: malfunctioning, evil adult as XML
• Next by thread: RE: malfunctioning, evil adult as XML
• Index(es):
  • Date
  • Thread