RE: RE: [emergency] Groups - emergency-CAPv1.1-errata1-fullspec.pdf (emergency-CAPv1.1-errata1-fullspec.pdf) uploaded

Hi Rex,

  The same concepts apply as to specifications themselves - at each point of
approval, the level of approval and associated date will need to be updated. So
right now the errata is a working draft; when voted and approved by the TC it
will become a Committee Draft with the date voted. The TC will then vote to
submit for 15-day public review and Elysa, as chair, will forward a request to
me to launch the review. Once the review is completed, comments must be resolved
and then the TC can decide to request a ballot for Committee Specification
status.

I hope this answers your question!

Mary 

> -----Original Message-----
> From: Rex Brooks [mailto:] 
> Sent: Monday, August 28, 2006 11:21 AM
> To: 
> Subject: Fwd: RE: [emergency] Groups - 
> emergency-CAPv1.1-errata1-fullspec.pdf 
> (emergency-CAPv1.1-errata1-fullspec.pdf) uploaded
> 
> Hi Mary,
> 
> Small point of order for naming guidelines on errata.
> 
> Does the overall date on the main document change denoting a 
> change in the document of record, or do we give the whole 
> document a new name, or do we publish the errata separately 
> and change only the date in the document of record (but make 
> the change in the document of record, of course)?
> 
> Cheers,
> Rex
> 
> >Subject: RE: [emergency] Groups -
> >emergency-CAPv1.1-errata1-fullspec.pdf
> >(emergency-CAPv1.1-errata1-fullspec.pdf) uploaded
> >Date: Thu, 24 Aug 2006 10:56:33 -0500
> >Thread-Topic: [emergency] Groups -
> >emergency-CAPv1.1-errata1-fullspec.pdf
> >(emergency-CAPv1.1-errata1-fullspec.pdf) uploaded
> >thread-index: AcbHlYwsXf47JAtUSle7WfF//esAoQAAFMqY
> >From: "Aymond, Patti" <>
> >To: <>,<>
> >X-Rcpt-To: <>
> >X-DPOP: Version number supressed
> >
> >Does the date need to change on the document for an errata?
> >
> >Patti
> >
> >
> >From:  [mailto:]
> >Sent: Thu 8/24/2006 10:52 AM
> >To: 
> >Subject: [emergency] Groups - emergency-CAPv1.1-errata1-fullspec.pdf
> >(emergency-CAPv1.1-errata1-fullspec.pdf) uploaded
> >
> >The document named emergency-CAPv1.1-errata1-fullspec.pdf
> >(emergency-CAPv1.1-errata1-fullspec.pdf) has been submitted by Rex 
> >Brooks* to the OASIS Emergency Management TC document repository.
> >
> >Document Description:
> >This is the pdf version of the full CAP v1.1 specification with the 
> >errata change.
> >
> >View Document Details:
> ><http://www.oasis-open.org/apps/org/workgroup/emergency/docum
> ent.php?do
> >cument_id=19902>http://www.oasis-open.org/apps/org/workgroup/
> emergency/
> >document.php?document_id=19902
> >
> >Download Document: 
> ><http://www.oasis-open.org/apps/org/workgroup/emergency/downl
> oad.php/19
> >902/emergency-CAPv1.1-errata1-fullspec.pdf>http://www.oasis-o
> pen.org/ap
> >ps/org/workgroup/emergency/download.php/19902/emergency-CAPv1
> .1-errata1
> >-fullspec.pdf
> >
> >
> >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.
> >
> >-OASIS Open Administration
> >
> >IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE:
> ><http://www.ieminc.com/e_mail_confidentiality_notice.html>htt
> p://www.ie
> >minc.com/e_mail_confidentiality_notice.html
> 
> 
> --
> Rex Brooks
> President, CEO
> Starbourne Communications Design
> GeoAddress: 1361-A Addison
> Berkeley, CA 94702
> Tel: 510-849-2309