W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2001

RE: Issue: PROP_ATTR

From: Kevin Wiggen <wiggs@wiggenout.com>
Date: Mon, 16 Apr 2001 07:30:17 -0700
To: "Greg Stein" <gstein@lyra.org>, "WebDAV WG" <w3c-dist-auth@w3.org>
Message-ID: <ONEOJMKKAIDAGPLOPJEDIEJNCOAA.wiggs@wiggenout.com>
>> Maybe we need to collect all issues regarding this topic before going
back
>> to this one. For instance, if somebody would want to store an XSLT or an
XSD
>> schema as a property value, he probably would expect that namespace
prefix
>> information is preserved as well...

>They're SOL with (at least) mod_dav. It doesn't preserve prefixes. That is
>potentially another issue for the RFC 2518 issues list (I have an opinion,
>but that can occur under a separate issue thread).

DAV servers cannot preserve the namespace prefix.  What would happen if two
proppatch's told the same resource to store properties with the same
prefixes but differing namespaces?  When the server went to output info on a
propfind, it would not be consistent.

<d:prop xmlns:f="http://www.xythos.com/namespaces">
  <f:bar/>
</d:prop>

and

<d:prop xmlns:f="fdfd">
  <f:bar/>
</d:prop>

Kevin

-----Original Message-----
From: w3c-dist-auth-request@w3.org
[mailto:w3c-dist-auth-request@w3.org]On Behalf Of Greg Stein
Sent: Sunday, April 15, 2001 1:54 PM
To: WebDAV WG
Subject: Re: Issue: PROP_ATTR


On Sun, Apr 15, 2001 at 11:14:33AM +0200, Julian F. Reschke wrote:
>...
> As I said, both point of views are possible. However, your position seems
to
> be:
>
> value = Infoset of all child elements *plus* the optional xml:lang
attribute

Yes, because the xml:lang value is scoped, and the property value occurs
within that scope.

And this isn't just because xml:lang occurs on the property name element; it
could be three levels higher in scope.

> How do you put the value of xml:lang into the serialization of the
element's
> contents? Sure, that's again an implementation issue, but including the
> element itself certainly makes it easier.

Nope. It could occur higher in scope, so it might not be on the property
name element at all. Thus, serializing the name isn't going to help with
preserving the xml:lang value.

I store the xml:lang and the (serialized) value as two items of data in the
property database.

> > My point is that it is more difficult for server implementors if
> > you want to
> > state that the attributes on the name element are part of the property
> > value, and (thus) need to be stored.
>
> While my point is that it makes absolutely no difference at all :-)

As an implementor of a server, I would disagree :-)

I just want to see the language state something to the effect of: all
attributes on elements, which are children of the name element, MUST be
preserved; attributes on the name element MAY be preserved. [ plus the
language about xml:lang ]

> Maybe we need to collect all issues regarding this topic before going back
> to this one. For instance, if somebody would want to store an XSLT or an
XSD
> schema as a property value, he probably would expect that namespace prefix
> information is preserved as well...

They're SOL with (at least) mod_dav. It doesn't preserve prefixes. That is
potentially another issue for the RFC 2518 issues list (I have an opinion,
but that can occur under a separate issue thread).

Cheers,
-g

--
Greg Stein, http://www.lyra.org/
Received on Monday, 16 April 2001 10:30:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:56 GMT