- From: Javier Godoy <rjgodoy@fich.unl.edu.ar>
- Date: Mon, 11 Feb 2008 10:27:23 -0200
- To: "Julian Reschke" <julian.reschke@gmx.de>
- Cc: <www-webdav-dasl@w3.org>
Yes, it is an elegant solution because it is unambiguous and it is quite diffent from positional operand-* elements, making clear that it applies to the element as a whole. The new wording in section 5.19.8 seems OK for me. Note that text below the example in 5.19.9 should be modified. Currently it says "Of the optional DAV operators, DAV:is-defined and DAV:like are supported". DAV:contains was added in the latest revision. Besides, I think the attribute declaration in section 5.19.1 must include an attribute default, for conformance with W3C REC-xml-20060816 http://www.w3.org/TR/2006/REC-xml-20060816/#attdecls <!ATTLIST opdesc allow-pcdata (yes|no) "no" > Best Regards, Javier ----- Original Message ----- From: "Julian Reschke" <julian.reschke@gmx.de> To: "Javier Godoy" <rjgodoy@fich.unl.edu.ar> Cc: <www-webdav-dasl@w3.org> Sent: Monday, February 11, 2008 8:30 AM Subject: Re: QSD description for DAV:contains in DAV:basicsearchschema > > Ok... > > As a compromise about just stating that DAV:contains is an exception, and > adding a new *element* to QSD, what I have specified is an attribute on > opdesc. > > See > <http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html#rfc.issue.5.19.8-opdesc-vs-contains>. > Javier, is that ok for you? > > BR, Julian
Received on Monday, 11 February 2008 12:30:52 UTC