Re: [security-services] FW: [chairs] Updating SpecificationStatus after ballots

I'll admit that I don't fully understand all this or what the implications
to us are.  However, I don't believe that we have any "Designated
Cross-Reference Changes" so best I can tell, this just means less work for
editors.  But, like I said, I don't really know so it probably does warrant
a little discussion on the call tomorrow.  If there's confusion, we can ask
for clarification from Mary.

On 5/19/08 5:54 PM, "Tom Scavo" <> wrote:

> Brian, the attached note is the first reference to "Designated
> Cross-Reference Change" I've seen or heard.
> 
> http://www.oasis-open.org/committees/process.php#crossRefs
> 
> It's rather complicated...does this warrant discussion on tomorrow's call?
> 
> Thanks,
> Tom
> 
> On Mon, May 19, 2008 at 6:27 PM, Brian Campbell
> <> wrote:
>> Though you may already be aware, I thought I should pass this along for the
>> benefit of our many spec editors.
>> 
>> ------ Forwarded Message
>> From: Mary McRae <>
>> Date: Mon, 12 May 2008 09:13:02 -0400 (EDT)
>> To: <>
>> Subject: [chairs] Updating Specification Status after ballots
>> 
>> To TC Chairs, Secretaries and Editors:
>> 
>> After a document has gone through and passed a Public Review, Committee
>> Specification or OASIS Standard ballot, the specification must be updated
>> to note the proper metadata on the title page and running footers. In the
>> past, I have asked the TCs to prepare these new versions. This often leads
>> to multiple iterations and as a result, delays the official posting of the
>> specification itself.
>> 
>> The vast majority of members are not publication specialists, and the
>> manipulation of styles and hyperlinks in word processing documents can be
>> tricky. Effective immediately, I will make the requisite modifications to
>> each of the supplied versions (editable source, HTML and PDF) unless the
>> TC has a ³Designated Cross-Reference Change² included in their
>> specifications. By editing each of the files no additional conversions
>> will take place.
>> 
>> Those TCs that have a ³Designated Cross-Reference Change² included in
>> their specification will still be asked to supply the updated versions of
>> the specification.
>> 
>> As a reminder, a checklist is available to help ensure your specification
>> meets the OASIS requirements. Completing the checklist prior to sending
>> your specification to the TC Administrator for action will cut down on
>> turnaround time and eliminate extra cycles.
>> http://docs.oasis-open.org/templates/QAChecklistV2.html
>> 
>> As always, please feel free to contact me should you have any questions,
>> comments or concerns.
>> 
>> Regards,
>> 
>> Mary
>> 
>> 
>> 
>> -----------------------------------
>> Mary P McRae
>> Manager of TC Administration, OASIS
>> email: 
>> web: www.oasis-open.org
>> phone: 603.232.9090
>> 
>> 
>> 
>> ------ End of Forwarded Message
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe from this mail list, you must leave the OASIS TC that
>> generates this mail.  You may a link to this group and all your TCs in OASIS
>> at:
>> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>> 
>>