- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 14 Nov 2009 02:37:01 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8295
Summary: Dialect IRI's versus "selector IRI's
Product: WS-Resource Access
Version: PR
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: MetadataExchange
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: gilbert.pilz@oracle.com
QAContact: public-ws-resource-access-notifications@w3.org
The "http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex-all" Dialect IRI will
never appear as the value of @Identifier in a mex:MetadataSection. It is
essentially a "selector IRI" that is only used in mex:GetMedata queries. The
fact that this IRI is lumped in with the normal Dialect IRI's is the source of
some confusion.
General Propsal 1: Define "Selector IRI's" as entities that are different from
Dilalect URI's and describe their use more accurately.
General Proposal 2: Eliminate the need for a special Selector IRI by defining
the mex:GetMetadata without a @Dialect value to mean "retrieve all metadata".
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Saturday, 14 November 2009 02:37:09 UTC