W3C home > Mailing lists > Public > public-annotation@w3.org > April 2016

Re: [web-annotation] HTML Serialization Use Cases

From: Ivan Herman via GitHub <sysbot+gh@w3.org>
Date: Fri, 08 Apr 2016 17:55:41 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-207536969-1460138139-sysbot+gh@w3.org>
Looking at the 
 put in by @tcole3 :

First of all, what I like in all these approaches is that they work 
out of the box today, without any need for an extension of HTML. That 
is a major plus. However I believe that, for practical purposes, we 
could cross microdata from the list. Microdata, as far as I know, is 
used only by schema.org (which is of course important!); I do not know
 of any other environments, tools, etc, that would process microdata.

One of the main complications (maybe _the_ major complication) of the 
RDFa encoding is that, being a true RDF serialization, it relies on a 
number of namespaces (duly set in a `@prefix` attribute). RDF 
experts/users have no problem with that, it is in their blood :-), but
 the Web Application community frowns on that (nay, they vehemently 
refuse doing that). We have avoided this problem in JSON-LD with the 
help of the appropriate `@context` file but, alas!, nothing like that 
exists in RDFa.

*If* we expect the RDFa encoding ever being done by human users and 
not only by machines behind the scenes, we may have to address this. 
There is an approach to do that, but I have to ask my RDF friends to 
hold their nose:-): we can define a single namespace vocabulary that 
consists of nothing else than a series of `owl:sameAs` statements (or 
equivalents for classes and properties) to the resources in the OA 
Vocabulary. Ie, it would provide, essentially, aliases (via 
`owl:sameAs`) to `oa` terms, `dc` terms, etc. A fake `@context` file, 
thus. If we do this, we can greatly simplify the RDFa encoding:

<p vocab="http://my.fake.vocabulary.ns">On August 1, 1779, F...
                from the <span id="Anno1" typeOf="Annotation" 
                        <time property="created" datatype="dateTime" 
                        <span property="creator" 
typeOf="Person"><meta property="name" content="Tim Cole"/></span>


It *is* an ugly hack from an RDF point of view, although perfectly 
"legal". But it works, and may become then a fairly acceptable way of 
encoding an annotation in RDFa.

Take a deep breath before you answer:-)

GitHub Notification of comment by iherman
Please view or discuss this issue at 
 using your GitHub account
Received on Friday, 8 April 2016 17:55:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:45 UTC