Additions to SIOC-Types Module Classes for WishList and OfferList

[kidehen]

All,

Strangely we don't have the ability to define WishList and OfferList
item containers in SIOC.

Here are RDF/XML snippets re. the classes that I am recommending for
incorporation:

<owl:Class rdf:about="http://rdfs.org/sioc/types#WishList">
<rdfs:label xml:lang="en">Wish List</rdfs:label>
<rdfs:comment xml:lang="en">
Describes a collection things sought by an agent. Ideal integration
point for
objects from a WishList ontology or vocabulary.
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://rdfs.org/sioc/ns#Container"/>
<rdfs:isDefinedBy rdf:resource="http://rdfs.org/sioc/types#"/>
<rdfs:seeAlso rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
</owl:Class>

<owl:Class rdf:about="http://rdfs.org/sioc/types#OfferList">
<rdfs:label xml:lang="en">Wish List</rdfs:label>
<rdfs:comment xml:lang="en">
Describes a collection of goods and services provided by vendors.
Ideal integration point for
GoodRelations Ontology Objects where sioc:Items would be linked via
rdf:type to GoodRelations Ontology objects such as <http://
www.heppnetz.de/ontologies/goodrelations/v1#BusinessEntity> .
SeeAlso: http://www.heppnetz.de/ontologies/goodrelations/v1
</rdfs:comment>
<rdfs:subClassOf rdf:resource="http://rdfs.org/sioc/ns#Container"/>
<rdfs:isDefinedBy rdf:resource="http://rdfs.org/sioc/types#"/>
<rdfs:seeAlso rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
</owl:Class>

Kingsley

Kingsley

[mh...@computer.org]

Hi Kingsley,
Good to see links between SIOC and GoodRelations evolving :-)

Please note that the authoritative base URI of GoodRelations is

http://purl.org/goodrelations/v1

and not (i.e., no longer)

http://www.heppnetz.de/ontologies/goodrelations/v1

http://purl.org/goodrelations/v1 is also the one supported by Yahoo
SearchMonkey.

The only reason for http://www.heppnetz.de/ontologies/goodrelations/v1
not disappearing completely from the Web is that purl.org allows only
very limited control over the redirect. So we cannot server the
GoodRelations ontology (RDF/XML) nor the documentation (XHTML) under
the purl.org namespace.

So please (everybody ;-)): Make sure you are using GoodRelations
elements in the purl.org namespace only.


Best wishes
Martin Hepp

On Mar 14, 5:40 pm, kidehen <kide...@openlinksw.com> wrote:
> All,
>
> Strangely we don't have the ability to define WishList and OfferList
> item containers in SIOC.
>
> Here are RDF/XML snippets re. the classes that I am recommending for
> incorporation:
>
> <owl:Class rdf:about="http://rdfs.org/sioc/types#WishList">
> <rdfs:label xml:lang="en">Wish List</rdfs:label>
> <rdfs:comment xml:lang="en">
> Describes a collection things sought by an agent. Ideal integration
> point for
> objects from a WishList ontology or vocabulary.
> </rdfs:comment>
> <rdfs:subClassOf rdf:resource="http://rdfs.org/sioc/ns#Container"/>
> <rdfs:isDefinedBy rdf:resource="http://rdfs.org/sioc/types#"/>
> <rdfs:seeAlso rdf:resource="http://xmlns.com/foaf/0.1/Agent"/>
> </owl:Class>
>
> <owl:Class rdf:about="http://rdfs.org/sioc/types#OfferList">
> <rdfs:label xml:lang="en">Wish List</rdfs:label>
> <rdfs:comment xml:lang="en">
> Describes a collection of goods and services provided by vendors.
> Ideal integration point for
> GoodRelations Ontology Objects where sioc:Items would be linked via

> rdf:type to GoodRelations Ontology objects such as <http://www.heppnetz.de/ontologies/goodrelations/v1#BusinessEntity> .

[Alexandre Passant]

Hi Kingsley,

Could you please add the feature in the wiki using the new process
[1], thanks.
One issue I see with your proposal is that any item contained in a
wishlist will be instanciated as a sioc:Item (due to the
sioc:container_of relationship), and I don't really like things like
DVDs, records, cars, etc. being instances of such classes.

Yet, indeed, the container itself is valuable.

Best,

Alex.

[1] http://groups.google.com/group/sioc-dev/browse_thread/thread/df7a1f8369898bd3


Le 14 mars 09 à 16:40, kidehen a écrit :

--
Alexandre Passant
Digital Enterprise Research Institute
National University of Ireland, Galway
:me owl:sameAs <http://apassant.net/alex> .

[Simon Reinhardt]

Hi Alexandre,

On Mar 16, 8:12 am, Alexandre Passant <alexandre.pass...@deri.org>
wrote:

> One issue I see with your proposal is that any item contained in a  
> wishlist will be instanciated as a sioc:Item (due to the  
> sioc:container_of relationship), and I don't really like things like  
> DVDs, records, cars, etc. being instances of such classes.

John made a similar remark the other day:
http://groups.google.com/group/sioc-dev/browse_thread/thread/da8a2d4c1f4adf38/c81cd3f85f899eee?#c81cd3f85f899eee
But to me it seems like this completely contradicts the decision made
in http://groups.google.com/group/sioc-dev/browse_thread/thread/132eaa291d93fb73/e8388393ca167985

Regards,
Simon

[Breslin, John]

Hi all -

Added WishList and OfferList - I made the descriptions quite short but I suggest we look at making a specification file for the Types module like we do for the main namespace where we could put in extended comments similar to those below.

My other comment is that I didn't put the seeAlso to Agent as the seeAlso's (for want of a better syntax to describe what a Container or Forum should contain) normally point to the type of Item that the Container holds... When we get a better way of suggesting usages of related vocabularies we can change from this convention.

Regarding my thoughts and Alex's thoughts that real-world Items shouldn't be in Containers, we can leave that to the discretion of the implementer but there will be pages describing these items - e.g. on Amazon, a page describing a book or CD has very similar structures to a YouTube page or a Flickr page - it is just that the product is the content Item and the discussion is attached to the page about that product.

Thanks,

John.
--
Dr. John Breslin

National University of Ireland, Galway

http://www.johnbreslin.org/
john.b...@nuigalway.ie

________________________________

[Simon Reinhardt]

On Mar 16, 1:33 pm, "Breslin, John" <john.bres...@nuigalway.ie> wrote:
> My other comment is that I didn't put the seeAlso to Agent as the seeAlso's (for want of a better syntax to describe what a Container or Forum should contain) normally point to the type of Item that the Container holds...  When we get a better way of suggesting usages of related vocabularies we can change from this convention.

Normally in OWL I'd do it like this...

For situations when you want to allow only one sort of thing for the
value of the property of a certain class, do:
sioct:Wiki a owl:Class ;
rdfs:subClassOf [
a owl:Restriction ;
owl:onProperty sioc:container_of ;
owl:allValuesFrom sioct:WikiArticle
] .

When you want to allow several different sorts of things in the range
but only those, do:
xyz a owl:Class ;
rdfs:subClassOf [
a owl:Restriction ;
owl:onProperty sioc:container_of ;
owl:allValuesFrom [
a owl:Class ;
owl:unionOf (:SomeClass :AnotherClass)
]
] .

When you want to suggest a sort of thing (probably from a different
vocabulary) that can be used in this situation, do:
sioct:WishList a owl:Class ;
rdfs:subClassOf [
a owl:Restriction ;
owl:onProperty sioc:container_of ;
owl:someValuesFrom goodrelations:BusinessEntity
] .

Not the most readable syntax and I'm not sure how useful those
statements will actually be but it's a possible way.

Regards,
Simon

[kidehen]

Alex,

On Mar 16, 4:12 am, Alexandre Passant <alexandre.pass...@deri.org>
wrote:

> Hi Kingsley,
>
> Could you please add the feature in the wiki using the new process  
> [1], thanks.
> One issue I see with your proposal is that any item contained in a  
> wishlist will be instanciated as a sioc:Item (due to the  
> sioc:container_of relationship), and I don't really like things like  
> DVDs, records, cars, etc. being instances of such classes.

Why isn't a DVD a sioc:Item ? Which is an owl:Thing? All you need to
do is qualify the sioc:Item with an rdf:type link to an ontology that
defines a class for describing consumer goods for instance.

I am just modelling the fact that a "WishList" is a collection of
"Things".

That said, what's you alternative modelling suggestion? The more eyes
the better as this is an important tweak to SIOC.


Kingsley

>
> Yet, indeed, the container itself is valuable.
>
> Best,
>
> Alex.
>

> [1]http://groups.google.com/group/sioc-dev/browse_thread/thread/df7a1f83...

[Alexandre Passant]

Le 16 mars 09 à 18:27, kidehen a écrit :

>
> Alex,
>
> On Mar 16, 4:12 am, Alexandre Passant <alexandre.pass...@deri.org>
> wrote:
>> Hi Kingsley,
>>
>> Could you please add the feature in the wiki using the new process
>> [1], thanks.
>> One issue I see with your proposal is that any item contained in a
>> wishlist will be instanciated as a sioc:Item (due to the
>> sioc:container_of relationship), and I don't really like things like
>> DVDs, records, cars, etc. being instances of such classes.
>
> Why isn't a DVD a sioc:Item ? Which is an owl:Thing? All you need to
> do is qualify the sioc:Item with an rdf:type link to an ontology that
> defines a class for describing consumer goods for instance.
>

To my mind, sioc:Item are on-line things.
A flash video file can be a sioc:Item, a webpage describing a DVD as
well, but the DVD, that you can buy in a store, is imho no more an
online object, i.e. a sioc:Item.
If everything becomes a sioc:Item, what's, at the end, its difference
with owl:Thing ?

> I am just modelling the fact that a "WishList" is a collection of
> "Things".

I agree, but currently container_of is a collection of Items

>
>
> That said, what's you alternative modelling suggestion? The more eyes
> the better as this is an important tweak to SIOC.

Well, I agree on the container, not sure yet how to represent the
inclusion of the item.

But as John suggested (if I understood well), an option is indeed to
have:

:x a sioc:Container ; a sioct:WishList ;
container_of :coolDVDPage .

:coolDVDPage a sioc:Item ;
sioc:topic :coolDVD .

:coolDVD a foo:DVD .

There's one more path in the graph, but that sounds more coherent to me.

Alex.

[mh...@computer.org]

Dear John, all:

Note that GoodRelations has also detailed support for wish lists using
gr:seeks.

Basically, you can describe what you want at the same level of
granularity and using the same elements as what you want to sell.

See

http://www.ebusiness-unibw.org/wiki/GoodRelationsSeeks

for details.

Best
Martin