clauwa.info

Few days ago I tried out the SIOC Importer for Wordpress, which is really cool. The importer requires as input a URI, which must point to an RDF graph, parses the graph for all instances of the type sioc:Post (this includes normally Blog Postings and comments) and creates new content on the target site using WordPress API calls.

The things I wondered about were:

• * the newly created resources, don’t include any machine-understandable information about their origin. (only the sioc:content text refers to the original source of the posting)
• * the resource should be a copy of the original postings, but e.g. the author of the posting is not copied. Only the content of the posting is copied.
• * why is the resource content copied and not embedded?

All in all I was thinking that for some use cases (e.g. reblogging) it would be better to embed external resources into the sioc:content of the automatically created sioc:Post Skeleton. This would have the advantage that the instances of the resource to share stay synchronized and that the origin of the displayed content would be machine-understandable.

The SIOC Core Ontology provides for resources of the type sioc:Item the property sioc:content. But this property only contain literals as value.  Maybe the sioc:attachment property can be used to expose that external resources should be embedded into a sioc:Post or proposed properties (such as sioc:embeds) can be used.