This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 8295 - MEX: Dialect IRI's versus "selector IRI's
Summary: MEX: Dialect IRI's versus "selector IRI's
Status: CLOSED WONTFIX
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Gilbert Pilz
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords: hasProposal
Depends on:
Blocks:
 
Reported: 2009-11-14 02:37 UTC by Gilbert Pilz
Modified: 2010-01-27 14:12 UTC (History)
0 users

See Also:

Attachments

Description Gilbert Pilz 2009-11-14 02:37:00 UTC 
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".