RDFa export in CCK
scor - March 10, 2009 - 15:46
| Project: | RDF CCK |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
Right now the mappings defined in RDF CCK get exported at /rdf. They could also be exported as RDFa which, for now, involves patching the CCK module.
I've created a patch for CCK which allows to mint the output of CCK fields with the RDFa mappings defined in the RDF CCK module. To apply this patch, go inside your cck module directory and type patch -p0 < rdfa_cck_1.patch.
In the longer run, I plan to find a way to integrate this into the CCK module.
| Attachment | Size |
|---|---|
| rdfa_cck_1.patch | 1.77 KB |
#1
Is the patch going to be submitted to CCK as well? I'd rather roll out a dev version of CCK than patching it myself :)
#2
this won't be committed to CCK for now. It is here for those who want to try RDFa with RDF CCK.
#3
I'm relatively new to RDF and RDFa, so please excuse if this is an uninformed question.
When I used this patch, the local term for the CCK field was assigned to the property attribute instead of the external vocabulary term that I had mapped to the CCK field.
For instance, my 'name' field was using the local term("site:field_name") instead of the external vocabulary term("foaf:name").
I tweaked the content.module file to use the external vocabulary term instead, but wasn't sure whether this was the right way to do it.
Should RDFa use the local terms or the external vocab terms?
#4
thanks Linclark, you are right, it should include both. attached a new patch.
#5
If you could re-write the CCK patch to be less specific to RDF, it could have a chance of being incorporated into CCK. I would think about using drupal_alter() or something like that to create a generic hook so that all the RDF-specific stuff is done by this module when it implements the hook. Since there are only a couple places you need to jump in, this may not be too hard to do.
#6
Hello,
I don't suppose somebody would be kinda enough to post the already patched file? I'm not very experienced at command line tasks. I did try using WinMerge and had to revert back to the original cck file due to errors. I would just wait for a ckk release but it looks like this is not on the agenda so guess one way or another i have to use the patch. Thanks. Kevin
#7
@6 Here are the two modified files, content-field.tpl.php and content.module. It is better to use the patch though, because they might be updated in newer version of CCK, these are based on 6.x-2.5.
EDIT: The modified versions seem to be causing errors, although the patch was applied ok.
#8
subscribe.
#9
Subscribe