[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ebxml-cppa] FW: How is Registry using OASIS NID
Dale: Please see my comments inline (bracketed by <arvola> </arvola>). -Arvola -----Original Message----- From: Dale Moberg [mailto:dmoberg@cyclonecommerce.com] Sent: Tuesday, February 26, 2002 10:31 AM To: ebxml-cppa@lists.oasis-open.org Cc: Nikola.Stojanovic@encodasystems.com Subject: [ebxml-cppa] FW: How is Registry using OASIS NID Hi, I am forwarding Nikola's message to the CPPA list discussing Registry's use of URNs for their namespace's identifying URI. Please comment on this if you think our TC should log an issue concerning namespace URI identification and schema location conventions. Since Messaging is using a resolvable URL for their URI, we have different conventions being used for namespace identification and schemaLocation within OASIS ebXML groups. (I believe that Messaging has just removed the "schemaLocation" discussion from their specification 2.0c also. So that would be another difference from what Registry has done, and what we now do.) <arvola> The 2.0c version still has the schemaLocation attribute section and in the examples because David wanted to respect the wishes of participants in the interop trials not to have to change their software. </arvola> It is not clear to me that there is any "issue" to be resolved because both Messaging and Registry make use of permitted conventions and use syntactially allowed values. I think this is probably the case with what we have currently done also. <arvola> I have previously brought up as an issue to the MSG team about using a URN based namespace in order to align with the registry team. The decision was in favor of using a namespace URI that is resolvable. Since I am maintaining the schema for both MSG and CPP/A, a common approach is used for naming the MSG and CPP/A namespaces. </arvola> Here are some assumptions I am laboring under: 1. The namespace URI can be a resolvable URI or an unresolvable URI; no standard mandates its use as a place to find a schema, or, more specifically, a w3c schema. So URNs can be used. But so can resolvable URLs, that resolve (by HTTP GET) to a schema. 2. In practice, when a namespace begins with "http://" it is often treated as resolvable, and also to a w3c style schema. Some have argued that this is neither Best Current Practice, and should be replaced by entirely new approaches. See, for example, http://www.openhealth.org/RDDL/ and an abundance of traffic archived at xml.com. But there is no clear verdict or consensus about these dissatisfactions and proposals that I can discern. 3. The schemaLocation attribute does not have to be used, and it is not the definitive resolvable URI for a w3c schema. CPPA uses it, but schemaLocation has the same value as the URI for the namespace. See the section in the XML schema spec (structures) on "Schema Representation Constraint: Schema Document Location Strategy" to see what is definitely specified about how to specify schema document location :-) <arvola> Since CPP/A is using a namespace URI that resolves to the appropriate schema, I don't think there is a real need for section 8.2 (schemaLocation Attribute) in the CPP/A spec. On the other hand, if we remove this section, subsequent section numbers will change and cause havoc to the hard coded section references that have not been turned into symbolic references. In particular, I think the CPA composition appendix have not been converted to use symbolic section references. </arvola> -----Original Message----- From: Nikola Stojanovic [mailto:Nikola.Stojanovic@encodasystems.com] Sent: Wednesday, February 20, 2002 12:27 PM To: Dale Moberg Subject: How is Registry using OASIS NID Dale, Here is the pointer re Karl's msg re OASIS NID http://lists.oasis-open.org/archives/regrep/200112/msg00063.html If you look at one of our schema http://www.oasis-open.org/committees/regrep/documents/2.0/schema/query.x sd you'll see that we've used OASIS URN syntax for namespaces. In addition to that, we've used schemaLocation to act as a hint where the schema can be found. <snip> <schema xmlns = "http://www.w3.org/2001/XMLSchema" targetNamespace = "urn:oasis:names:tc:ebxml-regrep:query:xsd:2.0" xmlns:tns = "urn:oasis:names:tc:ebxml-regrep:query:xsd:2.0" xmlns:rim = "urn:oasis:names:tc:ebxml-regrep:rim:xsd:2.0"> <!-- Import the rim.xsd file with XML schema mappaing from RIM --> <import namespace = "urn:oasis:names:tc:ebxml-regrep:rim:xsd:2.0" schemaLocation = "http://www.oasis-open.org/committees/regrep/documents/2.0/schema/rim.xs d"/> </snip> Nikola Stojanovic Architect, Architecture and Standards Encoda Systems, Inc. 101 Pineview Terrace Ithaca, NY 14850 USA nikola.stojanovic@encodasystems.com Tel: 607-273-2224 "The information in this e-mail is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized. If you are not the intended recipient, or believe that you have received this communication in error, please do not print, copy, retransmit, disseminate, or otherwise use the information. Also, please indicate to the sender that you have received this e-mail in error, and delete the copy you received. Thank you." ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC