Parent Page BuildingServicePerformance (2B44)
- Ontology IRI The ontology IRI is used to identify the ontology in the context of the world wide web. This site has been set as the ontology IRI to be the URL where the latest version of the ontology will be published in OWL/XML. (2BZO)
Issues (2B45)
- Current ontology in the built environment is not mature. The Open Floor Plan Display / Exchange (OFPD/X) project plan is to build an ontology for: (2BDS)
- To coordinate with related work by others, metadata will be represented in accordance with the ISO/IEC 11179 Metadata Registry (MDR) standard. (2BGM)
Basic concepts (2B47)
- Use of ontology in demonstration of a service providing architecture to display and exchange properly-scaled static floor plans with time based (e.g.sensor trigger) dynamic information overlay. (2BDX)
- Use of ontology in demonstration of semantic mapping of concepts for the flow of information throughout a response to an emergency incident. Responses and alerts will also be organized by type. (2BDY)
- Reasoning over ontology and domain rules to establish and maintain Common Operating Pictures emergency by emergency - improving the ontology and domain rules over time. (2BDZ)
- Use of ontologies and geographic locations to limit the number of building codes and standards to be reviewed and incorporated into data about specific buildings. (2BE0)
- Below are first passes at ontology structure and terminology refinement, and proposed data elements. (2BE1)
First pass at ontology structure and terminology refinement (2B4C)
- Term: Built Environment (2B4M)
- ObjectProperty: containsBuiltEnvironment (2B51)
- Term: Site (2B4Q)
- Term: Vehicle Access (2B4V)
- comment: Should contains'X' and has'X' properties be defined explicitly for subclasses Y of class X? e.g. Should there be an object property containsVehicleAccess or should it be kept at a special use of containsBuiltEnvironment? The approach may be to use explicit declarations of object properties in the ontology and more the more general type in an object orientied model where there can be multiple function declarations, e.g. getContainedBuiltEnvironment(containerObjType, containedObjType) with the different Classes/Objects required. (2BU1)
- ObjectProperty: containsVehicleAccess (2B56)
- Term: Compass Orientation (2B5D)
- ObjectProperty: hasCompassOrientation (2B5N)
- Term: Text Description (2B5R)
Comment: same question as above, but best practices for level of detail in Class structure. Should there be a VehicleAccessDescription or should it be kept at the higher level of TextDescription? (2BU2)
- ObjectProperty: hasDescription (2B5W)
- ObjectProperty: hasTextDescription (2B7I)
- Term: Restrictions (2B69)
- ObjectProperty: hasRestrictions (2B6E)
- Term: Hydrant (2B6I)
- ObjectProperty: hasHydrant (2B6N)
- Term: Hydrant Type (2B7O)
- ObjectProperty: hasHydrantType (2B7S)
- Term: Facility (2BLH)
- Term: Built Environment Classification (2BLM)
- ObjectProperty: hasBuiltEnvironmentClassification (2BU6)
- Term: Facility Function (2BLR)
- ObjectProperty: hasFacilityFunction (2BUA)
- Term: Facility Form (2BLV)
- ObjectProperty: hasFacilityForm (2BUE)
- Term: Construction Type (2BM1)
- ObjectProperty: hasConstructionType (2BUI)
- Term: Sprinklered (2BMN)
- ObjectProperty: hasSprinkleredClassification (2BUM)
- Term: IBC Occupancy Class (2BMS)
- ObjectProperty: hasIBCOccupancyClass (2BUQ)
- Comment: Should the following contact types have the word "type" appended to the class name? e.g. Should BuildingOwner be BuildingOwnerType? and Tenant be TenantType? (2BN5)
- Term: Building Owner (2BN6)
- Term: Facility Manager (2BNB)
- Term: Building Engineer (2BNG)
- Term: Electric Company (2BNL)
- Term: Water Company (2BNQ)
- Term: Gas Company (2BNV)
- Term: Monitioring Company (2BO0)
- Term: State Hazmat Duty Officer (2BO5)
- Term: Tenant (2BOA)
- Term: Tenant Directory (2BOJ)
- (2BPB)
- Class: CommissioningDate (2BPC)
- Class: OccupancyNumberDay (2BPD)
- Class: OccupancyNumberNight (2BPE)
- Class: BuiltEnvironmentCirculation (2BPF)
- Class: VerticalCirculation (2BPG)
- Class: Elevator (2BPH)
- Class: Stair (2BPI)
- Class: ElevatorNumber (2BPJ)
- Class: StairNumber (2BPK)
- Class: LevelDesignation (2BPL)
- Class: TerminusFloorTop (2BPM)
- Class: TerminusFloorBottom (2BPN)
- Class: FloorRange (2BPO)
- Class: DischargeLevel (2BPP)
- Class: Exit (2BPQ)
- Class: FireSafetyFeature (2BPR)
- Class: HazardousStructure (2BPS)
- Class: HazardousStructureType (2BPT)
- Class: Keybox (2BPU)
- Class: FireControlRoom (2BPV)
- Class: FireFighterEntrance (2BPW)
- Class: PrePositionedFirefightingGear (2BPX)
- Class: FireFightingGearType (2BPY)
- Class: AreaOfRefuge (2BPZ)
- Class: UtilityShutoff (2BQ0)
- Class: UtilityShutoffType (2BQ1)
- Class: SecurityFeature (2BQ2)
- Class: SecurityGuardStation (2BQ3)
- Class: VideoCamera (2BQ4)
- Class: VideoCameraCoverageArea (2BQ5)
- Class: Floor (2BQ6)
- Class: Floor0 (2BQ7)
- Class: FloorsAboveGround (2BQ8)
- Class: FloorsBelowGround (2BQ9)
- Class: NetArea (2BQA)
- Class: 2DShape (2BQB)
- Class: Corridor (2BQC)
- Class: EgressPath (2BQD)
- Class: Door (2BQE)
- Class: LockedState (2BQF)
- Class: Zone (2BQG)
- Class: FireZone (2BQH)
- Class: HVACZone (2BQI)
- Class: HVACState (2BQJ)
- Class: ElectricalZone (2BQK)
- Class: ElectricityState (2BQL)
- Class: WaterConnection (2BQM)
- Comment: Should this be Plumbing or <noWiki>PlumbingZone</noWiki> (2BQN)
- Class: Plumbing (2BQO)
- (2BQP)
- Class: SecurityZone (2BQQ)
- Class: AccessDoor (2BQR)
- Class: SprinklerZone (2BQS)
- Class: SprinklerState (2BQT)
- Class: StandpipeOutlet (2BQU)
- Class: StandpipeOutletType (2BQV)
- Class: FireExtinguisher (2BQW)
- Class: FireExtinguisherType (2BQX)
- Class: Space (2BQY)
- Class: SpaceForm (2BQZ)
- Class: SpaceFunction (2BR0)
- Class: SpaceNumber (2BR1)
- Class: SpaceName (2BR2)
- Class: FireRating (2BR3)
- Class: DoorType (2BR4)
- Class: Window (2BR5)
- Class: WindowType (2BR6)
- Class: HazardousMaterials (2BR7)
- Class: HazardousMaterialsType (2BR8)
- Class: HazardousMaterialsSymbol (2BR9)
- Class: WaterService (2BRA)
- Class: Sensor (2BRB)
- Class: FireDetectionSensor (2BRC)
- Class: TemperatureSensor (2BRD)
- Class: SecurityAlarmSensor (2BRE)
- Term: Location Measure (2BJ9)
- Term: Longitude (2BJG)
- ObjectProperty: hasLongitude (2BJL)
- Term: Latitude (2BJP)
Vertical distance measurement between a reference point and another point or object, with the default reference at sea level (2BRF)
- ObjectProperty: hasLatitude (2BJU)
- Term: GPS Position (2BJY)
- ObjectProperty: hasGPSPosition (2BK3)
- Term: State Plane Coordinates (2BK7)
- ObjectProperty: hasStatePlaneCoordinates (2BKC)
- Term: WG S84 (2BKG)
- ObjectProperty: hasWGS84 (2BKL)
First pass at proposed data elements (2BE4)
- Site (2BE5)
- Facility (2BED)
- Facility Type (2BEE)
- Service Address (2BEK)
- Vertical Circulation (2BEO)
- Exits (2BES)
- Fire Safety Features (2BET)
- Fire Command Canter (2BEU)
- Keybox Locations (2BEV)
- Structural Features (2BEW)
- Fire Fighter Entrances (2BEX)
- Standpipe Oulets and Hookups (2BEY)
- Pre-Positioned Fire Fighter Gear (2BEZ)
- Sprinklered / Not Sprinklered (2BF0)
- Areas of Refuge (2BF1)
- Utility Shut Off Locations (2BF2)
- Fire Extinguisher Locations (2BF3)
- Law Enforcement (2BF4)
- ** Class: <nowiki>or (2BF7)
- Space (2BFN)
- Sensors and Components (2BGH)