1149 2005-03-04 02:52:06 +0000 Suggestions of examples for section 2.3 2005-04-28 11:53:51 +0000 1 1 1 Unclassified QA QASpec-GL LC-2004-11-22 All All RESOLVED REMIND http://lists.w3.org/Archives/Public/www-qa/2005Mar/0004.html P2 minor --- 1 dom karl karl oldest_to_newest 3980 0 dom 2005-03-04 02:52:06 +0000 In section 2.3, the TAG would like to see a reference to 'referencing Unicode' (a pointer to charmod would suffice) and 'referencing XML (1.0, 1.1, or infoset). These are tow useful, common examples that it would be beneficial to discuss. 3886 1 dom 2005-03-08 14:31:56 +0000 Doing references in Unicode is explained in: http://www.w3.org/TR/2005/REC-charmod-20050215/#sec-RefUnicode [I don't know yet whether this should be incorporated as part of Req 2.3.A (make a list of normative references) or as a second example of GP 2.3.B (after the one based on URIs ref); I guess it depends what 2.3.B ends up being after the split up of the new workflow-oriented section] 3638 2 dom 2005-04-28 11:36:46 +0000 The following examples have been added to SpecGL: As a separate example, any specification that defines the behavior of a class of product that creates XML should address creation of XML 1.1 and anticipate future XML versions. In XSLT, creation of XML is specified by <xsl:output method="xml" version="1.0" />, and each version of XSLT defines the allowable range of values for the version attribute. Another option is to reference the XML Infoset - for instance, XML Inclusions are compatible both with XML 1.0 and XML 1.1 since they reference normatively the XML Infoset, which is the same for the two versions of XML. In its section Referencing the Unicode Standard and ISO/IEC 10646, the specification Character Model for the World Wide Web 1.0: Fundamentals [CHARMOD] gives a detailed indications for referencing Unicode Standard and ISO/IEC 10646. Specification editors are encouraged to follow these recommendations. 3685 3 dom 2005-04-28 11:53:51 +0000 setting version to LC in case of future use