I had not seen Chris' comments but I agree with some of them. He says: I think that using a sub-directory of the ebxml-msg and ebxml-cppa TC team's respective URLs is as good a scheme as any for our respective namespaces. which is good. I don't agree with making the namespace the same as the schema. We already have a versioning attribute and we don't need to do versioning with the namespace. The namespace needs to remain constant and let the schema name change as needed. Such a subdirectory would be one of:
http://oasis-open.org/committees/ebxml-msg/ http://oasis-open.org/committees/ebxml-msg/schema/ We should really use a different subdirectory for the schema and for services, with a common namespace root. IMO, unresolvable url references, such as .../NextMSH need to contain the namespace we designate to guarantee uniqueness. If we wanted to consolidate by using:
http://oasis-open.org/messageService/schema/draft-msg-header-03.xsd http://oasis-open.org/messageService/nextMSH http://oasis-open.org/messageService/ToPartyMSH then the namespace could be:
http://oasis-open.org/messageService or we could use the first namespace above and use:
http://oasis-open.org/committees/ebxml-msg/messageServices This subdirectory does not have to exist. All these options mean significant change and I would prefer not to do any of them. I view this as all jumbled now and I don't think it can be fixed. My preference is, at this point, to leave everything alone and just take the schema filename off the namespace. Regards, David Fischer Drummond Group.