W3C home > Mailing lists > Public > public-lod@w3.org > July 2012

Re: How to model the content from a document?

From: Leyla Jael García Castro <leyla.jael.garcia@gmail.com>
Date: Thu, 5 Jul 2012 15:21:12 +0100
Message-ID: <CAD=KBZJEt_rzj_kazTL75uN-MjN+j=Y7fv5rqp28JSNz+7KNhA@mail.gmail.com>
To: Sebastian Hellmann <hellmann@informatik.uni-leipzig.de>
Cc: Alan Ruttenberg <alanruttenberg@gmail.com>, "public-lod@w3.org" <public-lod@w3.org>
Hi Sebastian, Alan, Hans, all,

I am working on research-articles rdfication; please take a look at [1] and
[2]. We are rdfing and semantically annotating the open subset of PubMed
Central; the rdfication process includes the content not just the structure.

We have had some discussion about this rdfication; there have been some
comments about the property used to model the text contained in the
paragraphs. Initially, we used rdfs:comment; suggestions were more or less
"change it and find a better property". I have so far explored bibo:content
which is deprecated so we do not want to use it, rdf:value which still
seems to be kind of general, c4o:hasContent, and sioc:content. As there is
not a clear consensus, I am trying to figure out what people out there find
easier and natural.

What Sebastian suggested in his previous email looks fine but if the
ontology is changing right now, it is probably not a good time. I will keep
an eye on it. @Sebastian, could you please let me know when the version 2.0
has been released?

Any suggestions about what property suits better?



[1] García A., García Castro, L.J . A Translational Model for Representing
Research Articles <http://dl.acm.org/citation.cfm?id=2166904>. In
Proceedings of 4th International Semantic Web and Application Tools for
Life Sciences Workshop. 2011. London, UK
[2] García A., García Castro, L.J., McLaughlin, C., Flager, S. RDFising
PubMed Central. In Proceedings of Bio-Ontologies. 2012. Long Beach, CA,
[bibo] http://bibliontology.com
[c4o] http://purl.org/spar/c4o
[sioc] http://sioc-project.org/

On Thu, Jul 5, 2012 at 11:37 AM, Sebastian Hellmann <
hellmann@informatik.uni-leipzig.de> wrote:

> Hi Alan,
> you are right. That is probably the correct question to answer lj's query.
> lj, do you have a use case or a specific application in mind?
> What kind of queries do you want to answer with the model and the data you
> have?
> All the best,
> Sebastian
> Am 05.07.2012 01:10, schrieb Alan Ruttenberg:
>> What are you trying to accomplish - how would you decide one solution is
>> better than some other?
>> On Tuesday, July 3, 2012, Leyla Jael García Castro wrote:
>>  Hi all,
>>> I am modelling the structure and content of document. I am using DoCO (
>>> http://purl.org/spar/doco<http**://www.essepuntato.it/lode/**
>>> http://purl.org/spar/doco<http://www.essepuntato.it/lode/http://purl.org/spar/doco>
>>> >)
>>>  for the structure, i.e. Section, Paragraph, etc.
>>> Now I need to model the actual content in a paragraph, meaning the text
>>> in
>>> it. Here an example:
>>> <myDocumentURI> pattern:contains [ a doco:Section
>>> ; pattern:contains [ a doco:Paragraph
>>>   ; -content property- "This is the text in the paragraph." ] ] .
>>> What would be the best approach to do that? *bibo:content* (
>>> http://bibliontology.com/) is deprecated so I do not want to use that
>>> one; the recommendation there is to use *rdf:value*, that would be an
>>> alternative. *sioc:conten*t is another alternative. It could also be *
>>> c4o:hasContent* (http://purl.org/spar/c4o). I guess there are also other
>>> alternatives out there.
>>> Which one would be the best alternative? Any suggestions?
>>> Thanks so much,
>>> lj
> --
> Dipl. Inf. Sebastian Hellmann
> Department of Computer Science, University of Leipzig
> Events: http://wole2012.eurecom.fr (*Deadline: July 31st 2012*)
> Projects: http://nlp2rdf.org , http://dbpedia.org
> Homepage: http://bis.informatik.uni-**leipzig.de/SebastianHellmann<http://bis.informatik.uni-leipzig.de/SebastianHellmann>
> Research Group: http://aksw.org
Received on Thursday, 5 July 2012 14:22:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:23 UTC