W3C home > Mailing lists > Public > public-rdfa@w3.org > November 2012

Re: PHP Library EasyRdf to support RDFa in version 0.8.0

From: Stéphane Corlosquet <scorlosquet@gmail.com>
Date: Wed, 21 Nov 2012 11:56:21 -0500
Message-ID: <CAGR+nnEze8B0Do0ZXawRQ=UvdZEqEfTZxQpHTXspQb3k_gm_VQ@mail.gmail.com>
To: Nicholas Humfrey <Nicholas.Humfrey@bbc.co.uk>
Cc: public-rdfa@w3.org, Olivier Thereaux <Olivier.Thereaux@bbc.co.uk>
Hi Nicholas,

On Wed, Nov 21, 2012 at 10:50 AM, Nicholas Humfrey <
Nicholas.Humfrey@bbc.co.uk> wrote:

> Hello,
>
> After many weeks of work I have just merged RDFa 1.1 support into the
> master
> branch of EasyRdf:
> http://github.com/njh/easyrdf/


Fantastic, this great news. I see you're using composer so that should ease
its adoption.


>
>
> There is still quite a bit more work to do until it is officially released
> but I am making the announcement now because I have gone over 90% test
> coverage for XHTML5+RDFa1.1 test suite.
>
> When I started writing the RDFa parser I was fairly shocked at how
> incredibly complex the set of rules are for writing a parser. The number of
> similar rules with subtle differences is very confusing. While there are
> only a limited number of people actually need to write their own RDFa
> parsers, I wouldn't underestimate how this complexity is limiting adoption
> of RDFa in general.
>
> Even after writing a parser, I don't think I could look at an RDFa document
> and know for sure what triples are that would be generated for the
> different
> permutations of attributes.
>

Part of this is the legacy that RDFa 1.1 is carrying due to backward
compatibility constraints. If we had to start over, there are some features
which we probably wouldn't want to include (e.g. the magic of some of the
attributes like about) and that would make the parser simpler.

Note that we encourage certain practices in order to make the authoring
experience easier, RDFa Lite is one example, also using @resource instead
of @about, using @property everywhere and avoid @rel. These are to make the
authoring easier, but of course as a parser implementer, you cannot take
these shortcuts and have to follow the processing steps carefully...

Steph.


>
> It would have been incredibly difficult to write a compliant parser without
> the test suite - so thank you very much for providing that!
>
>
> nick.
>
>
> http://www.bbc.co.uk/
> This e-mail (and any attachments) is confidential and may contain personal
> views which are not the views of the BBC unless specifically stated.
> If you have received it in error, please delete it from your system.
> Do not use, copy or disclose the information in any way nor act in
> reliance on it and notify the sender immediately.
> Please note that the BBC monitors e-mails sent or received.
> Further communication will signify your consent to this.
>
>
>


-- 
Steph.
Received on Wednesday, 21 November 2012 16:56:51 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:15:09 UTC