Difference between revisions of "Namespace"

From OpenOrg
Jump to: navigation, search
(Predicates relating an organisation to a dataset)
(Misc)
Line 161: Line 161:
  
 
It should only be treated as a rough guide. (TODO; link to how to describe quantative & qualative  location features).
 
It should only be treated as a rough guide. (TODO; link to how to describe quantative & qualative  location features).
 +
 +
=== oo:access ===
 +
 +
This relates a place (geo:SpatialThing) with a text description of how to access this thing. It may be that there is limited wheel chair access, a certain entrance is required or any other access information to tell a person planning to visit this place.
  
 
=== oo:twitterHashtag ===
 
=== oo:twitterHashtag ===

Revision as of 13:03, 14 February 2011

For now the open org namespace: http://purl.org/openorg/ directs to this page, as we plan the vocab. This is not intended to provide a complete ontology, but rather to provide extensions to existing schemes which we find we need to publish organisation data.

The recommended prefix is "oo".

Feedback to cjg@ecs.soton.ac.uk

Dataset validity dates

oo:bestBefore

Sub-property of 'dcterms:date'. Relate a dataset or document to the date after which the publisher recommends it should be treated with caution. For example a resturant may publish a menu but want to warn people that after year it might be a bit wrong, but is still potentially useful. When ordering a take away, last year's menu is better than no menu at all, but you should still be warned that it might be out of date.

This is primarily aimed at assisting humans consume the results of this data, but it may also be used as a filter to keep potentially incorrect data out of a SPARQL database.

It is intended to apply to Datasets and Documents, but this is not enforced.

oo:doNotUseAfter

Sub-property of 'dcterms:date'. Relate a dataset or RDF document to the date after which the publisher recommends it should not be used as anything other than historical data.

Contacts and Corrections

dcterms only describes creators and so forth. It is useful to also list who to ask questions about a resource or dataset, and how to make corrections.

oo:contact

A mechanism of contacting someone who knows about this resource. Suggested targets of this property are a foaf:Agent, a Document (eg. the webpage listing contact methods), a vcard address or a mailto: URI.

oo:corrections

A sub-property of oo:contact indicating a route to have corrections made to data relating to this resource. Intended for use on a dataset, but it may be used on any URI -- for example you may use it to indicate that certain records in a dataset have different people to contact them to get it fixed.

Press info

These are used by the Press Info recipe to extend FOAF.

Linked Open Data

The following URIs may me used to indicate that a dataset conforms to a certain standard of open linked data:

TODO: when we make a schema for this, link these logos with foaf:logo ? http://lab.linkeddata.deri.ie/2010/lod-badges/

http://purl.org/openorg/opendata-1-star
http://purl.org/openorg/opendata-2-star
http://purl.org/openorg/opendata-3-star
http://purl.org/openorg/opendata-4-star
http://purl.org/openorg/opendata-5-star

Use with dcterms:conformsTo eg.

<void:Dataset rdf:about="....">
   <dcterms:title>My Dataset</dcterms:title>
   <dcterms:conformsTo rdf:resource="http://purl.org/openorg/opendata-5-star" />
</void:Dataset>

IMPORTANT : You don't even get one star until you have an open license.

Features of Places

oo:hasFeature

Range: geo:SpatialThing. Domain: oo:Feature.

Associate something geospatial with a feature which it has. The feature may be anything the producer of the dataset considers relevant, but it is unique to that place, the type of the feature is identified by the rdf:type of the feature, which should be a subclass of oo:Feature. The feature can optionally have other properties, describing it's quantity and quality, restrictions and availability etc. A dcterms:description may be added to provide a textual description of the feature, if the rdfs:label of the feature type is not enough. See Places for more information.

TODO: Defined how to describe things like number of carparking spaces, or capacity of a room for a seated audience, vs people standing up.

oo:lacksFeature

Range: geo:SpatialThing. Domain: oo:Feature.

Same syntax as hasFeature but this indicates the place does not (currently) have the feature. Generally the feature will only have a type, but it may have more properties if it's a feature that is only currently unavailable. For features like "Wheelchair Access", mentioning a lack is very useful!

oo:Feature

The class of all features a place may have. A feature is usually something that helps decide of a place is suitable for a specific purpose. It could be "has a cashpoint", "has parking for 100 cars" or "haunted".

TODO: Defined a sub section in openorg (or elsewhere) to provide a vocab of useful features.

Predicates relating an organisation to a dataset

oo:profile

Relate an organisation (or other thing) to an RDF document describing it. For people this may be a PersonalProfileDocument. It suggested that this document describe the general foaf and vcard links, plus links to datasets about this thing.

oo:publications

Relate an organisation (or other thing) to a dataset describing some of its publications. Nb. this does not mean that the dataset happens to contain publications of the organistation, its a dataset which is primarily about publications of this organisation.

Additional statements can be used to describe the structure and disposition of the dataset.

oo:pressinfo

Connect the URI of an organisation (or other thing) to a dataset (or document) which contains information useful to the press, such as who is available to be contact on various subjects, photo collections, and other items forming a digital press-pack. (open org page planned)

oo:places

Connect the URI of an organisatin (or other thing) to a dataset (or document) describing places relevant to the organisation, including (but not limited to) sites, buildings and rooms.

If the description is based on the Places recommendations on this wiki, you can indicate that with

<rdf:Description rdf:about="...my-org...">
  <oo:places rdf:resource="...places-dataset...">
</rdf:Description>
<rdf:Description rdf:about="...places-dataset...">
  <dct:conformsTo rdf:resource="http://openorg.ecs.soton.ac.uk/wiki/Organisational_Structure" />
</rdf:Description>

oo:dataCatalog

Relate an organisation (or other thing) to a data catalog related to that thing. The catalog may be a

<rdf:type rdf:resource="http://www.w3.org/ns/dcat#Catalog"/>

oo:structure

Relate an organisation to a dataset which describes the structure of the organisation. If the description is based on the Organisational Structure recommendations on this wiki, you can indicate that with

<dct:conformsTo rdf:resource="http://openorg.ecs.soton.ac.uk/wiki/Organisational_Structure" />

(see 'places' above for a full example).

Classes to indicate a type of dataset

These give an indication of the primary content of a dataset. Suggest other types to cjg@ecs.soton.ac.uk

oo:ResearchPublicationsRepository

Can be used to indicate that this dataset contains research publications of an organisation.

oo:AuthoritativeDataset

This indicates that this dataset was published by the data owner of the primary topic of the dataset. It is strongly recommended that this is combined with dct:publisher to indicate who this publisher is.

oo:NonAuthoritativeDataset

This indicates that this dataset was published by an agent which was NOT the data owner of the primary topic of the dataset. For example you may wish to republish a 3rd party open dataset in a form useful to your organisations open data environment, but make it clear that you are not the authoritative source for this data. It is strongly recommended you use dct:source to relate the dataset back to its source(s).

This is also recommended for use where you wish to link to a dataset about your organisation but make it clear in your data catalogue that it is NOT an authoritative dataset. For example, a crowd-sourced dataset.

Misc

oo:capacity

This is used to indicate the capacity of a thing when performing its default function. Ideally a more semantically meaningful predicate should be used, describing the capacity of something in a particular function.

This may be used to associate:

  • a classroom, theatre, cinema or resturant with the number of people it seats
  • a bar or other entertainment venue with the fire limit for the venue
  • a school with how many students it can teach
  • a pencil case with how many pencils it can hold.

You should be able to assume that resources of the same type, described in the same dataset, have capacities calculated in a more-or-less similar way.

It should only be treated as a rough guide. (TODO; link to how to describe quantative & qualative location features).

oo:access

This relates a place (geo:SpatialThing) with a text description of how to access this thing. It may be that there is limited wheel chair access, a certain entrance is required or any other access information to tell a person planning to visit this place.

oo:twitterHashtag

This is used to relate a concept to the Twitter hashtag people are using to talk about that thing.

We've created the twitterHashtag in the open org namespace. A hashtag can be related to a concept, location, event, or anything. A combination of hashtags may be used in one literal to indicate that it is that combination of hashtags which is associated with that resource.

Having two oo:twitterHashtag properties, however, would indicate that either is used to refer to the same thing (not recommended).

<oo:twitterHashtag>#myconf2010<oo:twitterHashtag>

or, to indicate a combo hashtag:

<oo:twitterHashtag>#myconf2010 #track2<oo:twitterHashtag>

Instead of a string literal this may also point to a URI used to identify the hashtag.