Comments on: Extended WP SIOC Exporter

By: Ryan Jones

Ryan Jones — Fri, 03 Jul 2009 19:10:58 +0000

Great idea for the SIOC plugin, thanks for the great info.

By: Tales from the SIOC-o-sphere part #9 « Cloudlands

Tales from the SIOC-o-sphere part #9 « Cloudlands — Thu, 19 Mar 2009 20:12:46 +0000

[...] Wagner has published an extended version of the WordPress SIOC Exporter that also exports any semantic metadata embedded within the content of a blog [...]

By: Claudia Wagner

Claudia Wagner — Thu, 26 Feb 2009 16:46:49 +0000

Matteo,

just change the require_once path in the sioc_include.php so that it points to the arc folder included in the rdftools folder.
Both plugins should of course share one ARC2 folder. Than require_once works and no redeclare errors appear.

By: Matteo Brunati

Matteo Brunati — Sun, 22 Feb 2009 09:40:34 +0000

Hi, good idea for the plugin .)

One thing: i have on my blog also rdf tools by novack as plugin actived.
There is a problem with arc2, it returns on the rdf tools admin panel this kind error:

Cannot redeclare class arc2 in /www/dagoneye.it/blog/wp-content/plugins/rdf-tools/arc/ARC2.php on line 15

Probably with the next version of the arc framework, it works, i think…
Nice stuff

By: enore savoia

enore savoia — Sat, 21 Feb 2009 13:53:06 +0000

I just updated the WordPress SIOC exporter plugin to the new version … tnx !

ps: Why this CAPTCHA ? please think different … , is only a suggestion !

By: Patrick Murray-John

Patrick Murray-John — Fri, 20 Feb 2009 01:44:30 +0000

The way I think of it, at least in terms of web pages, is that if a piece of content is stuffed into a page and loads up and displays when you view the page, that’s a dcterms:hasPart –> sioc:embed (BTW, I like the sioc:embed, it reflects well how people are using the term ‘embed’. For example, I’ve heard people talking about ‘embedding’ an image. Not HTML language, but reflects the concept people have!)

Seems to me that any distinction between sioc:links_to and dcterms:reference is contingent on the subject in the triple. A web page will sioc:links_to, while a print publication will need the more general dcterms:references? Bibliographic Ontology might help us here. But the incorporation of links into most any document makes that break down, especially while docs bound for print include footnotes. It’s a hard problem, and we’ll need to resurrect Bakhtin to solve it satisfactorily!

sioc:topic vs. dcterms:subject, I agree, seem like a very fine line. I kinda think that we (”we” being the big semweb community) might need to encounter some more edge cases to help us tease it out. But maybe other folks out there have better insights?

By: Claudia Wagner

Claudia Wagner — Thu, 19 Feb 2009 23:32:03 +0000

Patrick,

thanks for pointing me to dcterms:hasPart. It looks really good!
Now I wonder which property would be the most appropriate to model the relation between a post and an embedded resource? sioc:embed, dcterms:hasPart, sioc:topic or something else?
I think sioc:embed is more or less equivalent with dcterms:hasPart and sioc:topic seems to be the same as dc:subject.
As sioc:embeds is not part of the sioc core, I guess I should go for dcterms:hasPart, or what do you think?

The application area of sioc:embed/dcterms:hasPart, sioc:topic/dc:subject and sioc:links_to/dc:references are not clearly seperated from my point of view. So I guess everyone can feel free to choose

By: Patrick Murray-John

Patrick Murray-John — Thu, 19 Feb 2009 19:46:31 +0000

(I followed Uldis’ repost to get here.) This looks great!

I encountered a similar question about how to represent the embedded content. Eventually I just bailed out to dcterms:hasPart — I’m curious about your thoughts on that approach.

Thanks!