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 12093 - MEX: PutMetadata and dialects/types that don't define identifiers
Summary: MEX: PutMetadata and dialects/types that don't define identifiers
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: CR
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2011-02-16 05:20 UTC by Gilbert Pilz
Modified: 2011-09-13 21:35 UTC (History)
1 user (show)

See Also:

concrete proposal (353.00 KB, application/msword)
2011-03-02 19:20 UTC, Doug Davis

Description Gilbert Pilz 2011-02-16 05:20:45 UTC
The following is currently true in MEX:

1.) Metadata dialects/types are not required to define a "identifier". For example, there could be a dialect/type of {}foo (to use the new serialization) that does not define an "identifier"; there is no single element or attribute value in a "foo" document that makes any different from any other "foo" document.

2.) @Identifier is an optional attribute of mex:PutMetadata/mex:Metadata/mex:MetadataSection.

3.) Services that implement MEX are not required to understand all the metadata dialects/types that they are asked to manage.

So what happens a client does a PutMetadata with one or more MetadataSections that have no @Identifier (whether this is because the contained metadata does not define an identifier or the client simply decided to omit the @Identifier, the service can't tell - see (3)), then someone else comes along and does a GetMetadata with @Dialect="{}foo" and @Identifier=""? Do hunks of metatdata that were Put with no identifier match against all identifier queries or none? There are use cases to support either answer to that question.
Comment 1 Doug Davis 2011-02-16 14:07:55 UTC
- make @Identifier a required attribute of mex:MetadataSection
- if a metadata type does not have any useful data to use as the @Identifier
  value then it MUST use "" for the value
- keep @Identifier optional on the mex:GetMetadata operation
- mex:GetMetadata w/o @Identifier (not "") means match ALL @Identifiers
Comment 2 Robert Freund 2011-03-01 21:13:52 UTC
directional agreement on comment 1 with the second bullet needing work
Comment 3 Doug Davis 2011-03-02 19:20:27 UTC
Created attachment 963 [details]
concrete proposal
Comment 4 Robert Freund 2011-03-22 19:44:20 UTC
resolved as proposed in comment 3