Skip to content

Commit e22c173

Browse files
mspornymsporny
committed
Added HTML5 profile specification.
1 parent 78fce53 commit e22c173

File tree

11 files changed

+517
-91
lines changed

11 files changed

+517
-91
lines changed

‎configs/html5-profile.conf‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
# This file was auto-generated using the microsplit.py tool.
2+
#
3+
# You may edit this file in a number of ways and process it using the
4+
# microjoin.py tool to create an entirely new specification. To create a new
5+
# specification, copy this file to the "configs" directory in your repository
6+
# and start modifying it.
7+
#
8+
# * To delete a section, delete any line from the list below.
9+
# * To add a section, insert a line like the folowing:
10+
# include YOUR_MICROSECTION_FILE
11+
# * To apply a patch to the final, combined file, do the following:
12+
# (NOT IMPLEMENTED YET)
13+
# * To construct a new source document, run the following command:
14+
# ./bin/microjoin.py THIS_CONFIGURATION_FILE THE_OUTPUT_FILE
15+
#
16+
include headers/header-w3c-profile
17+
include build/table-of-contents
18+
include microsections/profile/introduction
19+
include microsections/profile/modifications
20+
include microsections/profile/references

‎configure.ac‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,7 @@ fi
5555
AC_CONFIG_FILES([
5656
Makefile
5757
headers/header-w3c-html5
58+
headers/header-w3c-profile
5859
headers/header-w3c-rdfa
5960
headers/header-w3c-msporny
6061
headers/header-w3c-microdata

‎headers/header-w3c-profile.in‎

Lines changed: 326 additions & 0 deletions
Large diffs are not rendered by default.

‎headers/header-w3c-rdfa‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -206,7 +206,7 @@
206206
<h2 class="no-num no-toc" id="a-mechanism-for-embedding-rdf-in-html">
207207
A mechanism for embedding RDF in HTML
208208
</h2>
209-
<h2 class="no-num no-toc" id="editor-s-draft-date-05-September-2009">Editor's Draft 05 September 2009</h2>
209+
<h2 class="no-num no-toc" id="editor-s-draft-date-26-September-2009">Editor's Draft 26 September 2009</h2>
210210
<!--:ZZZ-->
211211
<dl>
212212
<!-- ZZZ: update the month/day (twice), (un)comment out
@@ -259,8 +259,8 @@
259259
This specification defines rules and guidelines for adapting the
260260
RDF in XHTML: Syntax and Processing (RDFa) specification for use in the
261261
HTML5 and XHTML5 members of the HTML family. The rules defined in this
262-
document not only apply to HTML5 documents in non-XML and XML mode, but
263-
also to HTML4 documents interpreted through the HTML5 parsing rules.
262+
document not only apply to HTML5 documents in non-XML and XML mode,
263+
but also to HTML4 documents interpreted through the HTML5 parsing rules.
264264
</p>
265265
<h2 class="no-num no-toc"
266266
id="status-of-this-document">
@@ -318,8 +318,8 @@
318318
</p>
319319
<!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) -->
320320
<p>
321-
This specification is an extension to the HTML5 language. All
322-
normative content in the HTML5 specification, unless overridden by this
321+
This specification is an extension to the HTML5 language. All normative
322+
content in the HTML5 specification, unless specifically overridden by this
323323
specification, is intended to be the basis for this specification.
324324
</p>
325325
<!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate -->

‎headers/header-w3c-rdfa.in‎

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
<!-- when publishing, change bits marked ZZZ -->
44
<html lang="en-US-x-Hixie">
55
<head>
6-
<title>HTML5+RDFa</title>
6+
<title>HTML+RDFa</title>
77
<style type="text/css">
88
pre { margin-left: 2em; white-space: pre-wrap; }
99
h2 { margin: 3em 0 1em 0; }
@@ -202,7 +202,7 @@
202202
src="http://www.w3.org/Icons/w3c_home"
203203
width="72"></a>
204204
</p>
205-
<h1>HTML5+RDFa</h1>
205+
<h1>HTML+RDFa</h1>
206206
<h2 class="no-num no-toc" id="a-mechanism-for-embedding-rdf-in-html">
207207
A mechanism for embedding RDF in HTML
208208
</h2>
@@ -233,7 +233,7 @@
233233
Steven Pemberton (Chair, XHTML2, CWI)
234234
</dd>
235235
<dd>
236-
<a href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>, (Editor, HTML5+RDFa, Digital Bazaar, Inc.)
236+
<a href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>, (Editor, HTML+RDFa, Digital Bazaar, Inc.)
237237
</dd>
238238
</dl>
239239
<p class="copyright">
@@ -259,8 +259,8 @@
259259
This specification defines rules and guidelines for adapting the
260260
RDF in XHTML: Syntax and Processing (RDFa) specification for use in the
261261
HTML5 and XHTML5 members of the HTML family. The rules defined in this
262-
document not only apply to HTML5 documents, but also to HTML4 documents
263-
interpreted through the HTML5 parsing rules.
262+
document not only apply to HTML5 documents in non-XML and XML mode,
263+
but also to HTML4 documents interpreted through the HTML5 parsing rules.
264264
</p>
265265
<h2 class="no-num no-toc"
266266
id="status-of-this-document">
@@ -318,8 +318,9 @@
318318
</p>
319319
<!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) -->
320320
<p>
321-
This specification is intended to be included in the HTML5 specification
322-
as a section of the overall specification.
321+
This specification is an extension to the HTML5 language. All normative
322+
content in the HTML5 specification, unless specifically overridden by this
323+
specification, is intended to be the basis for this specification.
323324
</p>
324325
<!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- required patent boilerplate -->
325326
<p>

‎microsections/profile/introduction‎

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
<h2>Background</h2>
2+
3+
<p>
4+
The profile attribute was introduced in HTML 4 as a means to specify the location of one or more meta data profiles. The attribute could contain a space-separated list of tokens or URIs and was primarily designed to extend the way User Agents processed the HTML document. User agents could recognize the URI (without actually retrieving the profile) and perform some activity based on known conventions for that profile or dereference the URI and perform some activity based on the actual definitions within the profile.
5+
</p>
6+
7+
<p>
8+
While specific profiles were not defined in HTML 4, the profile attribute was later used in [<a href="#refsXHTML">XHTML</a>], [<a href="#refsERDF">ERDF</a>], [<a href="#refsGRDDL">GRDDL</a>], and [<a href="#refsXHTMLRDFA">XHTML+RDFA</a>] in order to present processing instructions for extracting semantics from attribute values containing the the HTML document.
9+
</p>

‎microsections/profile/modifications‎

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
<h2>
2+
Profile in HTML5
3+
</h2>
4+
5+
<p>
6+
<em>This section is normative.</em>
7+
</p>
8+
<p>
9+
There are a few changes that are required to the HTML5 specification in
10+
order to fully support User agent profiles. The following sub-sections
11+
outline the necessary modifications to the base HTML5 specification.
12+
</p>
13+
14+
<h3>The <code>profile</code> attribute and link type</h3>
15+
<p>
16+
For content conforming to this specification, <code>profile</code>
17+
is an obsolete but conforming attribute name when used in the
18+
<code>head</code> element and when its value is set to the
19+
XHTML Vocabulary URI: "http://www.w3.org/1999/xhtml/vocab".
20+
The <code>profile</code> link type replaces
21+
the <code>profile</code> attribute. The <code>profile</code> link type
22+
should be used in the <code>rel</code> attribute in a <code>link</code>
23+
element contained in the <code>head</code> element of a conforming
24+
document. When the <code>profile</code> link type is specified, its
25+
value must be the XHTML Vocabulary URI:
26+
"http://www.w3.org/1999/xhtml/vocab". For example:
27+
</p>
28+
29+
<pre>
30+
&lt;head&gt;
31+
&lt;link rel="profile" href="http://www.w3.org/1999/xhtml/vocab" /&gt;
32+
&lt;/head&gt;
33+
</pre>
34+
<p>
35+
This particular attribute and link type is used to provide a language
36+
version signalling mechanism to the RDFa Processor. In future versions
37+
of RDFa, the value of the profile may trigger different processing
38+
rules in RDFa Processors.
39+
</p>
40+
<p>
41+
Authors should use the <code>profile</code> link type instead of the
42+
<code>profile</code> attribute when authoring new HTML documents.
43+
</p>
44+
45+
<p>
46+
The table entry below extends the list of link types as specified in
47+
<a href="http://www.w3.org/TR/html5/Overview.html#linkTypes">Link types section</a>
48+
of the HTML5 specification:
49+
<table>
50+
<thead>
51+
<tr>
52+
<th rowspan="2">Link type</th>
53+
<th colspan="2">Effect on...</th>
54+
<th rowspan="2">Brief description</th>
55+
</tr>
56+
<tr>
57+
<th><code>link</code></th>
58+
<th><code>a</code> and <code>area</code></th>
59+
</tr>
60+
</thead>
61+
<tbody>
62+
63+
<tr>
64+
<td><code title="rel-profile">profile</code></td>
65+
<td><span title="hyperlink link">Hyperlink</span></td>
66+
<td><em>not allowed</em></td>
67+
<td>
68+
In the future, this may trigger different RDFa Processor behavior
69+
based on the value of the <code>href</code> attribute.
70+
</td>
71+
</tr>
72+
73+
</tbody
74+
</thead>
75+
</table>
76+
</p>

‎microsections/profile/references‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
<h2>Normative References</h2>
2+
3+
<dl>
4+
<dt id="refsHTML5">[HTML5] (currently not a REC)</dt>
5+
<dd>The HTML5 Specification</dd>
6+
</dl>
7+
8+
<h2>Non-Normative References</h2>
9+
10+
<p>All references are non-normative.</p>
11+
12+
<dl>
13+
<dt id="#refsGRDDL">[<a href="">GRDDL</a>]</dt>
14+
<dd>Gleaning Resource Descriptions from Dialects of Languages (GRDDL), Dan Connolly. W3C, September 2007.</dd>
15+
<dt id="refsXHTMLRDFA">[<a href="http://www.w3.org/TR/rdfa-syntax/">XHTML+RDFA</a>]</dt>
16+
<dd>RDFa in XHTML: Syntax and Processing, Mark Birbeck, Shane McCarron, Steven Pemberton. W3C, October 2008.</dd>
17+
<dt id="refsERDF">[<a href="http://research.talis.com/2005/erdf/wiki/Main/RdfInHtml">ERDF</a>]</dt>
18+
<dd>Embeddable Resource Description Framework, Ian Davis. Talis, October 2006</dd>
19+
</dl>

‎microsections/rdfa/rdfa-modifications-to-html5‎

Lines changed: 21 additions & 65 deletions
Original file line numberDiff line numberDiff line change
@@ -10,77 +10,33 @@
1010
necessary modifications to the base HTML5 specification.
1111
</p>
1212

13-
<h3>The <code>profile</code> attribute and link type</h3>
14-
<p>
15-
For content conforming to this specification, <code>profile</code>
16-
is an obsolete but conforming attribute name when used in the
17-
<code>head</code> element and when its value is set to the
18-
XHTML Vocabulary URI: "http://www.w3.org/1999/xhtml/vocab".
19-
The <code>profile</code> link type replaces
20-
the <code>profile</code> attribute. The <code>profile</code> link type
21-
should be used in the <code>rel</code> attribute in a <code>link</code>
22-
element contained in the <code>head</code> element of a conforming
23-
document. When the <code>profile</code> link type is specified, its
24-
value must be the XHTML Vocabulary URI:
25-
"http://www.w3.org/1999/xhtml/vocab". For example:
26-
</p>
27-
<pre>
28-
&lt;head&gt;
29-
&lt;link rel="profile" href="http://www.w3.org/1999/xhtml/vocab" /&gt;
30-
&lt;/head&gt;
31-
</pre>
32-
<p>
33-
This particular attribute and link type is used to provide a language
34-
version signalling mechanism to the RDFa Processor. In future versions
35-
of RDFa, the value of the profile may trigger different processing
36-
rules in RDFa Processors.
37-
</p>
38-
<p>
39-
Authors should use the <code>profile</code> link type instead of the
40-
<code>profile</code> attribute when authoring new HTML documents.
41-
</p>
13+
<h3>The RDFa Attributes and Valid Values</h3>
4214

4315
<p>
44-
The table entry below extends the list of link types as specified in
45-
<a href="http://www.w3.org/TR/html5/Overview.html#linkTypes">Link types section</a>
46-
of the HTML5 specification:
47-
<table>
48-
<thead>
49-
<tr>
50-
<th rowspan="2">Link type</th>
51-
<th colspan="2">Effect on...</th>
52-
<th rowspan="2">Brief description</th>
53-
</tr>
54-
<tr>
55-
<th><code>link</code></th>
56-
<th><code>a</code> and <code>area</code></th>
57-
</tr>
58-
</thead>
59-
<tbody>
16+
All RDFa attributes and valid values (including CURIEs), as listed in
17+
<a href="http://www.w3.org/TR/rdfa-syntax/#rdfa-attributes">Section 2.1: The RDFa Attributes</a>,
18+
are conforming when used in an HTML5 or XHTML5 document.
19+
</p>
6020

61-
<tr>
62-
<td><code title="rel-profile">profile</code></td>
63-
<td><span title="hyperlink link">Hyperlink</span></td>
64-
<td><em>not allowed</em></td>
65-
<td>
66-
In the future, this may trigger different RDFa Processor behavior
67-
based on the value of the <code>href</code> attribute.
68-
</td>
69-
</tr>
21+
<h3>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</h3>
7022

71-
</tbody
72-
</thead>
73-
</table>
23+
<p class="XXX">
24+
While this section outlines xmlns: conformance criteria for HTML+RDFa,
25+
the support for distributed extensibility in non-XML mode HTML5
26+
(using xmlns and xmlns:) is still an open issue. This section may be
27+
further modified before Last Call based on progress made on the
28+
distributed extensibility issue.
7429
</p>
7530

76-
<h3>Attributes That Start With <code>xmlns:</code></h3>
77-
7831
<p>
79-
Since RDFa uses <code>xmlns:</code> to specify CURIE prefixes, it is
32+
Since RDFa uses attributes starting with <code>xmlns:</code> to
33+
specify CURIE prefixes, it is
8034
important that any attribute starting with a case-insensitive match on
81-
the text string <code>xmlns:</code> be preserved in the DOM or other
82-
tree-like model that is passed to the RDFa Processor. It is also
83-
necessary that when validating non-XML mode documents that the validator
84-
must not generate a warning for attributes starting with
85-
<code>xmlns:</code>.
35+
the text string "<code>xmlns:</code>" be preserved in the DOM or other
36+
tree-like model that is passed to the RDFa Processor. While it is specified
37+
that HTML5 must preserve these attributes in the DOM, it must also accept
38+
these attributes as conforming in non-XML HTML5. For documents conforming
39+
to this specification, attributes with names that have the case
40+
insensitive prefix "<code>xmlns:</code>" are conforming in both HTML5 and
41+
XHTML5.
8642
</p>

‎microsections/rdfa/rdfa-modifications-to-xhtml-rdfa‎

Lines changed: 25 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -7,24 +7,28 @@
77
<p>
88
The [<a href="http://www.w3.org/TR/rdfa-syntax/">XHTML+RDFa</a>]
99
Recommendation is the base document on which this specification builds.
10-
XHTML+RDFa specifies the attributes and processing rules for extracting
10+
XHTML+RDFa specifies the attributes, in
11+
<a href="http://www.w3.org/TR/rdfa-syntax/#rdfa-attributes">Section 2.1: The RDFa Attributes</a>,
12+
and processing model, in
13+
<a href="http://www.w3.org/TR/rdfa-syntax/#s_model">Section 5: Processing Model</a>,
14+
for extracting
1115
RDF from an XHTML document. This section specifies changes to the
12-
attributes and processing rules defined in XHTML+RDFa in order to
16+
attributes and processing model defined in XHTML+RDFa in order to
1317
support extracting RDF from HTML documents.
1418
</p>
1519
<p>
1620
The requirements and rules, as specified in XHTML+RDFa and further
1721
modified in this document, apply to all HTML5 documents. The RDFa Processor
1822
operating on HTML and XHTML documents, specifically the resulting DOMs,
19-
must apply the same processing rules for both types of serializations an
23+
must apply the same processing rules for both types of serializations and
2024
DOMs.
2125
</p>
2226

2327
<h3>Specifying the language for a literal</h3>
2428
<p>
2529
The <code>lang</code> attribute must be processed in the same manner
2630
as the <code>xml:lang</code> attribute is in the XHTML+RDFa specification,
27-
<a href="http://www.w3.org/TR/rdfa-syntax/#sec_5.5.">Section 5.5</a>,
31+
<a href="http://www.w3.org/TR/rdfa-syntax/#sec_5.5.">Section 5.5: Sequence</a>,
2832
step #3.
2933
</p>
3034
The rules for determining the language of a node are specified in the
@@ -122,20 +126,30 @@
122126
element.
123127
</p>
124128

125-
<h3>The <code>xmlns:</code> attribute</h3>
129+
<h3><code>xmlns:</code>-Prefixed Attributes</h3>
130+
131+
<p class="XXX">
132+
While this section outlines xmlns: processing in RDFa, the support for
133+
distributed extensibility in non-XML mode HTML5 (using xmlns and xmlns:)
134+
is still an open issue. This section may be further modified before
135+
Last Call based on progress made on the distributed extensibility issue.
136+
</p>
137+
126138
<p>
127-
CURIE prefix mappings specified using <code>xmlns:</code>
128-
must be processed using the rules specified in the
129-
[<a href="http://www.w3.org/TR/REC-xml-names/">Namespaces in XML</a>]
130-
Recommendation.
139+
CURIE prefix mappings specified using attributes prepended with
140+
<code>xmlns:</code>
141+
must be processed using the rules specified in
142+
<a href="">Section 5.4, CURIE and URI Processing,</a>
143+
contained in the XHTML+RDFa specification.
131144
</p>
132145
<p>
133146
Since CURIE prefix mappings have been specified using <code>xmlns:</code>,
134147
and since HTML attribute names are case-insensitive, CURIE prefix names
135148
declared using the <code>xmlns:</code>attribute-name pattern
136149
<code>xmlns:&lt;PREFIX&gt;="&lt;URI&gt;"</code> should be specified
137-
using only lower-case characters. For example, the text "xmlns:" and the
138-
text in "&lt;PREFIX&gt;" should be lower-case only. This is to ensure that
150+
using only lower-case characters. For example, the text "<code>xmlns:</code>"
151+
and the text in <code>"&lt;PREFIX&gt;"</code> should be lower-case only.
152+
This is to ensure that
139153
prefix mappings are interpreted in the same way between HTML
140154
(case-insensitive attribute names) and XHTML (case-sensitive attribute
141155
names) document types.

0 commit comments

Comments
 (0)