Re: ISSUE-1: Format of the profile document

On 03/11/10 13:01, Mark Birbeck wrote:
> Sounds like a great meeting, sorry I missed it.

We missed having you there as well. :)

> So RDF or not RDF is the first question to resolve -- 
> CORS, JSONP, and so on, come next. :)

(co-chair hat off - opinionated rant to follow) :)

I would be very surprised if we settled on anything other than RDF. We
have these mechanisms (RDF and RDFa) that were designed to express
exactly what we need (a vocabulary document that is both machine and
human readable) in a fairly succinct manner that re-uses the same
code-path that we've designed and tested many times over, and we're
discussing another slightly more succinct mechanism for marking up RDFa
profiles.

I don't think the question is whether or not we are capable of inventing
a new, more succinct mechanism for markup of RDFa profiles. We are most
certainly capable and could do so if necessary.

The big issue with going with anything other than RDF and RDFa is the
added complexity to the RDFa Processors and the added burden on authors
to understand yet one more markup mechanism for utilizing RDFa.

If we pick something that is not RDF and RDFa, we are adding unnecessary
complexity and authoring burden to a system that is already considered
on the edge of being painfully complex for RDFa processor developers and
difficult to understand for new semantic web authors.

Please, let us not pile on more that web authors have to learn to use
RDFa. I just don't see how creating a new RDFa profile markup mechanism
moves the web forward.

-- manu

-- 
Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: PaySwarming Goes Open Source
http://blog.digitalbazaar.com/2010/02/01/bitmunk-payswarming/

Received on Thursday, 11 March 2010 19:00:22 UTC