[Bug 9031] New: MEX: Dialect is problematic

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9031

           Summary: MEX: Dialect is problematic
           Product: WS-Resource Access
           Version: LC
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: MetadataExchange
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org


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.


-- 
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 Tuesday, 16 February 2010 20:08:47 UTC