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 6411 - MEX: no way to create metadata
Summary: MEX: no way to create metadata
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: MetadataExchange (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
Keywords: hasProposal
Depends on:
Reported: 2009-01-14 00:13 UTC by Doug Davis
Modified: 2009-10-13 22:46 UTC (History)
1 user (show)

See Also:


Description Doug Davis 2009-01-14 00:13:30 UTC
Using MEX and WS-Transfer a client can retrieve, manipulate and even 
delete the metadata of an endpoint.  However, there is no mechanism to 
create it.  This seems like a criticial piece missing from the complete 

Add the ability for a client to create metadata for an endpoint.
No concrete proposal yet but I can think of two possible solutions:

1 - define a CreateMetadata(dialect, identifier, data) type of operation 
in MEX that an endpoint can support.  This is probably the easiest.

2 - Merge T and MEX.  Yes this is much bigger than #1 but its something 
I've been wondering about for a while and would like to at least have a 
discussion of it.

If you think of the XML representation of a resource and its metadata as 
just "data about the resource", then it seems odd to force extra(or 
special) steps to be taken when dealing with metadata.  For example, to 
get the state of a resource you can just use T/RT to retrieve just that 
one chunk of XML. But to get part of the metadata of a resource you must 
use mex.GetMetadata() and then use T/RT to get the data of interest.  Why 
not just treat the metadata as another variant of the resource's data?  So 
the basic idea is to extend the Transfer operations with an optional 
'view' or 'dialect' attribute that specific which piece of data its 
operating on.  For example
   transfer.get() is what we have today - gets the xml represenation of 
the resource
   transfer.get("wsdl") retrieves the wsdl
   transfer.put("wsdl",data) creates/updates the wsdl of the resource
Comment 1 Robert Freund 2009-03-14 17:53:00 UTC
Comment 2 Doug Davis 2009-07-22 02:00:50 UTC

In MEX define a new operation:

<wsmex:CreateMetadata ...>
    xs:any *
  xs:any *

<wsmex:CreateMetadataResponse ...>
  xs:any *

This will add the specified metadata to the resource.  Note that the metadata
could be either the data itself or a reference to it.  If metadata with 
the same Dialect/ID combo already exists then it will be replaced.

Comment 3 Robert Freund 2009-08-13 11:48:14 UTC
Agreement on direction. Add operations to MEX to expose factory EPR so that TRANSFER optional operation may be used on the factory EPR to create/modify metadata.
Action on Doug to create proposal along these lines