Bug 9031 - MEX: Dialect is problematic
: MEX: Dialect is problematic
Status: CLOSED REMIND
Product: WS-Resource Access
MetadataExchange
: LC
: PC Windows XP
: P2 normal
: ---
Assigned To: Doug Davis
: notifications mailing list for WS Resource Access
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2010-02-16 20:08 UTC by Doug Davis
Modified: 2010-07-27 20:27 UTC (History)
0 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug Davis 2010-02-16 20:08:45 UTC
The Dialect isn't composible, extensible and is problematic.

Right now each piece of metadata is required to create a new Dialect URI
so that the Dialect value can uniquely identify that piece of metadata.
This is problematic for a couple of reasons:

1 - it forces each new metadata creator to take MEX into account and create
a unique URI for each type of metadata.  This obviously doesn't work for
existing metadata types, nor is it appropriate to force people to create
a special URI just so that MEX can work.

2 - given that metadata creators may not do this, it will then require some
3rd party to be the keeper of mex Dialect URIs.  Who will
take on this role?  How will we ever have interop w/o this overlord?  :-)

This really is very similar to the problem we saw with @mode in ws-eventing.

Proposal:
Change Dialect to be a QName rather than a URI and have it be the root QName
of the metadata.

This obviously will uniquely identify the metadata type in question and it 
doesn't require the creation of a unique URI to go along with it 
(thus no overlord is needed).

This will also remove the need for MEX to define 
Dialect IRI/MetadataFormat table in section 5 - so it can be removed.
Comment 1 Robert Freund 2010-03-30 19:50:24 UTC
resolved as proposed


  翻译: