I designed over the last weekend the Info Service Ontology (see the graphic above). The initial intention behind designing this ontology was to add some knowledge re. linked websites from different information services (see the discussion in the prv-vocab mailing list about defining the term ‘information service‘), e.g. Wikipedia or MusicBrainz, in semantic graphs (as proposed in the FOAF wiki), e.g.
a foaf:Document ;
is:info_service isi:musicbrainz .
RDF/Turtle representation of a webpage linked to an Information Service
The Info Service Ontology consists of a basic is:InfoService concept (which could maybe related to prv:DataProvidingService, bibo:Collection, sioc:Space or void:Dataset instances) and some additional ones for describing such an information service (currently: is:InfoServiceQuality, is:InfoServiceType and is:InfoServiceContributorType – the specific individuals are currently only proof-of-concept examples).
The main hook re. specific websites from an information service is is:info_service, which associates an is:InfoService instance to e.g. a owl:Thing (or e.g. sub class of owl:Thing, e.g. foaf:Document) instance (e.g. a website link).
Furthermore, I defined some is:InfoService individuals, especially isi:musicbrainz (see the graphic above and code below) as proof-of-concept example. Therefore, I used also some category definitions from DBpedia (important is also the property is:main_subject for associating a main subject of an Information Service).
@prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix is: <http://purl.org/ontology/is/core#> .
@prefix ist: <http://purl.org/ontology/is/types/> .
@prefix isct: <http://purl.org/ontology/is/ctypes/> .
@prefix isq: <http://purl.org/ontology/is/quality/> .
@prefix isi: <http://purl.org/ontology/is/inst/> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
rdf:type is:InfoService ;
rdfs:isDefinedBy isi: ;
dc:description "An open content music database. Modelled here as information service."@en ;
dc:title "MusicBrainz"^^xsd:string ;
dcterms:subject <http://dbpedia.org/resource/Category:Metadata_registry> ,
ist:encyclopedia , ist:knowledge_base ;
is:main_subject <http://dbpedia.org/resource/Category:Music> ;
foaf:homepage <http://musicbrainz.org/> .
RDF/Turtle representation of MusicBrainz modelled as Information Service
Please feel to add comments, critics and suggestions re. which properties might be useful for describing an info service.
Planned extensions are:
- enabling multiple info service quality ratings, e.g. by using the Review Ontology, which may come from different info service rating agencies (e.g. modeled with foaf:Agent as hook) so that the customer of such rating could select the info service rating agency of his/her choice
- defining a is:recommendation property
- add further Information Service quality properties, this should maybe done in another sub ontology, because rating information quality could be somehow complex and be realized on different levels of complexity (see the ongoing discussion on the prv-vocab mailing list); this information quality classification could probably be used for a reference implementation of an Info Service Quality Ontology
With the is:info_service property as a relation to an Information Service description, it should be possible, e.g. to enable users the opportunity to choose their preferred Information Services as data sources for their knowledge base (or whatever) by selecting the different properties of such an Information Service.
That’s all for the moment 😉
PS: I would also give Olaf Hartig props for clarifying the term ‘Information Service‘ on which this ontology is grounded. Thank you very much (again) Olaf!