Difference between revisions of "Places/FeaturesAndConfigurations"

From OpenOrg
Jump to: navigation, search
(starting to work on the feature and configuration page.)
 
(Added example)
Line 12: Line 12:
  
 
<syntaxhighlight lang="xml">
 
<syntaxhighlight lang="xml">
 +
  <rooms:Room rdf:about="http://example.org/id/room/123">
 +
    <rdfs:label>Meeting Room A</rdfs:label>
 +
    <oo:hasSpaceConfiguration>
 +
      <oosc:Boardroom rdf:about="http://example.org/id/room/123/config/boardroom">
 +
        <oo:capacity rdf:datatype="&xsd;int">14</oo:capacity>
 +
      </oosc:Boardroom>
 +
    </oo:hasSpaceConfiguration>
 +
    <oo:hasSpaceConfiguration>
 +
      <oosc:UShape rdf:about="http://example.org/id/room/123/config/ushape">
 +
        <oo:capacity rdf:datatype="&xsd;int">10</oo:capacity>
 +
      </oosc:UShape>
 +
    </oo:hasSpaceConfiguration>
 +
    <oo:primarySpaceConfiguration rdf:resource="http://example.org/id/room/123/config/boardroom"/>
 +
    <oo:currentSpaceConfiguration rdf:resource="http://example.org/id/room/123/config/ushape"/>
 +
  </rooms:Room>
 
</syntaxhighlight>
 
</syntaxhighlight>

Revision as of 08:43, 30 March 2011

Rooms and other spaces can be tagged according to their available configurations (i.e. layouts) and features available to their occupants. Configurations for a meeting room might be 'theatre' or 'boardroom', whereas a field might have 'football pitch' or 'festival'. Features might include 'projector', 'induction loop', or 'parking space'.

Features may be attached directly to rooms and spaces to imply that they are ordinarily available for all configurations, or to an individual configuration. For example, a 'theatre' configuration may have the feature 'tiered seating', whereas a 'banquet' configuration might not (as the tiered seating is removable).

Configurations

Configurations are related to rooms by three properties: oo:hasSpaceConfiguration, oo:primarySpaceConfiguration, and oo:currentSpaceConfiguration.

Each configuration is an instance of some subclass of oosc:SpaceConfiguration. It should also be annotated with a capacity.

For example:

<syntaxhighlight lang="xml">

 <rooms:Room rdf:about="http://example.org/id/room/123">
   <rdfs:label>Meeting Room A</rdfs:label>
   <oo:hasSpaceConfiguration>
     <oosc:Boardroom rdf:about="http://example.org/id/room/123/config/boardroom">
       <oo:capacity rdf:datatype="&xsd;int">14</oo:capacity>
     </oosc:Boardroom>
   </oo:hasSpaceConfiguration>
   <oo:hasSpaceConfiguration>
     <oosc:UShape rdf:about="http://example.org/id/room/123/config/ushape">
       <oo:capacity rdf:datatype="&xsd;int">10</oo:capacity>
     </oosc:UShape>
   </oo:hasSpaceConfiguration>
   <oo:primarySpaceConfiguration rdf:resource="http://example.org/id/room/123/config/boardroom"/>
   <oo:currentSpaceConfiguration rdf:resource="http://example.org/id/room/123/config/ushape"/>
 </rooms:Room>

</syntaxhighlight>