Re: XML InfoSet and property value preservation

Can you put out a proposal of which of the items you think clients should be
able to depend on the clients preserving?



On 11/16/05 10:42 AM, "Julian Reschke" <julian.reschke@gmx.de> wrote:

> 
> Jim Whitehead wrote:
>> 
>> 
>> Begin forwarded message:
>> 
>>> *From: *"Lukas Mathis" <lukas.mathis@numcom.com
>>> <mailto:lukas.mathis@numcom.com>>
>>> *Date: *November 15, 2005 11:53:39 PM PST
>>> *To: *<w3c-dist-auth-request@w3.org <mailto:w3c-dist-auth-request@w3.org>>
>>> *Subject: **RE: XML InfoSet and property value preservation*
>>> 
>>>> Extreme option:  All InfoSet items MUST be preserved.  [This clearly
>>>> has the disadvantage of making existing implementations change their
>>>> code to comply, but has the advantage of simplicity and enforcing the
>>>> greatest consistency between servers.]
>>> 
>>> Maybe I'm missing something, so I hope somebody can explain this to me:
>>> Are you arguing about whether a server should preserve data which has no
>>> specific semantic meaning (comments) or which could be changed to a
>>> semantic equivalent in XML (namespace prefixes)?
>>> 
>>> Maybe I don't understand the issue well enough to comment on it, but I'd
>>> tend to go with the last option - only require servers to preserve that
>>> which is really needed by clients.
> 
> Yes, sure. The trouble actually is to figure out what this is.
> 
> For instance, I do agree with you that comments do not need to be
> preserved, but I don't agree that namespace prefixes are irrelevant.
> 
> And of course there's the separate issue that we can't simply invent new
>   requirements without also thinking about how to get servers to quickly
> support these....
> 
> Best regards, Julian

Received on Wednesday, 16 November 2005 20:39:26 UTC