Difference between revisions of "PolyglotRecommendationRationale"

From HTML WG Wiki
Jump to: navigation, search
(Initial rationale for polyglot as a Recommendation)
 
m
Line 10: Line 10:
 
** [http://www.w3.org/TR/wsc-ui/ Web Security Context: User Interface Guidelines]
 
** [http://www.w3.org/TR/wsc-ui/ Web Security Context: User Interface Guidelines]
  
<div id="normative">On the topic of using normative language in the specification:</div>
+
<div id="normative">On the topic of using ''normative language'' in the specification:</div>
  
 
* The purpose for using normative language in the specification is to make it clear which parts are necessary to conform to the specification and which parts provide advisory or informative content. The polyglot spec is intended to make it possible to objectively determine if a document adheres to its requirements and therefore it is appropriate to differentiate between normative and informative parts.
 
* The purpose for using normative language in the specification is to make it clear which parts are necessary to conform to the specification and which parts provide advisory or informative content. The polyglot spec is intended to make it possible to objectively determine if a document adheres to its requirements and therefore it is appropriate to differentiate between normative and informative parts.

Revision as of 16:20, 6 December 2012

The Polyglot Markup: HTML-Compatible XHTML Documents specification (aka Polyglot spec) should be considered for the Recommendation track because:

  • While we might not Recommend that all authors (or in fact that many authors) should create Polyglot documents, we should Recommend that when authors want to create polyglot markup they do so by following the authoring requirements outlined in this specification. In fact, the introduction of the Polyglot spec does state that "All web content need not be authored in polyglot markup."
  • The Polyglot spec does include normative language that can be followed precisely and a document can be measured objectively against those requirements to see if it successfully adheres to the polyglot markup rules. It is possible to build a validator that checks a document to see if it is a valid polyglot document according to the polyglot spec and to identify the normative requirements that have been violated should the validation fail.
On the topic of using normative language in the specification:
  • The purpose for using normative language in the specification is to make it clear which parts are necessary to conform to the specification and which parts provide advisory or informative content. The polyglot spec is intended to make it possible to objectively determine if a document adheres to its requirements and therefore it is appropriate to differentiate between normative and informative parts.