W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > February 2009

Issue 6604 - a proposal

From: Doug Davis <dug@us.ibm.com>
Date: Sat, 28 Feb 2009 10:16:45 -0500
To: public-ws-resource-access@w3.org
Message-ID: <OF79322E03.B19167D8-ON8525756B.0053DEEF-8525756B.0053F053@us.ibm.com>
(copy from issue)
Current form:
  <mex:GetMetadata ... >
    (<mex:Dialect>xs:anyURI</mex:Dialect>
       (<mex:Identifier>xs:anyURI</mex:Identifier>)?
    )?
    <mex:Content> xs:anyURI </mex:Content> *
  </mex:GetMetadata>

Proposal:
 <mex:GetMetadata ... >
   <mex:Dialect uri="xs:anyURI" 
                identifier="xs:anyURI"? 
                Content="xs:anyURI"? .../> *
   ...
 </mex:GetMetadata>

This gives you the flexibility of choosing different formats on a per 
Dialect
basis.  What's nice about this is that since we've defined the "all" 
Content
URI, you could ask for all forms of a certain metadata with a single 
element. 
However, if you want just 2 of the forms (e.g. URI and EPR) then you'll 
need to
use 2 elements.  Not a huge issue and I'm not sure one that will happen 
too
often.  It seems that if you want a reference to the data you'll probably 
plan
on only using one way to retrieve it - not both.

We could make the Content attribute a list of URIs, but that seems overly
complicated when adding a new Dialect element gives you the same end 
result
with only a few more bytes on the wire.


thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@us.ibm.com
Received on Saturday, 28 February 2009 15:17:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:17:45 GMT