W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > March 2010

Re: ISSUE-1 Proposal: RDFa Profiles via @map

From: Ivan Herman <ivan@w3.org>
Date: Mon, 15 Mar 2010 07:19:12 +0100
Message-ID: <4B9DD160.4020901@w3.org>
To: Manu Sporny <msporny@digitalbazaar.com>
CC: RDFa WG <public-rdfa-wg@w3.org>
For my understanding...

1. The @map attribute would be a 'local' version of what we discussed
until now on profiles. Ie, I may not be forced to put everything into a
separate file; some sort of an @xmlns on steroids.

I see value in that

2. But to use the same attributes in the vocabulary file... I do not
really like that. It is really confusing for me. If I have a file


that is an RDFa file which uses the @map then

- if I process this file through an RDFa processor, it leads to a bunch
of triples
- if I process the very same file through an RDFa processor but via a
@profile attribute then I have a totally different interpretation of the
attributes: I do not look for RDF triple any more but have to have a
separate XML parsing looking for the @map attributes an interpret the
values for the 'invoking' RDFa data. I find it very confusing.

I also do not see what it brings us compared to what we have.


On 2010-3-15 03:43 , Manu Sporny wrote:
> This proposal outlines one potential implementation of the RDFa Profiles
> feature. It also defines @map since its use is crucial to this proposal.
> The name @map is proposed because this proposal combines
> prefixes/keywords into one list in the RDFa Processor called a "list of
> mappings" and it may follow that @map is easier to understand than
> @token or @keyword.
> Proposal
> --------
> * @xmlns is preserved and operates as it normally does in RDFa 1.0.
> * A new attribute is introduced called @map. The attribute contains
>   a set of key/value mappings. The syntax for map is the same as CSS,
>   which will make it easier to use for those already familiar with CSS.
> * @xmlns: extends the "list of mappings" in the current element scope
> * @map extends the "list of mappings" in the current element scope and
>   any document that imports the document as a RDFa Profile**1
> Examples
> --------
> Example in a regular RDFa document:
> <div map="dc: http://purl.org/dc/terms/ ;
>           Person: http://xmlns.com/foaf/0.1/Person">
>    <span property="dc:title">The @map proposal</span>
> ...
> </div>
> Example in RDFa Profile document:
> <div map="Person: http://xmlns.com/foaf/0.1/Person;
>           name: http://xmlns.com/foaf/0.1/name"> ... </div>
> Example in RDFa document that utilizes the Profile document above:
> <div profile="http://example.org/foaf-profile"
>      about="#mark" typeof="Person">
>    <span property="name">Mark Birbeck</span>
> </div>
> -- manu
> **1: This is weird - most of the other RDFa attributes are scoped to the
> element, but @map isn't in the specific case where its values are
> imported via @profile.


Ivan Herman, W3C Semantic Web Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
PGP Key: http://www.ivan-herman.net/pgpkey.html
FOAF   : http://www.ivan-herman.net/foaf.rdf
vCard  : http://www.ivan-herman.net/HermanIvan.vcf

Received on Monday, 15 March 2010 06:18:40 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:19:46 UTC