Re: Press.net News Ontology

Hi Bernard
Many of the items on Bobs list we have done for good reason either for
specialisation of the class, or for contract binding.
For example pns:Person inherits from foaf:Person as we wanted to enhance the
parent class, and make relationships to other entities in the model,
similarly for Location, and Organization. But of course inference would
result in the foaf statements being published too.
Again the label / comment properties are subproperties of rdfs:label
specifically for contract binding reasons.

Thanks for pointing out the time namespace , I will fix it :)
Writh respect to tagging, we are aware of a number of public domain tagging
ontologies, but none of them have become the defacto tag ontology (as foaf
has in its domain). As one emerges then I imagine we would want to inherit
from it. But right now it didnt seem sensible.

I will have a look at the bio ontology for birth/death - I was not aware of
it.

best regards
Paul



On Thu, Sep 8, 2011 at 6:32 PM, Bernard Vatant
<bernard.vatant@mondeca.com>wrote:

> Adding to Bob's list with which I fully agree
>
> In http://data.press.net/ontology/stuff/ the namespace
> http://www.w3.org/TR/owl-time/ used for time ontology is not correct.
> http://www.w3.org/TR/owl-time/Instant is 404. Bing.
>
> The time ontology is indeed specified by http://www.w3.org/TR/owl-time
> But the namespace is http://www.w3.org/2006/time#
>
> ... speak about good URI practice in W3C specs ;-)
>
> Bob is using cute prefixes pns, pna etc.
> I'm using them as "recommended prefixes" at
> http://labs.mondeca.com/dataset/lov/ where I just started adding them.
> (not quite sure if they are in the right vocabulary space, though ...)
>
> Best
>
> Bernard
>
> 2011/9/8 Bob Ferris <zazi@smiy.org>
>
>> Hi Jarred,
>>
>> at a first glance, here are my remarks:
>>
>> 1. pne:Event, pne:sub_event seem to be a bit duplicated. I guess,
>> event:Event, event:sub_event are enough.
>>
>> 2. pne:title can be replaced by, e.g., dc:title.
>>
>> 3. pns:Person can be replaced by foaf:Person.
>>
>> 4. pns:Organization can be replaced by foaf:Organization.
>>
>> 5. pns:worksFor can be replaced by rel:employedBy [1].
>>
>> 6. pns:Lcoation can be replaced by geo:SpatialThing
>>
>> 7. Re. the tagging terms, I would recommend to have a look at the Tag
>> Ontology [2] or similar (see, e.g., [3])
>>
>> 8. Re. biographical events I would recommend to have a look at the Bio
>> Vocabulary [4], e.g., bio:birth/bio:death.
>>
>> 9. pns:label can be replaced by dc:title (or rdfs:label).
>>
>> 10. pns:comment can be replaced by dc:description (or rdfs:comment).
>>
>> 11. pns:describedBy can be replaced by wdrs:describedby [5].
>>
>> 12. Re. bibliographic terms I would recommend to have a look at the Bibo
>> Ontology [6], e.g., bibo:Image (or foaf:Image), or the FRBR Vocabulary [7],
>> e.g., frbr:Text.
>>
>> 13. pna:hasThumbnail can be replaced by foaf:thumbnail.
>>
>> ...
>>
>> Please help us to create 'shared understanding' by reutilising terms of
>> existing Semantic Web ontologies.
>>
>> Cheers,
>>
>>
>> Bo
>>
>>
>> [1] http://purl.org/vocab/**relationship/employedBy<http://purl.org/vocab/relationship/employedBy>
>> [2] http://www.holygoat.co.uk/**projects/tags/<http://www.holygoat.co.uk/projects/tags/>
>> [3] http://answers.semanticweb.**com/questions/1566/**
>> ontologyvocabulary-and-design-**patterns-for-tags-and-tagged-**data<http://answers.semanticweb.com/questions/1566/ontologyvocabulary-and-design-patterns-for-tags-and-tagged-data>
>> [4] http://purl.org/vocab/bio/0.1/
>> [5] http://www.w3.org/2007/05/**powder-s#describedby<http://www.w3.org/2007/05/powder-s#describedby>
>> [6] http://purl.org/ontology/bibo/
>> [7] http://purl.org/vocab/frbr/**core# <http://purl.org/vocab/frbr/core#>
>>
>>
>> On 9/8/2011 3:48 PM, Jarred McGinnis wrote:
>>
>>> Hello all,
>>>
>>> The Press Association has just published our first draft of a 'news'
>>> ontology (_http://data.press.net/**ontology_<http://data.press.net/ontology_>).
>>> For each of the ontologies
>>> documented, we've included the motivation for the ontologies as well as
>>> some of the design decisions behind it. Also, you can get the rdf or ttl
>>> by adding the extension. For example,
>>> http://data.press.net/**ontology/asset.rdf<http://data.press.net/ontology/asset.rdf>
>>> <http://**data.press.net/ontology/asset.**rdf<http://data.press.net/ontology/asset.rdf>
>>> >gives
>>>
>>> you the ontology described at http://data.press.net/**ontology/asset/<http://data.press.net/ontology/asset/>..
>>>
>>> Have a look at the ontology and tell us what you think. We think it is
>>> pretty good but feel free to point out our mistakes. We will fix it. Ask
>>> why we did it one way and not another. We will give you an answer.
>>>
>>> Paul Wilton of Ontoba has been working with us at the PA and has spelled
>>> out a lot of the guiding principles of this work at
>>> http://www.ontoba.com/blog.
>>>
>>> The reasons behind this work were talked about at SemTech 2011 San
>>> Fransisco:
>>> http://semtech2011.**semanticweb.com/sessionPop.**
>>> cfm?confid=62&proposalid=4134<http://semtech2011.semanticweb.com/sessionPop.cfm?confid=62&proposalid=4134>
>>> <http://semtech2011.**semanticweb.com/sessionPop.**
>>> cfm?confid=62&proposalid=4134<http://semtech2011.semanticweb.com/sessionPop.cfm?confid=62&proposalid=4134>
>>> >
>>>
>>> Looking forward to hearing from you,
>>>
>>> *Jarred McGinnis, PhD*
>>>
>>
>>
>>
>
>
> --
> *Bernard Vatant
> *
> Vocabularies & Data Engineering
> Tel :  + 33 (0)9 71 48 84 59
>  Skype : bernard.vatant
>
> --------------------------------------------------------
>
> *Mondeca**          **                   *
> 3 cité Nollez 75018 Paris, France
> www.mondeca.com
> Follow us on Twitter : @mondecanews <http://twitter.com/#%21/mondecanews>
>
>