General interaction with the module and exporting RDF data.
rod82 - January 29, 2009 - 22:55
| Project: | RDF CCK |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | scor |
| Status: | postponed (maintainer needs more info) |
Jump to:
Description
Hi there, I wanted to ask a few things, so I'll just list them below:
1) what is the best way to associate node data with RDF data (e.g. user name -> foaf:name or story body -> sioc:content, etc.).
2) once I have created new content nodes (previously associated with RDF), how do I expose their metadata in RDF on a page? What about RDFa?
I'm currently just trying to understand how to best interact with your module (and other existing RDF modules): if it is from a developer perspective or a site-admin / end-user perspective. I basically want to see how far I can go without writing code in order to get my site to be "Semantic Web compliant" using Drupal 6.
Any clarification is much appreciated!
Thanks,
R
#1
You will want to have a look at the RDF CCK module which allows you to map your node title, body and CCK fields to RDF classes and properties.
#2
Thanks for the suggestion, but I already have. It seems the module's development has halted at a dev version and from what I have seen there is no clear way to export the RDF data that is created from the user interface. While it is not related to this module, do you have any particular suggestions about the RDF CCK module and how to get the exporting to work?
Thanks,
R
#3
could you clarify whether you are talking about the RDF module or the RDF CCK module? Bear in mind that the RDF module is just an API and that most of the features are in the modules built on top of it. Make sure to check the RDF Schema module which ship with the RDF module, this one should also export some metadata about a node when you visit node/1/rdf for instance.
#4
I'm talking about the RDF CCK module that is available on the Drupal site. I'm not aware of any other version of it available elsewhere.
In any case, your suggestion of visiting node/1/rdf seems to be closer to what I want, although it didn't seem to work when I tried with the dev version of the RDF API module (it worked with the current alpha version). Any known issues there?
Basically, the mapping that you guys currently have for the dev version of the RDF API seems to be exactly what I want. What I would be missing in this case is some way of exporting the info as RDFa on a page.
I appreciate that this module is supposed to work as an API only and I'm getting to the conclusion that the extra RDFa exporting functionality I want will probably have to be something I integrate at the template level or as a node module or sth to that effect.
Any other suggestions?
Thanks,
R
#5
yes, there is no RDFa supported at the moment, simply because this must be dealt with on a theming level. Drupal 7 will support RDFa, but for Drupal 6 you will need to tweak your theme.
re RDF CCK, I'm working on a new version which I hope to release in the coming weeks.
#6
Well, thanks for the info / advice and I look forward to checking out the new version of RDF CCK. Good luck on the development!
Thanks,
R
#7
Hi again, I need a follow up on exporting RDF data.
I've installed the new release of the RDF API module (alpha5) and was trying to export the metadata for a node that has RDF mappings with node/%/rdf but it did not work. All I get is a blank RDF document with:
<?xml version="1.0" encoding="UTF-8"?>
I have setup all the permissions and have also tried re-installing the module on a fresh Drupal installation. I can also tell you that the 'rdf_resources', 'rdf_namespaces' and 'rdf_data' tables are all empty, even though I have created some content using a node type that has mappings for its fields.
Is there anything else I should be looking for?
Thanks,
R
#8
can you try with the latest dev snapshots please? make sure you use evoc 1.x and RDF CCK 2.x.
#9
Did you check your download list? The documentation says:
exported at node/*/rdf.
and my expectation was that the export code would appear in a browser window. Instead, a file appears in my download directory of choice.
#10
yes, this depends which default format you choose in the RDF settings page (RDF/XML, ntriples, json). json is the default one, and will not open in your browser by default.