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

[Bug 6405] WS-MEX - add the ability for a client to specify the format of the returned data

From: <bugzilla@wiggum.w3.org>
Date: Thu, 15 Jan 2009 23:36:49 +0000
To: public-ws-resource-access-notifications@w3.org
Message-Id: <E1LNblZ-0003dX-Jk@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6405





--- Comment #3 from Robert Freund <bob@freunds.com>  2009-01-15 23:36:49 ---
Edited from
http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jan/0040.html
Per our talks yesterday.... here's the new pseudo schema:

  <mex:GetMetadata ?>
    (<mex:Dialect>xs:anyURI</mex:Dialect>
      (<mex:Identifier>xs:anyURI</mex:Identifier>)?
    )?
    (<mex:Content> xs:anyURI </mex:Content>)*
  </mex:GetMetadata>

And the proposed set of changes are:
- define the default, when the mex:Content element is missing, as 'any'
- define a new URI for 'any' so people can be explicit if they want
- define a new URI for 'all' - meaning send back all metadata that is 
allowed to be sent back
- clarify that 'skip' means that if a service is unable to send back the 
requested content then no metadata section will be sent back for that content.

When not present the default is as current defined - up to the service to 
decide which (and how many) to return. We then need to define 5 URIs for 
each of the formats - eg:
        http://.../mex/content/EPR
        http://.../mex/content/URI
        http://.../mex/content/metadata
        http://.../mex/content/any
        http://.../mex/content/all


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 15 January 2009 23:50:12 GMT

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