Places

From OpenOrg
Revision as of 18:42, 10 January 2011 by WikiSysop (talk | contribs) (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)....")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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.

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>

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!)

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.


In a document mentioning a "place":

  • 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.