Author: Claudia Wagner | Published: 19th February 2009 | RSS | LINK
Somehow I have some problems with the sioc:content property, because the fact that it is limited on plain text seems to limit me as well
I wonder how I should model for example a blog post which consists only (or mainly) of images? I can describe each image itself with foaf or exif ontology, ok. But how do I express that these images are the content of the post? sioc:embeds would be a possibility and I am using it at the moment in my extended SIOC WP exporter.
But why am I not happy with this solution?
First I have no possibility to model relations between different content items (text blocks, images, videos) and positional information (which I might need to serialize the RDF model of a post in XHTML/RDFa - seeAlso posting from Uldis) get lost during exporting a post in RDF. The triples of a post only expose that some multimedia content and some unstructured text is contained in the post. If we are looking at the HTML representation of a post, we get a richer picture. We have sections, text belonging to images and so on…
I suggest to change the range of the sioc:content property from rdfs:Literal to rdfs:Resource (or sioc:Item). This would allow to model the content of sioc:Items on a higher granularity level. For example the relations (positional relations such as sioc:next, sioc:before and argumentative relations such as sioc:arises_from, sioc:agrees_with ) between individual content items could so be exposed as well.
My second point is that the name sioc:content seems to be confusing to me. A sioc:Item can be everything stored in a sioc:Container and the sioc type module introduces container such as ImageGallery, Video Channel and so on. I wonder if a property sioc:content, which can only holds plain text, can ever expose the content of the items stored in this containers?
Maybe it would be better to rename the current sioc:content property (which has a rdfs:Literal as range) to sioc:text_content or sioc:text and have another property sioc:content which has as range rdfs:Resource.
In the end I would like to be able to express something like this: