RE: [dita] Errata information added to home page

["Grosso, Paul" <pgrosso@ptc.com>]

> -----Original Message-----
> From: Mary McRae [mailto:marypmcrae@gmail.com] On Behalf Of Mary McRae
> Sent: Tuesday, 2007 September 04 13:51
> To: Grosso, Paul; dita@lists.oasis-open.org
> Subject: RE: [dita] Errata information added to home page
> 
> Hi Paul et al,
> 
> The only errata allowed by the OASIS TC Process is one that 
> has been created
> and approved by the TC, submitted for a 15-day public review, and then
> reapproved by the TC and then associated with the relevant 
> OASIS Standard.

Understood.  I suppose we'd have to explain that what our Errata 
page really records are the resolutions of cases where we found 
a mistake but it isn't an official erratum yet, but if you want
to know the "right" answer that we plan to put into the next
published version, check here.

> Note that our rules allow only non-substantive changes to be 
> incorporated
> into errata. It sounds like what the TC has instead decided 
> is to create, in
> effect, an issues list with suggested resolutions that will 
> be incorporated
> into a future release. 

You could call it that. 

> Some TCs do choose to post their 
> issues lists to
> docs.oasis-open.org so that there is a persistent 
> "latest-version" URI as
> well as version-specific URIs for historical reference. The 
> TC can also
> create a v1.1.1 and approve it as a Committee Draft, and then 
> continue to
> add corrections and reapprove. 

We probably will do that (I cannot speak for the TC, of course),
but what I thought we should do is have a page on which we
could record things we decided to put into the next CD immediately
upon decision rather than waiting until the next CD is actually
published.

> I'm not sure what the final 
> intent of the TC
> is - that at some point an official errata for v1.1 will be 
> issued, that a
> v1.1.1 will be submitted for OS approval, or that the changes will be
> incorporated in the next release (v1.2?)
> 
>   There is nothing to prevent the TC from creating a heading 
> on the existing
> public page entitled "Errata"
> and noting such documents and 
> having that
> document (or any other TC approved document - that is, 
> anything that has
> reached Committee Draft status) uploaded to 
> docs.oasis-open.org. There is
> also no problem in creating that Errata document, approving it by the
> committee as a CD, and then continuing to update it rather 
> than submitting
> for public review until such time as the TC feels they've 
> gotten through
> most of the flaws (our process requires a six-month period 
> between errata releases). 

If I understand, we could produce an "Errata" document (explaining
that these are "resolved issues" but not yet official errata) and
get that put at some reasonable URL on the OASIS site.  Then we
could augment the content of that document (without changing its
URL) as we find and resolve more issues.  Is that correct?  Who
would have permission to augment that document?  

Something like that would seem to me to be most beneficial to
our user and implementor community and most manageable by the TC.

paul

> 
>   I'm ready and willing to help - I just need to know exactly 
> how the TC
> wants to proceed.
> 
> Regards,
> 
> Mary
> 
> -----Original Message-----
> From: Grosso, Paul [mailto:pgrosso@ptc.com] 
> Sent: Tuesday, September 04, 2007 1:42 PM
> To: dita@lists.oasis-open.org
> Subject: RE: [dita] Errata information added to home page
> 
>  
> 
> > -----Original Message-----
> > From: Robert D Anderson [mailto:robander@us.ibm.com] 
> > Sent: Tuesday, 2007 September 04 12:19
> > To: dita@lists.oasis-open.org
> > Subject: RE: [dita] Errata information added to home page
> > 
> > "Grosso, Paul" <pgrosso@ptc.com> wrote on 09/04/2007 12:11:57 PM:
> > > However, it would be best to have a separate "Errata for DITA 1.1"
> > > page that could be linked to from this location on our 
> main TC page.
> > 
> > I agree - I asked Don about setting up another page at the 
> > TC, but it looks
> > like the only way to add pages to the main Committee page is 
> > by uploading a
> > document or by sending an email. In that case it won't really be a
> > permanent Errata page. One alternative was to point to a page 
> > on our Wiki,
> > but (to me) that seemed rather too unofficial. If somebody 
> > has a suggestion
> > of how to get a more official looking errata page at the TC, 
> > please speak
> > up... alternatively, if others think a wiki page is 
> > appropriate, we could just do that.
> 
> <rant>The OASIS Kavi system has many disadvantages, and some of
> us have been complaining about them for years.  Unfortunately,
> either we are in the minority or we have been ignored.  The
> problems, such as this, remain.  We still don't really have
> a web site, just a web-dispensed data base.  I hate it.</rant>
> 
> Maybe Mary can suggest a way we can have a real Errata page
> to which we can point and which we can update as necessary.
> 
> > 
> > > By the way, are the links into our mailing list and document
> > > archive member-only, or do they work for others?
> > 
> > The links from the TC page are for anybody. The internal 
> links within
> > Eric's email are member only, because that's what the 
> upload-document
> > function generates.
> 
> Which is a problem, because that means a non-member doesn't
> have access to the corrected schemas.  If we are going to
> "publish" an erratum with corrected schemas, it seems that
> non-members should be able to access those schemas.
> 
> Given the ongoing inadequacies in the OASIS web site setup,
> perhaps this idea of an Errata page is too much trouble.
> It seemed like such a simple, obvious idea--like the W3C
> uses--but if it's going to be so difficult to do right, 
> I'm ready to give up on it.
> 
> paul
>