[ebbp] Roberts 2/24/2004: Name for schemas [RSD] WI 7

["Monica J. Martin" <Monica.Martin@Sun.COM>]

Discussion|OASIS.ebBP.WI7-Versioning;
Topic|;
Attachment|http://www.oasis-open.org/archives/ebxml-bp/200402/msg00173.html;
Attachment|ftp://ftp.rfc-editor.org/in-notes/rfc3121.txt;
Attachment|http://www.oasis-open.org/committees/regrep/documents/2.5/schema/rim.xsd 
<http://www.oasis-open.org/committees/regrep/documents/2.5/schema/rim.xsd>;
Point|Namespace summary and recommendation;

mm1@
||Attachment: Martin - 
http://www.oasis-open.org/archives/ebxml-bp/200402/msg00173.html
||Attachment: RFC 3121 - ftp://ftp.rfc-editor.org/in-notes/rfc3121.txt
||Attachment: ebXML Registry uses OASIS URNs for namespaces: 
http://www.oasis-open.org/committees/regrep/documents/2.5/schema/rim.xsd

Martin,
We have two options for which I propose we open vote.  Unless any 
comment to the contrary is received, I will open a ballot on Saturday 
which allows notice to the TC on the Work Item 7.  I encourage the team 
to voice their comments this week prior to any vote so the vote verbiage 
can be crafted in line with the TC intent:

    * Use of an OASIS URN:
          o Reference
                + (a) RFC 3121
                  <ftp://ftp.rfc-editor.org/in-notes/rfc3121.txt> "A URN
                  Namespace for OASIS", targetNamespace for BPSS 2.0
                  schema will be: "urn:oasis:names:tc:ebxml-bp:bpss:2.0"
                + (b) ebXML Registry uses OASIS URNs for namespaces:
                  http://www.oasis-open.org/committees/regrep/documents/2.5/schema/rim.xsd
    * Use of URL in line with CPPA convention:
          o Example from Kenji Nagahashi:
            http://www.oasis-open.org/committees/ebxml-bp/schema/bp-2_0.xsd

As we think about this (and in line with Work Item 68 - Artifact 
versioning), we have these general requirements:

   1. To identify and make available key BPSS elements (in this case the
      schema or technical specification reference)
   2. To support the identification of the process description
      (specification)
   3. To support the identification of the computable process
      description (schema) [see (1) above]
   4. To support any alignment to the ebXML set of specifications [see
      my comment on use of URL with Kenji's example]

Vote notice: 24 Feb 2004
Vote open: 28 Feb 2004
Vote close: 6 March 2004

Fire away on comments folks. Monica

> Roberts:  It seems we are not going to get much from the general OASIS 
> community on this score. I feel unqualified to dictae the namespace so 
> if someone has strong views lets here them and we will settle it by a 
> simple vote ASAP.
>
@mm1