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


From: Jim Amsden <jamsden@us.ibm.com>
Date: Fri, 13 Apr 2001 16:30:28 -0400
To: w3c-dist-auth@w3c.org
Message-ID: <OFFFDEB218.048432A9-ON85256A2D.0070760C@raleigh.ibm.com>
I think the usual XML rules should apply. That is, namespace attributes on
the DAV:prop element get applied by default to the value unless the value
provides its own. Clients have complete control of this if it the default
isn't what they want. Servers should be uninvolved in determining semantics
other than following XML rules.

                    Crawford"            To:     "Kevin Wiggen" <wiggs@wiggenout.com>                        
                    <ccjason@us.ib       cc:     "WebDAV WG" <w3c-dist-auth@w3.org>                          
                    m.com>               Subject:     RE: Issue: PROP_ATTR                                   
                    03:28 PM                                                                                 

  <theprop attr1="foo"/>
  <theprop attr1="bar"/>
  <theprop attr2="fee"/>
I agree that this is not acceptable unless attr1 and attr2 are namespace
attributes that alter the effective tag name of the property name tags.

This does lead me to another question though.  If in the PROPPATCH call
there are xmlns attributes on the propertyupdate, set, or prop tags that
could potentially affect the tags within the property value, is the server
responsible for collecting those and representing those in PROPPATCH
responses?   Or should we require that the client put any xmlns attributes
that it cares about on the propertyname tag and within?

Received on Friday, 13 April 2001 16:43:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:22 UTC