OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: ebBP 3/6/2006: ASIS Guidelines on Use of Hyphen (ebBP Impact)


As discussed in Tuesday's call, we have a document from OASIS for an 
Artifact Standard Identification Scheme.

================
Summary: The ASIS document [1] which may be mandated by the Board as 
OASIS Policy [4] uses a definition of tcShortName that requires hyphens 
to be removed [3]: ebxml-bp    --> ebxmlbp

It has been noted that the ASIS rule could cause OASIS IT, TC and user 
confusion. For ebBP, we have 'hyphen' tcShortName is already official, 
such as the TC page: http://www.oasis-open.org/committees/ebxml-bp/ and  
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-bp.

This is further complicated by the fact of adhering to the artifact 
naming guidelines previously published. ebBP has shortened the names to 
not only adhere as much as we understand of these guidelines but to 
other constraints (like file path limits and naming).  It has been a 
challenge to balance these guidelines in this case.

For example, we've:

   1. Shortened the core schema for ease of use: ebbp-2.0.2.xsd
   2. Shortened the conventions to accommodate file system restraints:
      ebxmlbp-v2.0.2-Document-cd-Supplements-en.zip (Originally longer
      but errors occurred as the file naming became longer by guideline
      requirement).

Note that both of these examples don't use hyphens.

It is to be determined if this guideline will be mandated or not 
(recommended not mandatory). However, we discussed Tuesday that it 
should likely be to the TC discretion whether to use or not to use 
hyphens. I encourage you comment to OASIS and Jamie Clark.  I'll do the 
same given our discussion.  Thanks.

===========
[1] Artifact Standard Identification Scheme for Metadata 1.0,  Approved 
TAB Document 30 January 2006 Artifact Identifier:   
ArtifactStandardIdentificationSchemeForMetadata-1.0.1-req-approved
See: 
http://www.oasis-open.org/committees/download.php/16546/ArtifactStandardIdentificationSchemeForMetadata-1.0.1.pdf

[2] Membership and Public Review of OASIS Artifact Standard  
Identification Scheme for Metadata - Notices:

     http://lists.oasis-open.org/archives/members/200602/msg00007.html
     http://lists.oasis-open.org/archives/tc-announce/200602/msg00005.html
     http://lists.oasis-open.org/archives/oasis-member-discuss/200602/msg00000.html

 Review comments: 
http://lists.oasis-open.org/archives/oasis-member-discuss/200602/msg00001.html
 Post comments to: oasis-member-discuss@lists.oasis-open.org

 [3]  Hyphenless TCShortName
 From the ASIS specification:
 Lines 334-336 from Section 3.2 Metadata Definitions (Normative)
 TC Short Name: "The short name assigned by the TC Administrator to the 
Technical Committee, with any hyphens eliminated."

 EBNF confirms that tcShortName may not contain hyphen:
 726  TCshortName = NAMECHAR, {NAMECHARPLUSUNDERSCORE | NAMECHAR};
 745  NAMECHAR = LOALPHA | HIALPHA | DIGIT;
 746  NAMECHARPLUSUNDERSCORE = NAMECHAR | UNDERSCORE
 * LOALPHA = [a-z], HIALPHA = [A-Z]; DIGIT = [0-9]

 Lines 634-640  Section 8.2 Technical Committee Tree
 "The short name of the OASIS technical committee, as established by the 
TC Administrator, typically upon initial formation, MUST be the next 
node in the URI after the base:  docs.oasis-open.org/ [tcShortName]

 [4] Memo from Jamie Clark to Chairs "Draft ASIS under review: mandatory 
policy? Please review and comment by 1 March"
 From James Bryce Clark <jamie.clark@oasis-open.org> on 18 Feb 2006 
http://lists.oasis-open.org/archives/chairs/200602/msg00037.html





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]