Some relations are defined in the RDF mappings but not in RDF such as skos:inScheme or skos:broader. would be good to have these in the RDF model, RDFa could be done at the worst via <meta> tags in <head>.
Some relations are defined in the RDF mappings but not in RDF such as skos:inScheme or skos:broader. would be good to have these in the RDF model, RDFa could be done at the worst via <meta> tags in <head>.
Comments
Comment #1
scor commentedmake title more generic
Comment #2
scor commentedComment #3
scor commentedtagging
Comment #3.0
scor commentedupdating OP with accurate description
Comment #4
Anonymous (not verified) commentedIn general, I believe we should to try to ensure that the different serializations of the same resource match as much as possible. This would mean it should be added to both the RDFa and the RDF model.
Comment #5
Anonymous (not verified) commentedscor mentioned in the Google Hangout, there may be a URI in RestWS for the vocabulary. We could then create the relationship between the term and vocabulary in both RDFa and rdfx_get_model and also expose rdfx_get_model info for the vocabulary at it's URI. The vocabulary itself would not be exposed in RDFa because there is no HTML page for the vocabulary.
Comment #6
mlncn commentedFunction in question is rdfx_get_rdf_model() and i'm hoping a more complete example / use case would help indicate what work needs to be done. And the RDFa work belongs to Drupal core?
Comment #6.0
mlncn commentedAdded wrapping code tags.