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


Help: OASIS Mailing Lists Help | MarkMail Help

office message

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

Subject: [OASIS Issue Tracker] Created: (OFFICE-2051) The OASISSpecification Documents need specific, unique errata links

The OASIS Specification Documents need specific, unique errata links

                 Key: OFFICE-2051
                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2051
             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
          Issue Type: Bug
          Components: General
    Affects Versions: ODF 1.2
         Environment: This issue applies to existing OASIS Standards and to the new specifications
            Reporter: Dennis Hamilton

1, Now that there are going to be separate parts for the ODF 1.2 specification, we need to agree on whether or not each part have a separate prospective errata document and whether there be a specific link that can be followed from each document to where its errata are found (without having to search the ODF TC document registry, as is the case now).

2. There should always be an errata document, even if it is one that indicates there are no errata at the present time.

3. There might also be back-references to errata for earlier specifications, in the case that they might be applicable or be useful.  (For example, there could be a placeholder errata document for ODF 1.1 that did acknowledge, in an unofficial way, the errata for ODF 1.0.)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


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