Role of RDFa in 2016

Dear All,

Although I feel like I will be flamed for this question, I was 
interested in hearing some opinions about the role of RDFa vs JSON-LD 
(embedded in the HTML header, let's say) in HTML now that the latter has 
become more accepted, at least when it comes to one major search engine. 
  Has that weakened the use case for, or role of, RDFa?

To ask a broad question: Who/What consumers make regular use of RDFa 
(because there is no alternate/easy serialization to obtain)?

To ask a slightly more targeted question, if you publish a data service 
that responds to content-negotiation (and which can embed JSON-LD in the 
header and which can also provide rel="alternate" links in the header), 
is it reasonable to conclude that RDFa is overkill in such a scenario?

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.

--Kevin

Received on Tuesday, 4 October 2016 02:31:58 UTC