RE: XML valued datatypes

MessageActually,

defining a single XPath-based operator probably *would* suffice (we'd still
need to find out how this affects result sorting, though). However I agree
with Alan that we should leave this out of the spec for now.

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

  -----Original Message-----
  From: Babich, Alan [mailto:ABabich@filenet.com]
  Sent: Tuesday, October 07, 2003 6:57 PM
  To: Wallmer, Martin; Julian Reschke; www-webdav-dasl@w3.org
  Subject: RE: XML valued datatypes


  Martin,

  Querying XML documents is a much bigger deal than inventing an optional
operator. There is a whole working group for XML query. Please review what
they have done.

  Alan Babich
    -----Original Message-----
    From: Wallmer, Martin [mailto:Martin.Wallmer@softwareag.com]
    Sent: Tuesday, October 07, 2003 3:29 AM
    To: 'Julian Reschke'; Wallmer, Martin; www-webdav-dasl@w3.org
    Subject: RE: XML valued datatypes


    So lets make it an optional operator

    Regards,
    Martin
      -----Original Message-----
      From: Julian Reschke [mailto:julian.reschke@gmx.de]
      Sent: Dienstag, 7. Oktober 2003 11:48
      To: Wallmer, Martin; www-webdav-dasl@w3.org
      Subject: RE: XML valued datatypes


      Martin,

      the simple answer is that DAV:basicsearch doesn't support queries on
properties that do not have a text content model. See
http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html#non
-simple-types. So a server MUST NOT attempt to match in this case.

      So yes, a new operator that does XPath-based matching on a property
value may make a lot of sense, but of course it can't become a required
operator for DAV:basicsearch.

      Julian


      --
      <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

        -----Original Message-----
        From: www-webdav-dasl-request@w3.org
[mailto:www-webdav-dasl-request@w3.org]On Behalf Of Wallmer, Martin
        Sent: Tuesday, October 07, 2003 11:20 AM
        To: www-webdav-dasl@w3.org
        Subject: XML valued datatypes


        Hi,

        when we're talking about datatypes, what about xml value'd
properties?

        Example:

        You have two resources, one you PROPPATCHed with:

        <?xml version="1.0" encoding="utf-8"?>
        <D:propertyupdate xmlns:D="DAV:">
          <D:set>
            <D:prop xmlns:Z="http://www.w3.com/standards/z39.50">
              <Z:authors>
                <Z:Author>Jim Whitehead</Z:Author>
                <Z:Author>Roy Fielding</Z:Author>
                <Z:Co-author>Lieschen Mueller</Z:Co-author>
              </Z:authors>
            </D:prop>
          </D:set>
        </D:propertyupdate>

        the second with

        <?xml version="1.0" encoding="utf-8"?>
        <D:propertyupdate xmlns:D="DAV:">
          <D:set>
            <D:prop xmlns:Z="http://www.w3.com/standards/z39.50">
              <Z:authors>
                <Z:Author>Lieschen Mueller</Z:Author>
              </Z:authors>
            </D:prop>
          </D:set>
        </D:propertyupdate>

        How to find all resources, where Lieschen Mueller was author, not
Co-author? Currently you have to define something like:

        <like>
          <prop>
            <Z:authors/>
          </prop>
          <literal>%Lieschen Mueller%</literal>
        </like>

        but of course you will find both resources. Relying on formatting
won't work. So what about something like:

        <xpath>
          <prop>
            <Z:authors/>
          </prop>
          <literal>[Z:author="Lieschen Mueller"]</literal>
        </xpath>

        or finding all resources, where a Co-author is defined:

        <xpath-is-defined>
          <prop>
            <Z:authors/>
          </prop>
          <literal>./Z:Co-author</literal>
        </xpath-is-defined>

        where the literal is an xpath expression relative to the property
(root element).

        Regards,
        Martin

        __________________________
        Martin Wallmer
        Research & Development
        Software AG    ++49 6151 92 1831
        Uhlandstr. 12
        D 64297 Darmstadt