| bibo:hasPart
| -
4. Extensions to the HTML5 Syntax
There are a few attributes that are added as extensions to the HTML5
syntax in order to fully support RDFa:
- If HTML+RDFa Lite document conformance is desired, all RDFa attributes and
valid values (including CURIEs), as listed in
RDFa Lite 1.1, Section 2: The Attributes,
MUST be allowed and validate as conforming when used in an HTML4, HTML5 or
XHTML5 document. For the avoidance of doubt, the following RDFa attributes
are allowed on all elements in the HTML5 content model:
@vocab,
@typeof, @property, @resource, and
@prefix. All other attributes that RDFa may process, such as
@href and @src, are only allowed when consistent
with the content model for that element,
as defined in the HTML5 specification.
- If HTML+RDFa document conformance is desired, all RDFa attributes and
valid values (including CURIEs), as listed in
RDFa Core 1.1, Section 2.1: The RDFa Attributes,
MUST be allowed and validate as conforming when used in an HTML4, HTML5 or
XHTML5 document. For the avoidance of doubt, the following RDFa attributes
are allowed on all elements in the HTML5 content model:
@vocab,
@typeof, @property, @resource,
@prefix, @content, @about,
@rel, @rev, @datatype, and
@inlist. All other attributes that RDFa may process, such as
@href and @src, are only allowed when consistent
with the content model for that element,
as defined in the HTML5 specification.
- If the
@property RDFa attribute is present on the
link or meta elements, they MUST be viewed as
conforming if used in the body of the document.
More specifically,
when link or meta elements contain the
RDFa @property attribute and are used in the
body of an HTML5 document, they MUST be considered
flow content.
- If the RDFa
@property attribute is present on the link
element, the @rel attribute is not required.
- If the RDFa
@resource attribute is present on the link
element, the @href attribute is not required.
- If the RDFa
@property attribute is present on the meta
element, neither the @name, @http-equiv, nor @charset attributes are required
and the @content attribute MUST be specified.
-
4. Extensions to the HTML5 Syntax
There are a few attributes that are added as extensions to the HTML5
syntax in order to fully support RDFa:
- If HTML+RDFa Lite document conformance is desired, all RDFa attributes and
valid values (including CURIEs), as listed in
RDFa Lite 1.1, Section 2: The Attributes,
MUST be allowed and validate as conforming when used in an HTML4, HTML5 or
XHTML5 document. For the avoidance of doubt, the following RDFa attributes
are allowed on all elements in the HTML5 content model:
@vocab,
@typeof, @property, @resource, and
@prefix. All other attributes that RDFa may process, such as
@href and @src, are only allowed when consistent
with the content model for that element,
as defined in the HTML5 specification.
- If HTML+RDFa document conformance is desired, all RDFa attributes and
valid values (including CURIEs), as listed in
RDFa Core 1.1, Section 2.1: The RDFa Attributes,
MUST be allowed and validate as conforming when used in an HTML4, HTML5 or
XHTML5 document. For the avoidance of doubt, the following RDFa attributes
are allowed on all elements in the HTML5 content model:
@vocab,
@typeof, @property, @resource,
@prefix, @content, @about,
@rel, @rev, @datatype, and
@inlist. All other attributes that RDFa may process, such as
@href and @src, are only allowed when consistent
with the content model for that element,
as defined in the HTML5 specification.
- If the
@property RDFa attribute is present on the
link or meta elements, they MUST be viewed as
conforming if used in the body of the document.
More specifically,
when link or meta elements contain the
RDFa @property attribute and are used in the
body of an HTML5 document, they MUST be considered
flow content.
- If the RDFa
@property attribute is present on the link
element, the @rel attribute is not required.
- If the RDFa
@resource attribute is present on the link
element, the @href attribute is not required.
- If the RDFa
@property attribute is present on the meta
element, neither the @name, @http-equiv, nor @charset attributes are required
and the @content attribute MUST be specified.
|
![[OpenLink Software]](statics/openlinklogo_wstrap_2008.png)
