Re: Role of RDFa in 2016

Hello


> I recognize the use case for RDFa is much deeper than search engines, but
> I also suspect that in most cases when a service publishes RDFa in the
> HTML, that same service likely has made a 'cleaner' alternate serialization
> available.
>
>
No, on the contrary. RDFa is the simplest path for a publisher with an
existing web portal to disseminate structured/linked data; it only requires
to adapt the HTML generation templates, without worrying about setting up
content negociation, or an API, or a SPARQL endpoint, or changing in any
way the internal information system. So portals publishing RDFa might not
have another "cleaner" serialization available. The ELI project (
http://eur-lex.europa.eu/eli-register/about.html) has this situation, where
legal publishers in european countries (including countries with low
resources and budgets) are encouraged to disseminate legal metadata using
RDFa.
We are indeed facing the limitations you point out about mixing
presentation and data, and sometime need to create a kind of RDFa at the
top of web pages. But budgets and available competencies and resources make
RDFa an easy path for structured data publishing.

Cheers
Thomas


> --Kevin
>
>


-- 

*Thomas Francart* -* SPARNA*
Web de *données* | Architecture de l'*information* | Accès aux
*connaissances*
blog : blog.sparna.fr, site : sparna.fr, linkedin :
fr.linkedin.com/in/thomasfrancart
tel :  +33 (0)6.71.11.25.97, skype : francartthomas