Lists Home |
Date Index |
- From: Sean Mc Grath <email@example.com>
- To: firstname.lastname@example.org
- Date: Tue, 26 Aug 1997 14:08:57 +0100
>>Sean Mc Grath
>> >On Mon, 25 Aug 1997, Sean Mc Grath wrote:
>> >> User A : "What file format is that?"
>> >> User B : "It's MicroScape XML."
>> >> User A : "I better buy a copy of MicroScape so - otherwise the white space
>> >> will get busted again".
>> [Liam Quin]
>> >If this happens, it wlil be time to standardise whitespace handling at the
>> >applicaton level, perhaps. Right now, I fnd this argument totally bogus.
>> What are you saying? Lets wait and see if the horse bolts - if he
>> does we will lock the barn door?
>> Sean Mc Grath
>I agree with you totally. The horse will bolt, for certain. I want to
>be able to use XML editor A, and allow people to view the
>output on browser B and C, publish it on DTP system D,
>send the data to someone else using editor E,
>and let people search for pseude-elements using extended pointers
>in products E and F, and all without extra spaces appearing or
>vital spaces disappearing at any point.
[Lots of v. good points about WS elided]
Is this a fair summary of the position then? :-
1) WS handling is an application convention - not part of the XML standard
2) Different applicatioms are free to have different conventions
3) There is a generally agreed need to work out some conventions/idioms
a) They will give app. developers a leg up on a potentially
b) They will hopefully contain the "distilled essense" of the WS
c) They will give tools purchasers a stick with which to beat
vendors IFF divigations
from the conventions prove troublesome. I.e. "does your XML tool
support the Bradley
conventions for white space handling...?"
If so. Lets go for it. How about we concentrate in the first instance on
of straight XML editing tools?
xml-dev: A list for W3C XML Developers
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To unsubscribe, send to email@example.com the following message;
List coordinator, Henry Rzepa (firstname.lastname@example.org)