Yep - I would create a new folder. Note that folders are displayed in
alphabetical order with subfolders listed directly below their parent
Thus, to keep the folders in an order that made sense (to me :-)) with
V2.0 at the top, I added a prefix consisting of "letter.number:". The
letter was associated with the version, where "A" is for V2.0, "X" is
for V1.1, "Y" is for V1.0, and "Z" is for temporary stuff. The intent
was that if we did a V2.1 or V3.0, then we sould simply rename the
current "A" folders to "W" and create new ones with "A".
So, "A.0:" currently holds the V2.0 OASIS Standard docs/schemas, "A.1"
is used for outreach documents, "A.2" is post-v2.0 committee
drafts/committee specs, and "A.3" is post V2.0 working documents. "A.4"
is the various committee drafts leading up to the V2.0 OS, etc. A.9 is
for pre-2.0 working documents.
Since we're not doing a new version, I recommend just sliding the A.1
thru A.4 names down by renaming them to bump up their numbers and
inserting a new "A.1" for Post-V2.0 OASIS Standard Specifications".
I will take care of that unless someone objects very quickly...
RSA, the Security Division of EMC
Senior Technologist | e-Mail: rphi...@rsa.com | Office: +1
781-515-7115 | Mobile: +1 617-510-0893
From: Scott Cantor [mailto:cant...@osu.edu]
Sent: Tuesday, November 06, 2007 12:51 PM
To: 'OASIS SSTC'
Subject: [security-services] Uploading OS packages
The edits are minimal but I'm not sure where to upload the OS versions
the two specs. It looks like Rob created the original folder
final 2.0 specs, but it's locked to me, and these would probably need
2.0 standard folder anyway.