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] Commented: (OFFICE-2155) Reconciling ExternalReferences in ODF 1.2

    [ http://tools.oasis-open.org/issues/browse/OFFICE-2155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476#action_16476 ] 

Michael Brauer commented on OFFICE-2155:

Here are the changes made for part 1, and a few comments to unchanged references:

CSS2: unmodified, because no information could be found what the changes to to CSS2 (revised) are. CSS2.1 is a candidate recommendation, and therefor not suitable for a normative reference.

DCMI: Updated to the latest version.

GRDDL: Added permanent URL.

HTML4: Kept as is, but corrected misspelled names. The most recent approved HTML version is XHTML 1.0, but this is a reformulation of HTML4, where the specification itself does not contain a description of the elements and attributes to which we refer. It is not suitable as a reference.

ISO/IEC Directives: Corrected as proposed.

ISO15924: Corrected as proposed (other ISO references as well). RFC5464, which we reference additionally, clarifies which script codes are permitted.

ISO3166-1: Updated as proposed.

JDBC: has been removed (the reference was not required at all)

MIMETYPES: Updated as proposed.

ODF 1.0, ODF 1.1: Corrected as proposed

OLE: Not updated, because no alternative reference has been found

PNG: Updated as proposed

RDF-CONCEPTS: Corrected as proposed.

RDF-XML: Corrected as proposed.

RDFa: Corrected as proposed.

RFC2048: Removed. References to RFC2048 have been replaced by references to RFC4288

RFC2616: Corrected as proposed.

RFC3066: Removed. References to RFC2048 have been replaced by references to RFC5464

RFC4646: Removed. References to RFC2048 have been replaced by references to RFC5464

RNG: Kept as is, since we have no experience with the updated RNG version.

SMIL20: Updated to SMIL 20  Second edition. There new versions (2.1 and 3.0), but these are updates, where a deeper analysis would be required what an update to these versions would mean.

UAX9: Kept as is, because this is the version that corresponds to UNICODE 4.

UNICODE: Kept as is (UNICODE 4)

UTR20: Added permanent URL. The already referenced version 7 refers to UNICODE 4. Newer versions refer to UNICODE 5.

XForms: Updated to XForms 1.0 (Third Edition)

XLink: Added permanent URL

XML-ID: Corrected as proposed.

xml-names: No change. Was already 1.0 (Second Edition)

XML 1.0: Updated to XML 1.0 (4th edition). See also OFFICE-1208.

xmlenc-core: The references actually cited XML DSig, but should be XML Encryption. This has been corrected.

XSL: Corrected as proposed.

XSLT 1.0: Kept as is. A switch to XSLT 2.0 requires a deeper analysis.

> Reconciling External References in ODF 1.2
> ------------------------------------------
>                 Key: OFFICE-2155
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2155
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: External References, OpenFormula, Packaging
>    Affects Versions: ODF 1.2
>         Environment: This applies to the current (2009-10-21) posted drafts of ODF 1.2 Part 1, ODF 1.2 Part 2, and ODF 1.2 Part 3.
>            Reporter: Dennis Hamilton
>            Assignee: Michael Brauer
>            Priority: Critical
>             Fix For: ODF 1.2
> The consistent reconciliation of the references used in the ODF 1.2 parts, with use of the appropriate currently-applicable specifications is required.  There is no good single place for determining what the references are and ensuring that they are used with the same understanding in the details of those parts.
> Approach:
> There are a variety of unresolved issues around the reference sections and the choice of specific references in those sections.  This JIRA issue provides a place for the top-level resolution that is required with regard to organization and what the individual references are.
> Use individual issues when needed for deeper reconciliation of specific considerations with regard to an individual normative reference:  addressing any difference from previous versions of ODF and their impact, profiling of normative use of provisions from other specifications, etc.  Those issue number may be catalogued and cross-referenced with this issue for easy location and review.
> Resources: 
> Rely on the references.odt file and discussion held earlier in 2009.  See http://www.oasis-open.org/committees/document.php?document_id=31301

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]