[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Namespaces
One of the outstanding items for this subteam was the resolution on namespaces. Here is what I'd like to suggest to the group to consider. One of the few registered formal URN Namespaces is "A URN Namespace for OASIS" (see [1]). It seems that its structure and semantics would be sufficient for our work. According to [1] ebXML namespaces would be under "names:tc:" hierarchy so they would start with urn:oasis:names:tc: A unique "tc-id" in our case, according to Karl Best, would be ebxml-regrep. Then the rest of it might look like: urn:oasis:names:tc:ebxml-regrep:registry:xsd:1.1 - this would be a Registry schema urn:oasis:names:tc:ebxml-regrep:services:wsdl:1.7 - this would be a Registry Services WSDL urn:oasis:names:tc:ebxml-regrep:soapbinding:wsdl:1.8 - this would be a Registry Services WSDL SOAP binding [1] http://lists.research.netsol.com/pipermail/urn-nid/2001-January/000120.html Regards, Nikola Stojanovic Lead Technologist, Research and Development Encoda Systems Inc. 101 Pineview Terrace Ithaca, NY 14850 USA nikola.stojanovic@encodasystems.com Tel: 607-273-2224
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC