Difference between revisions of "Places"

From OpenOrg
Jump to: navigation, search
(Created page with "This is a pattern to describe physical places of note to an organisation. Generally this will include, but is not limited to Rooms, Buildings and Sites (eg. a university campus)....")
 
Line 1: Line 1:
 
This is a pattern to describe physical places of note to an organisation. Generally this will include, but is not limited to Rooms, Buildings and Sites (eg. a university campus). We have learned in planning this that one size will not fit all, so will describe a very simple basic pattern, then extensions for various purposes.
 
This is a pattern to describe physical places of note to an organisation. Generally this will include, but is not limited to Rooms, Buildings and Sites (eg. a university campus). We have learned in planning this that one size will not fit all, so will describe a very simple basic pattern, then extensions for various purposes.
 +
 +
== Namespaces ==
 +
 +
[http://prefix.cc/rdfs,geo,spacerel,room,org,foaf rdfs geo spacerel room org foaf ]
  
 
== Place ==
 
== Place ==
Line 13: Line 17:
 
</syntaxhighlight>
 
</syntaxhighlight>
  
== Buildings ==
+
== Lat & Long ==
 +
 
 +
If known then its very useful to give the latitude and longitude of a reference point for this place. You may wish to include more fancy descriptions of its shape but this is very useful to anybody trying to use your data so include it even if its not perfect. It should represent a useful point to refer to the place-- usually either the center or the main entrance or reception.
 +
 
 +
== Place Hierarchy ==
 +
 
 +
It may be useful to organise your places as a hierarchy. Any place may be declared as 'within' other places. For example;
 +
* Carparks and Buildings are within a site (campus)
 +
* Rooms are within buildings
 +
* Points of service (eg. a shop or bar) are within Rooms or Buildings
 +
It may be useful to infer a lat,long of something using the within relationship, eg. If a shop (point of service) is in a room, and that room is in a building then you could use the lat/long of the building to render an approximate location for the shop. It is not recommended that this chain is followed past "Building" or at most "Site" as it becomes rather useless to work out that a shop is in "Scotland" and use a reference point for Scotland to locate the shop!
 +
 
 +
IDEA FOR LATER: It might be useful later to add a 'Reference Point Accuracy' value so you can tell how useful a reference point is. ie. A shop would be accurate +/- 10m but the reference point for a building is more like +/-50 and for a city +/-3000.
 +
 +
== Building ==
 +
 
 +
<syntaxhighlight lang="xml">
 +
    <rdf:type rdf:resource="http://vocab.deri.ie/rooms#Building" />
 +
</syntaxhighlight>
 +
 
  
 
If just publishing a list of buildings (or sites and buildings) and data about them, then it is recommended that this is a single document unless impractical to do so (you have 1000's of buildings!)  
 
If just publishing a list of buildings (or sites and buildings) and data about them, then it is recommended that this is a single document unless impractical to do so (you have 1000's of buildings!)  
Line 19: Line 42:
 
If you want to publish data on every room in every building then that (probably) needs to be one document per building, but you should still maintain a top-level list of buildings, and make sure people can [[follow your nose|follow their nose]] to get to the full description of the building and rooms.
 
If you want to publish data on every room in every building then that (probably) needs to be one document per building, but you should still maintain a top-level list of buildings, and make sure people can [[follow your nose|follow their nose]] to get to the full description of the building and rooms.
  
 +
Don't get too het up about what is or isn't a building, and the following are perfectly reasonabl
 +
* A building within a building
 +
* A room within 2 different buildings
 +
 +
 +
http://vocab.deri.ie/rooms#Room
 +
 +
      <rdf:type rdf:resource="http://vocab.deri.ie/rooms#Building" />
 +
      <rdf:type rdf:resource="http://vocab.deri.ie/rooms#Room" />
 +
 +
 +
== Room ==
 +
 +
<syntaxhighlight lang="xml">
 +
    <rdf:type rdf:resource="http://vocab.deri.ie/rooms#Room" />
 +
</syntaxhighlight>
 +
 +
== Site ==
 +
 +
This is a place where all or part of an organisation is located. A cluster of places with something in common, such as a university campus or the Glastonbury Festival site.
 +
 +
<syntaxhighlight lang="xml">
 +
    <rdf:type rdf:resource="http://www.w3.org/ns/org#Site" />
 +
</syntaxhighlight>
 +
 +
Rather than listing a site as being spacerel:within a city, country or state, it should be described by what is the nearest population center or similar landmark.
 +
 +
eg.
 +
 +
<syntaxhighlight lang="xml">
 +
<rdf:Description rdf:about="http://id.southampton.ac.uk/place/highfield-campus">
 +
  <rdfs:label>Highfield Campus</rdfs:label>
 +
  <rdf:type rdf:resource="http://www.w3.org/ns/org#Site" />
 +
  <foaf:based_near rdf:resource="http://sws.geonames.org/2637487/" />
 +
</rdf:Description>
 +
<rdf:Description rdf:about="http://sws.geonames.org/2637487/">
 +
  <rdfs:label>Southampton</rdfs:label>
 +
</rdf:Description>
 +
</syntaxhighlight>
  
 +
Ideally, use geonames to identify cities, but a less-good alternative is to use dbpedia. eg. http://dbpedia.org/resource/Southampton is the ID for whatever http://en.wikipedia.org/page/Southampton is about, but it's always possible wikipedia pages will change their meaning which is why that's not so good.
  
In a document mentioning a "place":
+
== Points of Service ==
* if possible give it a lat/long
 
* if possible include a summary of the containing place(s) up to the highest "level" of containment in your dataset. eg. for us up to the Campus. A summary is at least type, label and should contain lat/long if available. (I think we should decide to either recommend listing that a room is contained by a building & contained by a campus /OR/ that a room is contained by a building, and that building by a site. Maybe the 2nd model is better as it's less verbose and more descriptive)
 
* It must contain a summary of it's immediate "container" and things it directly "contains" in your model (however you model it), but it can contain as much more as you like.
 

Revision as of 19:27, 10 January 2011

This is a pattern to describe physical places of note to an organisation. Generally this will include, but is not limited to Rooms, Buildings and Sites (eg. a university campus). We have learned in planning this that one size will not fit all, so will describe a very simple basic pattern, then extensions for various purposes.

Namespaces

rdfs geo spacerel room org foaf

Place

A place is any physical location so there's very little you can say about it, it may have no rdf classes, or several. By definition all places are of class geo:SpatialThing, but it is not required to be stated.

The most simple definition of a place is just a URI and a label.

<syntaxhighlight lang="xml">

 <rdf:Description rdf:about='...PLACE-URI...'>
    <rdfs:label>Behind the Bikesheds</rdfs:label>
 <rdf:Description>

</syntaxhighlight>

Lat & Long

If known then its very useful to give the latitude and longitude of a reference point for this place. You may wish to include more fancy descriptions of its shape but this is very useful to anybody trying to use your data so include it even if its not perfect. It should represent a useful point to refer to the place-- usually either the center or the main entrance or reception.

Place Hierarchy

It may be useful to organise your places as a hierarchy. Any place may be declared as 'within' other places. For example;

  • Carparks and Buildings are within a site (campus)
  • Rooms are within buildings
  • Points of service (eg. a shop or bar) are within Rooms or Buildings

It may be useful to infer a lat,long of something using the within relationship, eg. If a shop (point of service) is in a room, and that room is in a building then you could use the lat/long of the building to render an approximate location for the shop. It is not recommended that this chain is followed past "Building" or at most "Site" as it becomes rather useless to work out that a shop is in "Scotland" and use a reference point for Scotland to locate the shop!

IDEA FOR LATER: It might be useful later to add a 'Reference Point Accuracy' value so you can tell how useful a reference point is. ie. A shop would be accurate +/- 10m but the reference point for a building is more like +/-50 and for a city +/-3000.

Building

<syntaxhighlight lang="xml">

    <rdf:type rdf:resource="http://vocab.deri.ie/rooms#Building" />

</syntaxhighlight>


If just publishing a list of buildings (or sites and buildings) and data about them, then it is recommended that this is a single document unless impractical to do so (you have 1000's of buildings!)

If you want to publish data on every room in every building then that (probably) needs to be one document per building, but you should still maintain a top-level list of buildings, and make sure people can follow their nose to get to the full description of the building and rooms.

Don't get too het up about what is or isn't a building, and the following are perfectly reasonabl

  • A building within a building
  • A room within 2 different buildings


http://vocab.deri.ie/rooms#Room

      <rdf:type rdf:resource="http://vocab.deri.ie/rooms#Building" />
      <rdf:type rdf:resource="http://vocab.deri.ie/rooms#Room" />


Room

<syntaxhighlight lang="xml">

    <rdf:type rdf:resource="http://vocab.deri.ie/rooms#Room" />

</syntaxhighlight>

Site

This is a place where all or part of an organisation is located. A cluster of places with something in common, such as a university campus or the Glastonbury Festival site.

<syntaxhighlight lang="xml">

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

</syntaxhighlight>

Rather than listing a site as being spacerel:within a city, country or state, it should be described by what is the nearest population center or similar landmark.

eg.

<syntaxhighlight lang="xml">

<rdf:Description rdf:about="http://id.southampton.ac.uk/place/highfield-campus">
  <rdfs:label>Highfield Campus</rdfs:label>
  <rdf:type rdf:resource="http://www.w3.org/ns/org#Site" />
  <foaf:based_near rdf:resource="http://sws.geonames.org/2637487/" />
</rdf:Description>
<rdf:Description rdf:about="http://sws.geonames.org/2637487/">
  <rdfs:label>Southampton</rdfs:label>
</rdf:Description>

</syntaxhighlight>

Ideally, use geonames to identify cities, but a less-good alternative is to use dbpedia. eg. http://dbpedia.org/resource/Southampton is the ID for whatever http://en.wikipedia.org/page/Southampton is about, but it's always possible wikipedia pages will change their meaning which is why that's not so good.

Points of Service