7670
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
WONT
|
Use of prefixes is too complicated for a Web technology
|
2009-09-18
|
2011-08-04
|
8976
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Modifying the Input Document section is labeled as informative but include normative requirements
|
2010-02-14
|
2011-08-04
|
8977
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Some conformance keywords are used prior to the Conformance Requirements section
|
2010-02-14
|
2011-08-04
|
8978
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Document conformance requirements does not state that extensions to HTML5 syntax are allowed
|
2010-02-14
|
2011-08-04
|
8979
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
WONT
|
Please reconsider should-level requirement for version attribute
|
2010-02-14
|
2011-08-04
|
8980
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
HTML+RDFa has should-/may-level requirements for undefined constructs
|
2010-02-14
|
2011-08-04
|
8981
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Conforming documents are not required to use RDFa constructs in a conforming way
|
2010-02-14
|
2011-08-04
|
8982
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Unclear what features are required for user agents
|
2010-02-14
|
2011-08-04
|
8983
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Section 4.1 is unclear about language requirements
|
2010-02-14
|
2011-08-04
|
8984
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Invalid XMLLiteral definition of namesspace-well-formed XML fragments is too weak
|
2010-02-14
|
2011-08-04
|
8985
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Unclear if requirement to ensure namespace well-formed fragments is separate from other transformation requirements
|
2010-02-14
|
2011-08-04
|
8986
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Link to "Section 5.4, CURIE and URI Processing" points to the wrong place
|
2010-02-14
|
2011-08-04
|
8987
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Processing requirements for attributes starting with xmlns: are undefined
|
2010-02-14
|
2011-08-04
|
8988
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Extensions to HTML5 syntax should be described as extensions, not modifications
|
2010-02-14
|
2011-08-04
|
8989
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Allowance for attributes starting with xmlns: should be stated as a requirement on documents and conformance checkers, not on the HTML5 spec
|
2010-02-14
|
2011-08-04
|
8990
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Attributes starting with xmlns: are conforming even if illegal per Namespaces in XML
|
2010-02-14
|
2011-08-04
|
8991
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Change to "coercion to infoset" rules is underdefined
|
2010-02-14
|
2011-08-04
|
8992
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
WONT
|
Coercion to Infoset extensions mean that HTML document could produce different infosets in an HTML5 UA and an HTML+RDFa UA
|
2010-02-14
|
2011-08-04
|
8993
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Spec says that mapping from DOM to tree-model is not necessary, but later gives such a mapping
|
2010-02-14
|
2011-08-04
|
8994
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
HTML+RDFa will process attributes in the XHML namespace as well as the null namespace; XHTML+RDFa does not
|
2010-02-14
|
2011-08-04
|
8995
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
NEED
|
DOM processing of xmlns: attributes should look at namespace URI, not namespace prefix
|
2010-02-14
|
2011-08-04
|
8996
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
INVA
|
Typo in DOM processing rules
|
2010-02-14
|
2011-08-04
|
8997
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Sections 6 and 7 are informative but appear to give normative requirements
|
2010-02-14
|
2011-08-04
|
8998
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
There is no requirement that the values of attributes starting with xmlns: conform to Namespaces in XML
|
2010-02-14
|
2011-08-04
|
9010
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
INVA
|
There are one or more alternate methods of adding data without using RDFa, such as [microdata].
|
2010-02-16
|
2011-08-04
|
9011
|
HTML WG
|
LC1 HTML
|
msporny
|
CLOS
|
FIXE
|
There are discussions of alternate extensibility mechanisms, covered in [issue-41], which might allow other ways of integrating RDFa.
|
2010-02-16
|
2011-08-04
|
9012
|
HTML WG
|
LC1 HTML
|
msporny
|
CLOS
|
FIXE
|
There is concern that continued development of HTML+RDFa belongs in a different working group.
|
2010-02-16
|
2011-08-04
|
9646
|
HTML WG
|
LC1 HTML
|
msporny
|
CLOS
|
FIXE
|
Clean up the DTD - e.g. remove reference to Strict and Transtitional
|
2010-05-03
|
2011-08-04
|
9647
|
HTML WG
|
LC1 HTML
|
msporny
|
CLOS
|
INVA
|
Turn HTML+RDFa into a polyglot specification
|
2010-05-03
|
2011-08-04
|
9874
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
HTML+RDFa 1.1 in @version could be confusing
|
2010-06-08
|
2011-08-04
|
10319
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Wrong link to "RDFa Profile"
|
2010-08-09
|
2011-08-04
|
10970
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
WONT
|
Align HTML+RDFa with Microdata: add support for @cite
|
2010-10-03
|
2011-08-04
|
11169
|
HTML WG
|
LC1 HTML
|
msporny
|
CLOS
|
WONT
|
HTML+RDFa - Infer @content from @datetime on time tag
|
2010-10-29
|
2011-08-04
|
11371
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Some elements not allowed to take RDFa attributes - list seems pretty arbitrary.
|
2010-11-22
|
2011-08-04
|
13101
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
NEED
|
TAG issue on HTML+RDFa and Microdata last call drafts
|
2011-06-30
|
2011-10-11
|
13645
|
HTML WG
|
LC1 HTML
|
msporny
|
RESO
|
FIXE
|
Reference section 12.1 'text/html' of HTML5 instead of RFC 3236
|
2011-08-03
|
2012-01-22
|