Pete Johnston wrote:
> Using the conventions of the current DC-HTML profile, to generate a URI of http://purl.org/dc/terms/abstract you'd need
>
> <link rel="schema.DC" href="http://purl.org/dc/terms/"/>
> <link rel="DC.abstract" href="#abstract"/>
> ...
I keep being confused by dcterms/ vs elements/1.1/, but I guess that's
an orthogonal issue.
> Re the fragment id, I don't see any reason it shouldn't work in principle.
>
> The only question that occurred to me (and it is just a question - I'm by no means sure about this) was whether it would be more appropriate to use something like
>
> <div id="#abstract">
> <h1>Abstract</h1>
> <p>...</p>
> </div>
Yes, my example was broken; and you spotted a related question; should
it be a container, including title and text, or maybe:
<h1>Abstract</h1>
<p id="abstract">...</p>
Or, rephrasing this: is the title of the Abstract supposed to be part of
the abstract?
> on the basis that the abstract is more than just the h1 element?
>
> I guess this is "what does a fragment id in HTML identify?" territory, which I think is determined by media type
>
> http://www.ietf.org/rfc/rfc2854.txt (for media type text/html)
> http://www.ietf.org/rfc/rfc3236.txt (for media type application/xml+xhtml)
> ...
BR, Julian
|