Problem/Motivation
Currently, RDF module handles both the mapping functionality and the RDFa output. The only way to turn off RDFa is to turn off the module. However, if we are going to depend on the mapping functionality for JSON-LD, it's foreseeable that a site would want JSON-LD and not RDFa, so these need to be independent.
Fago touched on this in an issue in the D7 cycle, #575508: building RDFa support on centralized metadata.
Proposed resolution
Both the RDFa placement functionality of RDF module and the mapping functionality will be shifting significantly based on open issues, for example:
RDFa placement
Mapping
#1791678: Change the way RDF mappings are stored
#1778410: Throw exception when RDF namespaces collide
It should be reasonably easy to maintain the development of these as two separate modules. We will then need to create an upgrade path for any sites that have RDF module enabled in Drupal 7, moving the mapping to the mapping module and simply turning RDFa module on.
Comments
Comment #9
quietone commentedComment #13
smustgrave commentedWith RDF moving out of core and into https://www.drupal.org/project/rdf.
Brought this up on d1readiness channel and agreed we can close out.
If still a valid task please reopen under the contrib module