W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > January 2008

Re: RDFa for HTML imagemap accessibility and clipart?

From: Dan Brickley <danbri@danbri.org>
Date: Mon, 07 Jan 2008 15:16:04 +0000
Message-ID: <47824234.9030502@danbri.org>
To: Ivan Herman <ivan@w3.org>
CC: RDFa <public-rdf-in-xhtml-tf@w3.org>, foaf-dev <foaf-dev@lists.foaf-project.org>

Ivan Herman wrote:
> I made a run at it; it is actually pretty close to Niklas' second 
> version.

Thanks Ivan, Niklas, Karl, ...

We're getting there!

> What I guess you wanted to achieve was:
> 
> _:a a foaf:Person;
>     foaf:name "Dan Brickley".
> <#area> ex:depicts _:a.
> <http://danbri.org> foaf:primaryTopic :_a.

Yup, but I was hoping also to get the details of the area and the image 
URL into triples too, so a SPARQL store can be a self-contained 
photographic addressbook / clipart db.

I put your example into http://danbri.org/2008/imagemap/ivan.html and 
ran the latest GetN3 .js bookmarklet on it. Results:

_:n0 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> 
<http://xmlns.com/foaf/0.1/Person> .
_:n0 <http://xmlns.com/foaf/0.1/name> "Dan Brickley"@en .

<http://danbri.org/2008/imagemap/ivan.html#area1> 
<http://xmlns.com/foaf/0.1/depicts> _:n0 .


hmm it's not getting the primaryTopic. Maybe the .js is out of date?

Some candidate goals:

* look as much like current HTML as possible
* work with multiple tagged areas
* allow enough info to be exposed via triples to reconstruct the shapes 
over the mapped image from the RDF

> According to the latest status of the group's discussions (not the 
> syntax document as published, though), the following encoding does the 
> trick:
> 
> <div instanceof="foaf:Person"
>   property="foaf:name" content="Dan Brickley">
>   <map name="da8bb51_b" id="da8bb51_b">
>     <area id="area1"
>       shape="POLY" coords="463,662,..."
>       rev="foaf:primaryTopic" href="http://danbri.org/"/>
>   </map>
>   <span rev="foaf:depicts" resource="#area1"/>
>   <img src="2169955372_503da8bb51_b.jpg"
>      width="1024" height="770" usemap="#da8bb51_b"/>
> </div>
> 
> The reason why a separate <span> is necessary is because for many use 
> cases the special interpretation of @src is necessary, and does get a 
> special usage in RDFa (essentially, it behaves like an @about). That is 

So we can get triples that use the URI from src somehow?

> why the @rev and @resource pair could not be put on the <img> element. 
> If, instead of <img> you had used something like <object>, for example, 
> then you could also have
> 
> <div instanceof="foaf:Person"
>   property="foaf:name" content="Dan Brickley">
>   <map name="da8bb51_b" id="da8bb51_b">
>     <area id="area1"
>       shape="POLY" coords="463,662,..."
>       rev="foaf:primaryTopic" href="http://danbri.org/"/>
>   </map>
>   <object data="2169955372_503da8bb51_b.jpg"
>      width="1024" height="770" usemap="#da8bb51_b"
>      rev="foaf:depicts" resource="#area1"
>   />
> </div>
> 
> which is, actually, quite nice!

Is it legit to use <object>? do browsers understand it appropriately in 
this context?

cheers,

Dan
Received on Monday, 7 January 2008 15:16:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:20 GMT