Re: HTML+RDFa Editorial Comment

Hi,

I've got some more editorial suggestions for "3.5 Property Copying":

1. The introductory text only mentions rdfa:copy explicitly
(highlighted with code). I suggest to mention rdfa:Pattern as well, by
changing:

* From: "This mechanism can be activated by using the
<code>rdfa:copy</code> predicate."
To: "This mechanism can be activated by declaring an
<code>rdfa:Pattern</code> and linking to it using the
<code>rdfa:copy</code> predicate."

* From: "In this case, the common properties for all of the events are
expressed in the first div."
To: "In this case, the common properties for all of the events are
expressed in the first div, captured in an <code>rdfa:Pattern</code>."

2. It may be good to add a note along the lines of:

Note that this mechanism and the examples given assume the predefined
prefix <code>rdfa:</code>, which is bound to
<http://www.w3.org/ns/rdfa#</code> by default. Thus,
<code>rdfa:copy</code> is expanded to
<code>http://www.w3.org/ns/rdfa#copy</code> and
<code>rdfa:Pattern</code> to
<code>http://www.w3.org/ns/rdfa#Pattern</code>. These are the IRIs
which RDFa processors will operate on. In practise, this default
prefix should be relied upon, since the predefined prefixes SHOULD NOT
be redefined, and a processor MUST issue warnings if this is the case.
But if for some reason <code>rdfa:</code> is locally rebound to
something else, authors using this mechanism need to use another
prefix bound to <code>http://www.w3.org/ns/rdfa#</code>, or use the
full IRIs instead.

(Perhaps the first two or three sentences are enough.) I suggest to
put it at the end of 3.5, after the last example, just prior to 3.5.1.

Cheers,
Niklas

Received on Saturday, 2 February 2013 16:16:35 UTC