This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13600 - Provide XHTML entity definitions in a more convenient way
Summary: Provide XHTML entity definitions in a more convenient way
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-03 09:25 UTC by Jirka Kosek
Modified: 2011-09-23 22:35 UTC (History)
5 users (show)

See Also:


Attachments

Description Jirka Kosek 2011-08-03 09:25:26 UTC
Section 9.2 contains data URI to provide definitions of entities for XHTML content. Such definition should directly listed in the HTML5 spec or should be available at some http://... URI
Comment 1 David Carlisle 2011-08-03 16:39:13 UTC
(In reply to comment #0)
> Section 9.2 contains data URI to provide definitions of entities for XHTML
> content. Such definition should directly listed in the HTML5 spec or should be
> available at some http://... URI

baring bugs they should be the same as

http://www.w3.org/2003/entities/2007/htmlmathml-f.ent

(they are derived from the same source)


David
Comment 2 Jirka Kosek 2011-08-03 21:45:57 UTC
(In reply to comment #1)

> baring bugs they should be the same as
> 
> http://www.w3.org/2003/entities/2007/htmlmathml-f.ent
> 
> (they are derived from the same source)

Cool. Then adding just this URL into spec should be fine. I was reading printed version of spec and having link to data-URI was not really very convenient. ;-)
Comment 3 Michael[tm] Smith 2011-08-04 05:15:14 UTC
mass-move component to LC1
Comment 4 Ian 'Hixie' Hickson 2011-08-14 06:57:12 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: The file in question is huge and not intended to be human-readable. It's already in the spec in a human readable fashion in the table a few pages earlier.
Comment 5 David Carlisle 2011-08-14 09:52:10 UTC
(In reply to comment #4)

> Rationale: The file in question is huge and not intended to be human-readable.
> It's already in the spec in a human readable fashion in the table a few pages
> earlier.

Ian, would it be possible to add a line saying that?

It isn't at all obvious reading the spec that that base 64 encoded data URL has essentially the same data as the entity table given earlier. Would you consider changing

 the public identifiers given in the following list all correspond to <a href="data:...>the URL given by this
  link</a>.

to something like


 the public identifiers given in the following list all correspond to <a href="data:...>the URL given by this
  link</a>, which defines all the entities listed in the section <a href="#...>Named character references</a> which are compatible with the XML syntax.
Comment 6 Jirka Kosek 2011-08-15 07:47:38 UTC
I second David's suggestion. Adding such simple explanatory text will eliminate any possible confusion.
Comment 7 Ian 'Hixie' Hickson 2011-08-23 05:01:15 UTC
Sure, I can add some pointer to that section.
Comment 8 Ian 'Hixie' Hickson 2011-09-23 22:34:06 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Adding an explanation is useful.
Comment 9 contributor 2011-09-23 22:35:35 UTC
Checked in as WHATWG revision r6583.
Check-in comment: Explain what the DTD is.
http://html5.org/tools/web-apps-tracker?from=6582&to=6583