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


Help: OASIS Mailing Lists Help | MarkMail Help

xri-editors message

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

Subject: RE: [xri-editors] PLEASE PROOF: [xri-editors] Groups - xri-syntax-resolution-1.0-cd-PROOF.doc

We had this very question about the vote - whether any final editorial
changes (including things as simple as typo corrections) could be made
by the editors after the vote or not. We specifically worded the ballot
to allow that but it sounds like that may not be kosher with OASIS
I agree with Gabe, and have already talked with the Chair of the XRI
Editor's SC, Dave McAlpin, who also agrees that we'll just do another
But we still need our OASIS reference questions answered so we can lock
the document for the vote. I note that we looked at the TC Process
documents for guidance about Committee Drafts in this respect and didn't
find anything about this subject of final changes at all, even though
based on our experience this must be a scenario every TC goes through.
Can I suggest that OASIS produce a document that specifically addresses
the process for producing a finished Committee Draft? Questions
addressed in this document should include:
* Naming conventions, and how to deal with them up until the FINAL "cd"
* Errata document references (specifically, the questions in the email I
sent on 12/23 to Karl about how to include a reference to this doc when
one doesn't exist yet).
* How to handle references to other related TC documents (such as a
primer, or conformance specs, or other related specs) esp. when they are
planned and not actual yet.
* How to handle Acknowledgements.
* How to handle Revision History (what levels of changes to record and
* How/when to obtain an OASIS persistent identifier for the document.
* How/when/if to publish the spec in multiple formats (Word, PDF, HTML,
* Who to notify about the vote, the posting, etc.
* How and when to get a link to the final spec added to the TC home
Like the final finishing details on a new house, the process of
finishing a Committee Draft is actually much more difficult and labor
intensive than it looks. It would really help to have a guidance
document devoted just to this step (and potentially including all the
subsequent document processing steps to advance to an OASIS Standard).
Thanks for your help,
-----Original Message-----
From: Wachob, Gabe [mailto:gwachob@visa.com]
Sent: Monday, December 29, 2003 3:09 PM
To: 'James Bryce Clark'; Drummond Reed; loren.west@epok.net;
Cc: xri-editors@lists.oasis-open.org; karl.best@oasis-open.org
Subject: RE: [xri-editors] PLEASE PROOF: [xri-editors] Groups -
I'm pretty sure we've notified Karl about the vote. 
As for post-vote changes, I spose we should in fact have another vote,
but it will be a formality. I think we need to wait until after this
week to initiate that vote. In fact, I don't think we've yet published
any post-vote document. There was some confusion about whether editorial
changes (such as typos, etc) would trigger a revote, but it turns out, I
think we may have gone slightly beyond those sort of changes.
Also, I think Drummond had some outstanding technical issues about the
self-reference in the document (ideally something other than a big long
URL with document.php in the middle of it, for example). 
Anyway, it may be easiest just to hold another vote at this point after
all of Drummond's questions get answered.
 -----Original Message-----
From: James Bryce Clark [mailto:jamie.clark@oasis-open.org]
Sent: Monday, December 29, 2003 2:37 PM
To: drummond.reed@onename.com; loren.west@epok.net;
Cc: xri-editors@lists.oasis-open.org; karl.best@oasis-open.org
Subject: Re: [xri-editors] PLEASE PROOF: [xri-editors] Groups -
    Hello all and Happy New Year.  I have a couple of queries regarding
the status of the currently-underway XRI committee draft.  If you
already have covered these with Karl, that's fine, but he's away this
week and I'm unaware of the resolutions;  so if not, let's confirm with
him early next week.
    I see from Gabe's 8 December message below (#1) that you may have
conducted an approval vote on a committee draft.  If so, please be sure
to formally notify either Karl or me, as required by Section 3(a) of the
OASIS TC Process rules.  I will be happy to include the spec in our
public registry of completed works but can't do so until that step has
been taken.
    I am also concerned about the suggestion that an approved draft
might be further edited, in Drummond's 21 December message below (#2).
OASIS practice is to freeze changes when a work is put up for vote, and
not to permit changes thereafter except by formal process (e.g., another
vote resulting in a new version) or distinct errata (also requiring a
vote).  Obviously this is to preserve intact the version as a record of
what the TC actually approved.   So it is possible that any post-vote
changes may need a vote and a version number change.  
    Congratulations in any case on successfully completing the work.
I'm sure the formalities will not prove to be an obstacle of any
significance.  If there are any questions, let's discuss early next week
once everyone's back from holiday.  If there's more to this than I know
or some urgency for resolving this sooner, please feel free to advise.  
    Regards  Jamie  


From: "Wachob, Gabe" <gwachob@visa.com>
To: "'xri@lists.oasis-open.org'" <xri@lists.oasis-open.org>
Date: Mon, 8 Dec 2003 10:01:13 -0800 
Subject: [xri] Unanimous approval of RC2

TC Members-
    The XRI Syntax and Resolution Specification RC2 has been unanimously
approved as a committee specification.
    We expect errata and other minor changes to be made after
implementation effforts begin (there is at least one open source effort
that we know of). 
    I'd like to congratulate the TC and especially the editors for
making this specification happen! We still have some work upcoming
though: metadata specification, secure resolution specification, and
incorporating feedback from implementation (as noted above). 
    The mechanics of how RC2 is published as the official committee spec
is being worked on now. We plan on taking this to the whole of Oasis as
an Oasis-approved spec after some implementation is done and feedback is

At 10:21 PM 12/21/2003, Drummond Reed wrote:

Editors (and Loren, since he suggested some of the relevant changes):

Dave is on vacation this week so he handed me the final 1.0 spec to
prepare for final posting. We were aiming for last Friday but we made
enough changes (8 total, including one minor error in the ABNF for Query
and Fragment that I caught) that we wanted to have other editors and
Loren review our work before final posting tomorrow.

I just uploaded the proposed 1.0 document to the Editor's TC (see link
below). Note that the date reads 12/23/2003 because that's when I plan
to post it. J

Just open the Comments window to review the changes. In additon to the 8
edits, there are still two outstanding questions. The first one is
simply a procedural question for OASIS about the errata doc. The other
one is a clarification needed - primarily from Gabe - about a sentence
in section 3.7.

Loren, please review the XRI Descriptor XML schema to make sure you are
happy with the new element names.

Please post a note to the Editor's list once you have reviewed these
edits/questions (Loren, you can just send me mail directly). Then I'll
post the final final by the end of the day on Tuesday to wrap up our XRI
TC work for 2003.


-----Original Message-----

From: Drummond Reed 
Sent: Sunday, December 21, 2003 10:27 PM
To: xri-editors@lists.oasis-open.org
Subject: [xri-editors] Groups - xri-syntax-resolution-1.0-cd-PROOF.doc

The document xri-syntax-resolution-1.0-cd-PROOF.doc has been submitted
by Drummond Reed (drummond.reed@onename.com) to the XRI Editors SC
document repository.

Document Description:
Final proof draft of 1.0 spec, ready for publication (with two
outstanding questions). See separate email for summary of comments.

Download Document: 

View Document Details:

PLEASE NOTE:  If the above links do not work for you, your email
application may be breaking the link into two pieces.  You may be able
to copy and paste the entire link address into the address field of your
web browser.

To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
workgroup.php> .

To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to
workgroup.php> .

~   James Bryce Clark
~   Manager Tech Stds Dev, OASIS
~   +1 978 667 5115 x 203 central office
~   +1 310 293 6739 direct 
To unsubscribe from this mailing list (and be removed from the roster of
the OASIS TC), go to

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