Fw: [opencsa-ms] Document URL structure

[Graham Barber <graham_barber@uk.ibm.com>]

Bryan

Thank you for raising this cross-TC
item which was considered by the Steering Committee and OASIS Staff at
the SC teleconference on October 5th.

The Steering Committee feel that the
most appropriate course of action would be for one of the Technical Committees
to propose a full and complete recommendation for endorsement. Once that
has been reviewed by OASIS Staff and the Steering Committee, the a Steering
Committee recommendation will be submitted to all SCA TCs for their final
decision.

Given that you raised the topic, can
I ask you please to put together a complete recommendation?

Graham J Barber,

OASIS Open CSA Steering Committee Secretary & Vice-Chair
Program Director, SOA Partnerships,
      Graham_Barber@uk.ibm.com
      Graham Barber@IBMGB
Phone:
Internal:                  
             245702,  External:
+44 (0)1962 815702
Secretary (Yulia):          247672,    
               +44 (0)1962 817672
Cellphone (Worldwide):              
                     +44
(0)7880 734005
----- Forwarded by Graham
Barber/UK/IBM on 06/10/2007 14:24 -----

Graham Barber/UK/IBM

05/10/2007 15:41

To	Bryan Aupperle <aupperle@us.ibm.com>
cc
Subject	Re: [opencsa-ms] Document URL structureLink

Bryan
        Action
item raised & will be on SC
Agenda today.

Graham J Barber,

Program Director, SOA Partnerships,
      Graham_Barber@uk.ibm.com
      Graham Barber@IBMGB
Phone:
Internal:                  
             245702,  External:
+44 (0)1962 815702
Secretary (Yulia):          247672,    
               +44 (0)1962 817672
Cellphone (Worldwide):              
                     +44
(0)7880 734005

Bryan Aupperle <aupperle@us.ibm.com>

05/10/2007 14:35

To	opencsa-ms@lists.oasis-open.org
cc
Subject	[opencsa-ms] Document URL structure

The OASIS template requires a that all specifications contain URLs  for
the current spec, previous spec, latest spec, and latest  approved
spec, however it doesn't specify a structure for the  location of
these documents, or how individual specifications  should be named.

From the template: http://docs.oasis-open.org/[tc-short-name]/[additional
path/filename].html for an html version of a document.   In the C-C++
TC, we have accepted an issue to define the additional  path and file
name.  However, it probably makes sense for all 6 TCs  to adopt
a common additional path structure and a consistent  document naming
convention.

For example do we want to have separate directories for working  drafts
vs. committee drafts, etc.?  Do we want to use draft dates  or
draft numbers in the file name?

A Steering Committee recommendation on this would be helpful and provide
some consistency across the TCs. 

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
Master Inventor

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

---

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU