Re: Comment on RDFa 1.1 Core: Profiles, term mappings, and URIs as literals (ISSUE-39)

Hi Richard,

On Sat, Aug 7, 2010 at 10:39 PM, Richard Cyganiak
<richard.cyganiak@deri.org> wrote:
> [...]
> Also, I don't think that the goal of @profile is to make “statements” in the
> knowledge representation sense. The goal is to establish prefix mappings and
> term mappings. RDF triples are simply the data structure for writing down
> the mappings. For this purpose it does not matter between what kind of
> brackets or quotes you stick the string -- the information needed for RDFa
> processing is there in the data structure.
> [...]

That a profile shouldn't primarily be about making statements is a
good opportunity for me to raise again my objection to using RDF as
the primary mechanism for defining prefix mappings.

I'm not saying that we shouldn't at some point allow vocabularies to
be imported and then deduce the prefix mappings from those
vocabularies. I'm also not against an import mechanism in the future
that allows us to import graphs (my RDFa parser looks for owl:imports
predicates and loads the triples).

But what I have been saying is that when it comes to something as
fundamental as profiles and prefix mappings, there needs to be a basic
way to define a profile document that does not rely on using an RDFa
parser to work out what the mappings are.

This issue was also raised on the list in relation to Michael McEvoy's
point about a simple text file of name/value pairs being sufficient:

  <http://lists.w3.org/Archives/Public/public-rdfa-wg/2010Jul/0119.html>

For some reason -- despite the prior noise on the subject! -- there
haven't yet been any responses. ;)

Regards,

Mark

--
Mark Birbeck, webBackplane

mark.birbeck@webBackplane.com

http://webBackplane.com/mark-birbeck

webBackplane is a trading name of Backplane Ltd. (company number
05972288, registered office: 2nd Floor, 69/85 Tabernacle Street,
London, EC2A 4RR)

Received on Thursday, 12 August 2010 11:13:47 UTC