9031 2010-02-16 20:08:45 +0000 MEX: Dialect is problematic 2010-07-27 20:27:01 +0000 1 1 1 Unclassified WS-Resource Access MetadataExchange LC PC Windows XP CLOSED REMIND P2 normal --- 1 dug dug public-ws-resource-access-notifications oldest_to_newest 32204 0 dug 2010-02-16 20:08:45 +0000 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. 34158 1 bob 2010-03-30 19:50:24 +0000 resolved as proposed