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


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

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

Subject: Re: [chairs] Naming guidelines for comment


Check out RFC 3121.


   Date: Thu, 16 Sep 2004 18:28:06 +0100
   From: "Furniss, Peter" <Peter.Furniss@choreology.com>

   Bill (and others),

   Since the business transactions TC is just tidying up BTP 1.1, this was
   exactly what I needed to sort out what the namespace identification
   should be, so I've at long last looked at it.

   All fairly clear and good, but I don't quite understand the URN rules,
   which say the prefix is


   which, were we to use URNs for namespaces (which we probably won't),
   would give (for working draft, revision 2)


   I assume the ":" is the component separator applies to the parts,
   over-riding the rule about hyphens in 4.

   Why is {artifact} required ?  And, why force duplication of the TC name

   For some reason, the Business Transactions TC has a "short name" of
   "business-transaction" (at least, as in the URL for tc web-pages and
   mail archive). I assume the recommendation about internal hyphens
   becoming an underscore applies to all fields, and in all cases.

   For comparison, I believe the URL would be:


   but in this case, it will presumably be possible to put at least the cd
   and later schemas at that URL, so the duplication makes sense as the
   first occurrence will be a directory name. (http://docs.oasis-open.org
   is there, and returns a document containing a title and full stop)

   (I notice the guideline document itself doesn't have version or artifact
   in its identification)

   (BTP editor)

   Peter Furniss
   Chief Scientist, Choreology Ltd
   web: http://www.choreology.com
   email: peter.furniss@choreology.com
   phone: +44 870 739 0066
   mobile: +44 7951 536168

   > -----Original Message-----
   > From: William Cox [mailto:wtcox@comcast.net]
   > Sent: 23 July 2004 18:01
   > To: OASIS Chairs
   > Subject: [chairs] Naming guidelines for comment
   > Chairs --
   > The attached working draft,
   > oasis-tab-artifact_naming_guidelines-wd-06.doc, is for your comments.
   > The TAB Quality Subcommittee has broadened and evolved Eve
   > Maler's  18 
   > February 2003 "Proposed Rules for OASIS Document File Naming"  (at  
   > http://www.oasis-open.org/spectools/docs/chairs-filenaming-02.html ) 
   > which in turn was based on an email thread on the chairs list.
   > Comments are welcome, either on this list or directly to me
   > (wtcox@comcast.net) as the chair of the  TAB Quality Sumcommittee.
   > The TAB's goal is to move these guidelines forward in the
   > near future as 
   > the OASUS rules for artifact naming.
   > bill cox

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