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

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-comment message

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


Subject: Normative References in the CAP Specification.


Title: Message
    Except by implication from the examples and the XML Schema, the CAP specification doesn't really say what version of XML is to be used in conforming systems. Given that XML 1.1 has been defined and given that one would probably want to ensure that readers did not think that XML 1.1 was being supported, it would be good to explicitly state that CAP is based on XML 1.0. A reference to the XML 1.0 specification should be provided in section 1.6 "Normative References."
    There should also be normative references to ISO 8601, RFC3066, FIPS Publication 180-1, WGS-84 and the other references mentioned below: (After corrections to the spec are made...)
    The CAP specification refers to RFC1766 when defining the language element. However, RFC1766 is obsolete. It was replaced by RFC3066 and RFC3282. The definition of the language element should be modified to reflect this and an appropriate normative reference included in section 1.6.
    The definition of the mimeType element refers to RFC1521. However, this RFC is also obsolete. According to the IETF,  it was obsoleted by RFC2045, RFC2046, RFC2047, RFC2048, RFC2049 and updated by RFC1590.
    The specification refers to "namespaces" although namespaces are not defined in XML 1.0. Thus, there should be a reference to the appropriate namespace specification at W3.org. You probably want "Namespaces in XML" which is at http://www.w3.org/TR/REC-xml-names/ rather than the more recent "Namespaces in XML 1.1".
    Given that there are multiple versions of these documents it is critically important that explicit normative references be made to them. If you don't do this, the result will be ambiguity that could compromise the ability to produce interoperable implementations.
 
        bob wyman
 


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