View source for html5-profile-issues

{{DISPLAYTITLE:HTML5 profile attribute issues }}
__TOC__
These are externally raised issues about the [[html5-profile|HTML5 Profile Attribute]] with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. 

'''IMPORTANT''': Please read the [[html5-profile-faq|HTML5 Profile Attribute FAQ]] and the [[html5-profile-issues-resolved|HTML5 Profile Attribute resolved issues]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — [[User:Tantek|Tantek]]

== closed issues ==
See: [[html5-profile-issues-closed]]

== resolved issues ==
See: [[html5-profile-issues-resolved]]

== issues ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list below by copy and pasting the [[#template|template]].  Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues.  Duplicate issue additions will be reverted.

===2010===
* Copyright statement - 2010-02-19

This is a request for clarification.

This document is in the public domain. If the W3C HTML Working Group accepts to take on the proposal as a deliverable, should contributions from the Working Group participants expected to be in the public domain as well, or can they remain under the W3C Document license? As owner of [http://www.w3.org/html/wg/tracker/actions/29 ACTION-29] in the WG, I'm interested in gathering rationals in both approaches. -PLH.
<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2010-02-20</span> 
 raised by <span class="fn">Krzysztof Maczyński</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">Should sections 2 and 3 be normative?</strong>
The [http://lists.w3.org/Archives/Public/public-html/2010Feb/0683.html message announcing the draft] indicates that sections 2 (“listing known HTML 4.01 errata regarding the profile attribute on the head element”) and 3 (“describing how this specification could be applied to both previous versions of HTML and XHTML, and other markup languages”) would be informative. I propose that the HTML WG consider making them normative.
** other [http://lists.w3.org/Archives/Public/public-html/2010Feb/0685.html relevant] [http://lists.w3.org/Archives/Public/public-html/2010Feb/0690.html messages]
</div>
</div>


<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2010-02-21</span> 
 raised by <span class="fn">[[User:Komputist|LHS]]</span>
</span>
<div class="entry-content discussion issues">
*<strong class="entry-title"><code>data-foo=""</code> should be in (subsequent) scope of @profile.</strong> An <code> &lt;element class="classname"></code> that is linked to a profile should be treated as an element, for which it should be possible to specify optional or required data-foo attributes. <strong>Example:</strong> <code> &lt;element class="classname" data-profileprefix-attribute="value">&lt;/element></code> In other words, it should be possible to specify required/optional <code>data-foo=""</code> attributes together with specific ''element@class'' combinations. 
;Related info and messages: 
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0720 My message to the HTMLwg leading up to this issue entry],
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0692 Message from Toby Inkster in support of a html5 profile spec], 
:[http://lists.w3.org/Archives/Public/public-html/2010Jan/0618 The original profile  based distributed extensibility idea of Toby Inkster],
:[http://dev.w3.org/html5/spec/dom.html#attr-data data-foo="" in HTML5, including the ''space ship element'' example]: &lt;div class="spaceship" data-ship-id="92432" data-weapons="laser 2" [ etc ]
:For scripting libraries, then HTML5 recommends using a prefix (<code>data-prefx-attribute=""</code> to avoid clashes and should be considered for the HTML5 profile specification also.


</div>
</div>




<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2010-02-21</span> 
 raised by <span class="fn">[[User:Komputist|LHS]]</span>
</span>
<div class="entry-content discussion issues">
*<strong class="entry-title">ARIA attributes and <code>role=""</code> should be in (subsequent) scope of @profile.</strong> An <code> &lt;element class="classname"></code> that is linked to a profile should be treated as an element, for which it should be possible to specify recommended ARIA and role attribtues. <strong>Example:</strong> <code> &lt;element class="classname" role="button">&lt;/element></code>
;Related info and messages: 
:[http://lists.w3.org/Archives/Public/public-html/2010Feb/0720 My message to the HTMLwg leading up to this issue entry],
:[http://www.w3.org/mid/83960F12C8BA4EB2AD7753AAF13C38E1@joe1446a4150a8 Question from Joe D Williams (comment to Toby Inksters Distributed Extensibility proposal]


</div>
</div>

== template ==
{{issues-format}}

== related pages ==
* [[html5-profile]]
* [[html5]]
* [[xmdp]]