RDF is based on statements of the form subject - predicate - object. Subject and object are illustrated as ellipses, the prediacte – or property – connects them and points from subject to object.
The XML Namespace URI that should be used by implementations of this version of the specification is: http://carsten.io/hxl/ns-2012-02-22.
The preferred prefix for the vocabulary is hxl.
Draft specification of the Humanitarian eXchange Language (HXL) standard. This vocabulary specification is currently under development and may change at any time without notice.
The porpuse of HXL is to facilitate data exchange within the humanitarian domain. It provides a core domain model that has been created bottom-up by inspecting a broad range of systems in use with different humanitarian organisations. As needs vary widely across organisations in this domain, this vocabulary does not intend to be complete; in fact, it is the smallest common denominator. Any organisations that wish to publish full exports of their data can do so by extending this domain model with application- or organisation-specific models that reflect their internal data models (which may already be formalised in an XML schema or database schema).
The Humanitarian eXchange Language is defined as a set of classes and properties, using the Resource Description Framework (RDF) as underlying technology. This enables HXL to publish humanitarian data as part of the Linked Open Data cloud. We recommend Tim Berners-Lee's TED Talk as a quick introduction to Linked Data and RDF, and the Linked Data book by Tom Heath and Chris Bizer as a more in-depth, technical primer to the topic.
The following series of figures illustrates the basics of RDF and Linked Data that are required to understand this document.
RDF is based on statements of the form subject - predicate - object. Subject and object are illustrated as ellipses, the prediacte – or property – connects them and points from subject to object.
URLs act as unique identifiers for subjects, properties and objects, as shown here. This way, more information about these can be found out by visiting the URLs. In case of the property, it should return its definition – again in RDF.
Namespace declarations can be used to make the URLs more compact. In this standard, we only show the namespace prefix if the class or property has been defined in an external standard. Moreover, the object of a statement (or triple) can also be a literal, such as a string or a number. Literals are visualized as boxes.
Any subjects and (non-literal) objects should be typed. The classes defined in this standard declare the types that can be used for this purpose.
The definitions of these classes are based on subclass hierarchies, indicated by a dotted red line in the figure. Emergency is a subclass of Situation, for example. Subclasses inherit from their superclasses, most importantly in terms of the domain and range of properties.
The domain and range define the types of things between which a property can be used. Consider the property hasObjective, whose domain is defined as Humanitarian Activity. This states that whenever we see a statement using hasObjective as property, we can infere that the subject of this triple is a Humanitarian Activity. Likewise, its range is defined as Objective, so that we can infere that the object in any statement using hasObjective is an Objective. In the graphs shown in this standard, the property arrows point from domain to range (i.e., from kinds of subjects to kinds of objects).
An alphabetical index of all terms from the HXL vocabulary, by class and by property, is given below for quick reference. Click the terms for a more detailed description.
Classes | Humanitarian Activity | Administrative Unit | Administrative Unit Level | Affected Population | Age Group | Approval level | Bladder | Blanket | Bounding Box | Bucket | Bucket / Jerry Can | Casualty | Cluster | Community tool kit | Cot | Data container | Dead | Displaced | Distributing partner | Distribution | Emergency | Tent (family) | Family tool kit | Feature | Female | GLIDE number | Geometry | Hygiene kit | Internally Displaced Person | Impact planned | Indicator | Individual item | Injured | Jerry Can | Kit | Kitchen set | Tent (large) | Line String | Male | Mat | Missing | MosquitoNet | Need | Non-Displaced | Non-food item | Objective | Organisation | Internally Displaced Person | Outcome planned | Outcome to date | Output planned | Output to date | Point | Pole | Polygon | Populated Place | Population | Priority | Refugees and Asylum Seekers | Reporting Period | Response | Rope | Sex | Sheet | Shelter kit | Situation | Status | Supplying agency | Tarpaulin | Tent | Tool kit | Total Population | Water filter | http://purl.org/dc/terms/PeriodOfTime | http://xmlns.com/foaf/0.1/Agent | http://xmlns.com/foaf/0.1/Group | http://xmlns.com/foaf/0.1/Organisation |
Properties | actual end | actual start | addresses | affected by | approved at level | approved by | as WKT | at level | atLocation | based on | common title | completed outcome of | completed output of | contains | contains item | contains primary data | contains secondary data | count | crosses | data collection process | distributes | duration | end | equals | extends | for emergency | from age | funded by | has beneficiary | has GLIDE number | has geometry | has objective | has part | has priority | has standard | has status | has value | identified at | implemented by | in administrative unit | intersects | involved in | measurement of | measures | near | overlaps | planned end | planned start | provenance Information | provides | reaches | reported by | start | supplies | to age | touches | within | http://purl.org/dc/terms/date | http://purl.org/dc/terms/description |
The cross-reference is organized into thematic sections. Each section is illustrated by a graph of the respective classes and properties. The ellipses in the graph represent classes, whereas the arrows represent properties. Dashed lines indicate a subclass relationship (e.g. Camp is a subclass of Site). Solid lines are labeled with the property that connects these two classes. Grey ellipses indicate adjacent classes that are defined in a different section.
Jump directly to the different sections: | Date/Time Section | Geolocation Section | Metadata Section | Response Section | Shelter Cluster Section | Situation Section |
This section of the vocabulary defines the date/time standard. The draft HXL date/time standard contains a detailed description of how to use the classes and properties.
Alphabetical index of all classes and properties in the Date/Time Section:
Classes | Reporting Period | http://purl.org/dc/terms/PeriodOfTime |
Properties | actual end | actual start | duration | end | planned end | planned start | start | http://purl.org/dc/terms/date |
Extended graph visualization of the Date/Time Section, including adjacent classes defined in a different section (in grey).
[click to enlarge]
The time frame that a report covers.
Term origin: Sigmah DB.
| Identifier: | ReportingPeriod |
|---|---|
| Subclass of: | http://purl.org/dc/terms/PeriodOfTime |
| Identifier: | http://purl.org/dc/terms/PeriodOfTime |
|---|---|
| Subclasses: | Reporting Period | |
| Domain of: | duration | end | start | |
Specifies the actual end of an activity.
| Identifier: | actualEnd |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the actual start of an activity.
| Identifier: | actualStart |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the duration of a period of time; if the duration is given, start and/or end may be omitted.
| Identifier: | duration |
|---|---|
| Domain: | http://purl.org/dc/terms/PeriodOfTime |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the end of activities, projects, etc.
| Identifier: | end |
|---|---|
| Domain: | http://purl.org/dc/terms/PeriodOfTime |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the planned end of an activity.
| Identifier: | plannedEnd |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the planned start of an activity.
| Identifier: | plannedStart |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the start of time periods.
| Identifier: | start |
|---|---|
| Domain: | http://purl.org/dc/terms/PeriodOfTime |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Generic property for date/time stamps at arbitrary granularity.
| Identifier: | http://purl.org/dc/terms/date |
|---|---|
| Domain: | Outcome to date Output to date |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
This section of the vocabulary defines the geolocation standard. The draft HXL geolocation standard contains a detailed description of how to use the classes and properties.
Alphabetical index of all classes and properties in the Geolocation Section:
Classes | Administrative Unit | Administrative Unit Level | Bounding Box | Feature | Geometry | Line String | Point | Polygon | Populated Place |
Properties | as WKT | at level | atLocation | contains | crosses | equals | has geometry | in administrative unit | intersects | near | overlaps | touches | within |
Extended graph visualization of the Geolocation Section, including adjacent classes defined in a different section (in grey).
[click to enlarge]
Administrative units can include coutries, regions, cities, etc. The hierarchy of administrative units can vary from country to country.
| Identifier: | AdminUnit |
|---|---|
| Subclass of: | Feature |
| Subclasses: | Populated Place | |
| Domain of: | at level | in administrative unit | |
| Range of: | in administrative unit | |
The specific administrative unit levels can vary from country to country. Administrative Unit Level 0 is a country – in this case, hxl:Country should be used.
| Identifier: | AdminUnitLevel |
|---|---|
| Range of: | at level | |
A BoundingBox is a Polygon defined by 1 exterior boundary and 0 interior boundaries. The exterior boundary consists of 4 points arranged as a rectangle.
| Identifier: | BoundingBox |
|---|---|
| Subclass of: | Polygon |
Any real-word phenomenon with spatial extent, i.e. size, shape, or position.
| Identifier: | Feature |
|---|---|
| Subclass of: | http://www.w3.org/2003/01/geo/wgs84_pos#SpatialThing |
| Subclasses: | Administrative Unit | |
| Domain of: | has geometry | |
| Range of: | atLocation | |
Abstract root class of the geometry. This class should not be instantiated; use any of the subclasses when creating actual geometries.
| Identifier: | Geometry |
|---|---|
| Subclasses: | Line String | Point | Polygon | |
| Domain of: | as WKT | contains | crosses | equals | intersects | near | overlaps | touches | within | |
| Range of: | contains | crosses | equals | has geometry | intersects | near | overlaps | touches | within | |
A LineString is a Curve with linear interpolation between Points. Each consecutive pair of Points defines a Line segment.
| Identifier: | Line |
|---|---|
| Subclass of: | Geometry |
A Point is a 0-dimensional geometric object and represents a single location in a two- or three-dimensional coordinate space.
| Identifier: | Point |
|---|---|
| Subclass of: | Geometry |
A Polygon is a planar Surface defined by 1 exterior boundary and 0 or more interior boundaries. Each interior boundary defines a hole in the Polygon.
| Identifier: | Polygon |
|---|---|
| Subclass of: | Geometry |
| Subclasses: | Bounding Box | |
Lowest-level administrative unit, such as a town or settlement.
| Identifier: | PopulatedPlace |
|---|---|
| Subclass of: | Administrative Unit |
A geometry serialised as WKT. Note that the WKT serialisation contains the spatial reference system (SRS), as specified in the OGC Simple Feature standard. If no SRS is given, HXL uses WGS 84 as the standard SRS.
| Identifier: | asWKT |
|---|---|
| Domain: | Geometry |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the level for an administrative unit.
| Identifier: | atLevel |
|---|---|
| Domain: | Administrative Unit |
| Range: | Administrative Unit Level |
| Inverse property: | levelOf |
Specififes the location for things like emergencies, projects, or camps.
| Identifier: | atLocation |
|---|---|
| Domain: | Emergency Situation Humanitarian Activity |
| Range: | Feature |
| Inverse property: | locationOf |
Topological relation. States that one geometry contains another one.
| Identifier: | contains |
|---|---|
| Domain: | Geometry |
| Range: | Geometry |
Topological relation. States that one geometry crosses another one.
| Identifier: | crosses |
|---|---|
| Domain: | Geometry |
| Range: | Geometry |
Topological relation. States that two geometries are equal.
| Identifier: | equals |
|---|---|
| Domain: | Geometry |
| Range: | Geometry |
Relates a feature to its geometry.
| Identifier: | hasGeometry |
|---|---|
| Domain: | Feature |
| Range: | Geometry |
| Inverse property: | isGeometryOf |
Specifies direct containment between two administrative units. This property should only be used between administrative units that directly contain each other, i.e., when the administrative unit level of the containing unit is the level of the contained unit plus 1.
| Identifier: | inAdminUnit |
|---|---|
| Domain: | Administrative Unit |
| Range: | Administrative Unit |
Topological relation. States that one geometry intersects another one.
| Identifier: | intersects |
|---|---|
| Domain: | Geometry |
| Range: | Geometry |
Topological relation. States that one geometry is near another one.
| Identifier: | near |
|---|---|
| Domain: | Geometry |
| Range: | Geometry |
Topological relation. States that one geometry overlaps another one.
| Identifier: | overlaps |
|---|---|
| Domain: | Geometry |
| Range: | Geometry |
Topological relation. States that one geometry touches another one.
| Identifier: | touches |
|---|---|
| Domain: | Geometry |
| Range: | Geometry |
Topological relation. States that one geometry is within another one.
| Identifier: | within |
|---|---|
| Domain: | Geometry |
| Range: | Geometry |
This section of the vocabulary defines the standards for metadata about a set of HXL data that is being exchanged.
Alphabetical index of all classes and properties in the Metadata Section:
Classes | Approval level | Data container |
Properties | approved at level | approved by | contains primary data | contains secondary data | data collection process | reported by |
Extended graph visualization of the Metadata Section, including adjacent classes defined in a different section (in grey).
[click to enlarge]
Instance of this class define fixed levels of approval. E.g. in the WHO system, there could be three levels: region, country, and world.
| Identifier: | ApprovalLevel |
|---|---|
| Range of: | approved at level | |
This is the container element for to attach any metadata to. Any HXL file has to include exactly one data container element and make all metadata statements about this container. When loading the file into the triple store, a new named graph will be created that inherits the metadata from this container.
| Identifier: | DataContainer |
|---|---|
| Domain of: | approved at level | approved by | contains primary data | contains secondary data | data collection process | reported by | |
A container can have approval at different levels, which may in turn indicate for which kind of analyses the data in this container is fit.
| Identifier: | approvedAtLevel |
|---|---|
| Domain: | Data container |
| Range: | Approval level |
Link from a container to the person or organisation who has 'lifted' it to the current approvalLevel.
| Identifier: | approvedBy |
|---|---|
| Domain: | Data container |
| Range: | http://xmlns.com/foaf/0.1/Agent |
A container can contain primary data, secondary data, or both.
| Identifier: | containsPrimaryData |
|---|---|
| Domain: | Data container |
| Range: | http://www.w3.org/2001/XMLSchema#boolean |
A container can contain primary data, secondary data, or both.
| Identifier: | containsSecondaryData |
|---|---|
| Domain: | Data container |
| Range: | http://www.w3.org/2001/XMLSchema#boolean |
Links a container to a description of the data collection process. We'll have to discuss this – is there a set fixed procedures (such as MIRA) so that it would make sense to have a class DataCollectionProcess?
| Identifier: | dataCollectionProcess |
|---|---|
| Domain: | Data container |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
The reporting person or organization is not necessarily involved in the aid activity itself, though in practice it often will be a donor or appealing agency.
Term origin: IATI.
| Identifier: | reportedBy |
|---|---|
| Domain: | Data container |
| Range: | http://xmlns.com/foaf/0.1/Agent |
This section of the vocabulary defines the standards for response activities.
Alphabetical index of all classes and properties in the Response Section:
Classes | Humanitarian Activity | Cluster | Impact planned | Objective | Organisation | Outcome planned | Outcome to date | Output planned | Output to date | Priority | Response | Status | http://xmlns.com/foaf/0.1/Organisation |
Properties | addresses | completed outcome of | completed output of | extends | for emergency | funded by | has beneficiary | has objective | has part | has priority | has status | implemented by | involved in | measurement of | measures |
Extended graph visualization of the Response Section, including adjacent classes defined in a different section (in grey).
[click to enlarge]
An Activity generally addresses some kind of need given in a Humanitarian Situation. Synonyms: Project, intervention.
Term origin: IATI, CAP OPS, Pakistan SRF, Sahana Project, Sigmah DB
| Identifier: | Activity |
|---|---|
| Subclasses: | Distribution | |
| Domain of: | actual end | actual start | addresses | atLocation | funded by | has beneficiary | has objective | has part | has priority | has status | implemented by | planned end | planned start | |
| Range of: | has part | involved in | |
An organizational unit responsible for one or more sectors during an emergency.
Term origin: CAP OPS, CCDI.
| Identifier: | Cluster |
|---|
The positive and negative, primary and secondary long-term effects produced by a humanitarian action, directly or indirectly. Example: reduction in child mortality. See CAP Guidelines 2012.
| Identifier: | ImpactPlanned |
|---|---|
| Subclass of: | Objective |
An objective states part of your humanitarian strategy in terms of the expected outputs, outcomes and impact, supported by a convincing description of how you will attain them in the face of limited resources, imperfect access and other impediments. Every objective should be SMART: specific, measurable (when matched with relevant indicators), achievable, relevant and time-bound. (CAP 2012 Guidelines)
Term origin: Sahana Project, CERF
| Identifier: | Objective |
|---|---|
| Subclasses: | Impact planned | Outcome planned | Output planned | |
| Range of: | has objective | measures | |
A humanitarian organisation.
Term origin: IATI, CAP OPS, Pakistan SRF, EIMS Report, Shelter Cluster, Sigmah DB.
| Identifier: | Organisation |
|---|---|
| Subclass of: | http://xmlns.com/foaf/0.1/Organisation |
| Subclasses: | Distributing partner | Supplying agency | |
| Domain of: | involved in | |
| Range of: | extends | funded by | has beneficiary | implemented by | |
Planned outcome. An outcome is the short-term or medium-term effect of a humanitarian action on the affected population. Outcomes often are the results of multiple outputs; each outcome in your planning may therefore correspond to more than one output. Example: increase in household consumption of potable water. See CAP Guidelines 2012.
| Identifier: | OutcomePlanned |
|---|---|
| Subclass of: | Objective |
| Range of: | completed outcome of | |
The state of this outcome at a certain point in time. An outcome is the short-term or medium-term effect of a humanitarian action on the affected population. Outcomes often are the results of multiple outputs; each outcome in your planning may therefore correspond to more than one output. Example: increase in household consumption of potable water. See CAP Guidelines 2012.
| Identifier: | OutcomeToDate |
|---|---|
| Domain of: | completed outcome of | measurement of | http://purl.org/dc/terms/date | |
Planned output. The outputs are the products, goods or services that are the direct results of a humanitarian action. Example: NFI kits in the hands of affected households; functioning water points; latrines; distributed food rations; therapeutic feeding treatments. See CAP Guidelines 2012.
| Identifier: | OutputPlanned |
|---|---|
| Subclass of: | Objective |
| Range of: | completed output of | |
The state of this outcome at a certain point in time. The outputs are the products, goods or services that are the direct results of a humanitarian action. Example: NFI kits in the hands of affected households; functioning water points; latrines; distributed food rations; therapeutic feeding treatments. See CAP Guidelines 2012. See CAP Guidelines 2012.
| Identifier: | OutputToDate |
|---|---|
| Domain of: | completed output of | measurement of | http://purl.org/dc/terms/date | |
The priority for a project or activity. Individuals of this class should be created whenever a fixed scale for priorities is in use.
Term origin: CAP OPS, UNHCR Camp DB, Sahana Project, MIRA, HPM Ethiopia.
| Identifier: | Priority |
|---|---|
| Range of: | has priority | |
Generic term for the collection of all activities that address the needs araising from an emergency.
Term origin: ACAPS DSS, ACAPS DSS, MIRA, EDXL, CCDI (Humanitarian Response), CERF (Humanitarian Response)
| Identifier: | Response |
|---|---|
| Domain of: | addresses | for emergency | has part | |
Status of an activity. Can be instantiated by organisations that use standardised status codes.
Term origin: Sahana Project CCDI, CERF, EDXL.
| Identifier: | Status |
|---|---|
| Range of: | has status | |
| Identifier: | http://xmlns.com/foaf/0.1/Organisation |
|---|---|
| Subclass of: | http://xmlns.com/foaf/0.1/Agent |
| Subclasses: | Organisation | |
States that a certain activity addresses a need.
| Identifier: | addresses |
|---|---|
| Domain: | Response Humanitarian Activity |
| Range: | Need |
| Inverse property: | addressedBy |
Relates the outcome to date to the outcome planned.
| Identifier: | completedOutcomeOf |
|---|---|
| Domain: | Outcome to date |
| Range: | Outcome planned |
Relates the output to date to the output planned.
| Identifier: | completedOutputOf |
|---|---|
| Domain: | Output to date |
| Range: | Output planned |
The subunit of the funding country or organisation, financing the activity from its own budget (e.g. a government agency or department).
Term origin: IATI.
| Identifier: | extends |
|---|---|
| Domain: | |
| Range: | Organisation |
States that a certain activity has been initiated for an emergency.
| Identifier: | forEmergency |
|---|---|
| Domain: | Response |
| Range: | Emergency |
| Inverse property: | emergencyOf |
Relates an activity to the organisation providing money or any kind of funding.
Term origin: IATI.
| Identifier: | fundedBy |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | Organisation |
An organisation receiving funding for this activity and ultimately carrying it out.
Term origin: IATI.
| Identifier: | hasBeneficiary |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | Organisation |
Defines the objectives for an activity or project.
| Identifier: | hasObjective |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | Objective |
| Inverse property: | isObjectiveOf |
Specifies part-whole relationships; e.g., a specific project can have sub-projects or specific activities.
| Identifier: | hasPart |
|---|---|
| Domain: | Response Humanitarian Activity |
| Range: | Humanitarian Activity |
| Inverse property: | partOf |
Defines the priority for an activity or project.
| Identifier: | hasPriority |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | Priority |
| Inverse property: | isPriorityOf |
Sets the current status for an activity.
| Identifier: | hasStatus |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | Status |
| Inverse property: | statusOf |
Property for external organisations / partners implenting (parts) of a project for an agency.
Term origin: IATI, CAP OPS, Pakistan SRF, HPM Ethiopia (Partner), Sigmah DB (Partner).
| Identifier: | implementedBy |
|---|---|
| Domain: | Humanitarian Activity |
| Range: | Organisation |
Indicates an organisation's involvement in an activity.
| Identifier: | involvedIn |
|---|---|
| Domain: | Organisation |
| Range: | Humanitarian Activity |
| Inverse property: | involvedOrganisation |
Defines what impact an output / outcome to date measures.
| Identifier: | measurementOf |
|---|---|
| Domain: | Output to date Outcome to date |
| Range: | Indicator |
Specififes the need or objective that a certain indicator addresses or measures. Eventually create second property for objectives?
| Identifier: | measures |
|---|---|
| Domain: | Indicator |
| Range: | Objective |
| Inverse property: | measuredBy |
This section of the vocabulary defines the standards for the shelter cluster.
Alphabetical index of all classes and properties in the Shelter Cluster Section:
Classes | Bladder | Blanket | Bucket | Bucket / Jerry Can | Community tool kit | Cot | Distributing partner | Distribution | Tent (family) | Family tool kit | Hygiene kit | Individual item | Jerry Can | Kit | Kitchen set | Tent (large) | Mat | MosquitoNet | Non-food item | Pole | Rope | Sheet | Shelter kit | Supplying agency | Tarpaulin | Tent | Tool kit | Water filter |
Properties | contains item | distributes | provides | reaches | supplies |
Extended graph visualization of the Shelter Cluster Section, including adjacent classes defined in a different section (in grey).
[click to enlarge]
Term origin: Shelter Cluster.
| Identifier: | BucketJerryCan |
|---|---|
| Subclass of: | Non-food item |
| Subclasses: | Bucket | Jerry Can | |
Term origin: Shelter Cluster.
| Identifier: | CommunityToolKit |
|---|---|
| Subclass of: | Tool kit |
Term origin: Shelter Cluster.
| Identifier: | DistributingPartner |
|---|---|
| Subclass of: | Organisation |
| Domain of: | distributes | |
Do we need a distribution point?Term origin: Shelter Cluster.
| Identifier: | Distribution |
|---|---|
| Subclass of: | Humanitarian Activity |
| Domain of: | provides | reaches | |
Term origin: Shelter Cluster.
| Identifier: | FamilyTent |
|---|---|
| Subclass of: | Tent |
Term origin: Shelter Cluster.
| Identifier: | FamilyToolKit |
|---|---|
| Subclass of: | Tool kit |
Term origin: Shelter Cluster.
| Identifier: | IndividualItem |
|---|---|
| Subclass of: | Non-food item |
Term origin: Shelter Cluster.
| Identifier: | Kit |
|---|---|
| Subclasses: | Hygiene kit | Shelter kit | Tool kit | |
| Domain of: | contains item | |
| Range of: | distributes | provides | supplies | |
Is this a Kit?Term origin: Shelter Cluster.
| Identifier: | KitchenSet |
|---|---|
| Subclass of: | Non-food item |
Term origin: Shelter Cluster.
| Identifier: | LargeTent |
|---|---|
| Subclass of: | Tent |
Term origin: Shelter Cluster.
| Identifier: | NonFoodItem |
|---|---|
| Subclasses: | Bladder | Blanket | Bucket / Jerry Can | Cot | Individual item | Kitchen set | Mat | MosquitoNet | Pole | Rope | Sheet | Tarpaulin | Tent | Water filter | |
| Range of: | contains item | distributes | provides | supplies | |
Term origin: Shelter Cluster.
| Identifier: | SupplyingAgency |
|---|---|
| Subclass of: | Organisation |
| Domain of: | supplies | |
Term origin: Shelter Cluster.
| Identifier: | Tarpaulin |
|---|---|
| Subclass of: | Non-food item |
Term origin: Shelter Cluster.
| Identifier: | Tent |
|---|---|
| Subclass of: | Non-food item |
| Subclasses: | Tent (family) | Tent (large) | |
Term origin: Shelter Cluster.
| Identifier: | ToolKit |
|---|---|
| Subclass of: | Kit |
| Subclasses: | Community tool kit | Family tool kit | |
Term origin: Shelter Cluster.
| Identifier: | WaterFilter |
|---|---|
| Subclass of: | Non-food item |
Used to specify the items contained in a kit.
| Identifier: | containsItem |
|---|---|
| Domain: | Kit |
| Range: | Non-food item |
Specifies with items or kits a distributing partner is resposible for.
| Identifier: | distributes |
|---|---|
| Domain: | Distributing partner |
| Range: | Non-food item Kit |
Links the items and kits to a distribution.
| Identifier: | provides |
|---|---|
| Domain: | Distribution |
| Range: | Non-food item Kit |
Links the items and kits to a population.
| Identifier: | reaches |
|---|---|
| Domain: | Distribution |
| Range: | Population |
Links the items and kits to the supplying agency.
| Identifier: | supplies |
|---|---|
| Domain: | Supplying agency |
| Range: | Non-food item Kit |
This section of the vocabulary defines the standards for situations and emergencies.
Alphabetical index of all classes and properties in the Situation Section:
Classes | Affected Population | Age Group | Casualty | Dead | Displaced | Emergency | Female | GLIDE number | Internally Displaced Person | Indicator | Injured | Male | Missing | Need | Non-Displaced | Internally Displaced Person | Population | Refugees and Asylum Seekers | Sex | Situation | Total Population | http://xmlns.com/foaf/0.1/Agent | http://xmlns.com/foaf/0.1/Group |
Properties | affected by | based on | common title | count | from age | has GLIDE number | has standard | has value | identified at | provenance Information | to age | http://purl.org/dc/terms/description |
Extended graph visualization of the Situation Section, including adjacent classes defined in a different section (in grey).
[click to enlarge]
The population affected by an emergency.
Term origin: Humanitarian Profile (Affected);
| Identifier: | AffectedPopulation |
|---|---|
| Subclass of: | Population |
| Subclasses: | Casualty | Displaced | Non-Displaced | |
| Domain of: | affected by | |
Generic class for age groups; instances should be created for actual age groups (e.g. children under 5).
| Identifier: | AgeGroup |
|---|---|
| Subclass of: | Population |
| Domain of: | from age | to age | |
E.g. injured or dead.
Term origin: ACAPS DSS, Humanitarian Profile.
| Identifier: | Casualty |
|---|---|
| Subclass of: | Affected Population |
| Subclasses: | Dead | Injured | Missing | |
A (reported) death.
Term origin: ACAPS DSS, HPM Ethiopia, Shelter Cluster, Humanitarian Profile (Dead).
| Identifier: | Dead |
|---|---|
| Subclass of: | Casualty |
Refers to internally displaced persons, refugees, and others of concern.
Term origin: Humanitarian Profile, ACAPS DSS (Displacement)
| Identifier: | Displaced |
|---|---|
| Subclass of: | Affected Population |
| Subclasses: | Internally Displaced Person | Internally Displaced Person | Refugees and Asylum Seekers | |
Any situation in which ... life or well-being ... will be threatened unless immediate and appropriate action is taken, and which demands an extraordinary response and exceptional measures” (UNHCR Handbook for Emergencies)
A sudden crisis situation or event requiring immediate action (WART)
Any situation in which there is an exceptional and widespread threat to life, health or basic subsistence, that is beyond the coping capacity of individuals and the community” (Oxfam GB Emergency Response Manual).
Where and when a disaster provokes an immediate, exceptional and widespread threat to life, health or basic subsistence, which overwhelms the coping capacity of individual and community, implying need of external assistance” (source: ACFIN Emergency module)
Term origin: CAP OPS, Pakistan SRF, ACAPS DSS, CERF, MIRA.| Identifier: | Emergency |
|---|---|
| Subclass of: | Situation |
| Domain of: | atLocation | has GLIDE number | |
| Range of: | affected by | for emergency | |
A woman/girl or group of women/girls.
Term origin: CERF, EIMS Report.
| Identifier: | Female |
|---|---|
| Subclass of: | http://xmlns.com/foaf/0.1/Agent |
Globally common Unique ID code for disasters. See about GLIDE.
| Identifier: | GLIDEnumber |
|---|---|
| Range of: | has GLIDE number | |
A group of internally displaced persons (IDPs).
Term origin: Humanitarian Profile, CERF, HPM Ethiopia
| Identifier: | IDP |
|---|---|
| Subclass of: | Displaced |
Concrete measurable reference for a concrete need; e.g., 5 litres of clean water per person and day.
Term origin: Pakistan SRF, ACAPS DSS, CCDI, CERF, HPM Ethiopia, Sigmah DB
| Identifier: | Indicator |
|---|---|
| Domain of: | has standard | has value | measures | |
| Range of: | based on | measurement of | |
Injured part of the population.
Term origin: ACAPS DSS, Humanitarian Profile, Shelter Cluster, HERAMS Checklist (Injury)
| Identifier: | Injured |
|---|---|
| Subclass of: | Casualty |
A man/boy or group of men/boys.
Term origin: CERF, EIMS Report.
| Identifier: | Male |
|---|---|
| Subclass of: | http://xmlns.com/foaf/0.1/Agent |
Missing population.
Term origin: Humanitarian Profile.
| Identifier: | Missing |
|---|---|
| Subclass of: | Casualty |
A concrete need, lack, or gap, e.g. a shortage of food. Can be based on the application of relevant norms (usually a minimum requirement or a pre-existing ‘normal’ situation); and an assessment of how the reality differs. Identifying and measuring deficits, either actual or predicted.
Term origin: CAP OPS, ACAPS DSS (also: Humanitarian Need), CCDI (Humanitarian Need), CCDI Shelter Cluster (Gap), HPM Ethiopia (Gap).
| Identifier: | Need |
|---|---|
| Domain of: | based on | identified at | |
| Range of: | addresses | |
Refers to the part of the affected population that is not displaced (i.e., host or non-host);.
Term origin: Humanitarian Profile.
| Identifier: | NonDisplaced |
|---|---|
| Subclass of: | Affected Population |
A group of displaced persons that does neither fit the IDP nor Refugees/Asylum Seekers classes.
Term origin: Humanitarian Profile
| Identifier: | Others |
|---|---|
| Subclass of: | Displaced |
Generic class for any kind of population (e.g. total, affected, etc.); use the subclasses for the data annotation.
| Identifier: | Population |
|---|---|
| Subclass of: | http://xmlns.com/foaf/0.1/Group |
| Subclasses: | Affected Population | Age Group | Total Population | |
| Domain of: | count | provenance Information | |
| Range of: | reaches | |
A group of refugees and asylum seekers.
Term origin: Humanitarian Profile
| Identifier: | RefugeesAsylumSeekers |
|---|---|
| Subclass of: | Displaced |
Class to describe sex-specific issues, either at individual or group level.
Term origin: MIRA, CCDI
| Identifier: | Sex |
|---|---|
| Subclasses: | Female | Male | |
Generic situation.
| Identifier: | Situation |
|---|---|
| Subclasses: | Emergency | |
| Domain of: | atLocation | common title | http://purl.org/dc/terms/description | |
Total population for a given administrative unit or geographic area. Instances can be created to make statements about this population.
| Identifier: | TotalPopulation |
|---|---|
| Subclass of: | Population |
| Identifier: | http://xmlns.com/foaf/0.1/Agent |
|---|---|
| Subclasses: | Female | Male | http://xmlns.com/foaf/0.1/Group | http://xmlns.com/foaf/0.1/Organisation | |
| Range of: | approved by | reported by | |
| Identifier: | http://xmlns.com/foaf/0.1/Group |
|---|---|
| Subclass of: | http://xmlns.com/foaf/0.1/Agent |
| Subclasses: | Population | |
States that a Population is affacted by an Emergency.
| Identifier: | affectedBy |
|---|---|
| Domain: | Affected Population |
| Range: | Emergency |
| Inverse property: | affects |
Specififes that a gap for a certain need has been identified based on a specific indicator.
| Identifier: | basedOn |
|---|---|
| Domain: | Need |
| Range: | Indicator |
| Inverse property: | indicates |
A commonly use title/name for an emergency.
| Identifier: | commonTitle |
|---|---|
| Domain: | Situation |
| Range: | http://www.w3.org/2001/XMLSchema#string |
Assigns numbers to populations. The range is intentionally not restricted to numeric values, so that rough numbers or estimates are supported.
| Identifier: | count |
|---|---|
| Domain: | Population |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the bottom of an age range for an AgeGroup (in years).
| Identifier: | fromAge |
|---|---|
| Domain: | Age Group |
| Range: | http://www.w3.org/2001/XMLSchema#int |
Assigns the GLIDE number to an Emergency.
| Identifier: | hasGLIDEnumber |
|---|---|
| Domain: | Emergency |
| Range: | GLIDE number |
A reference against which the measured value can be compared to know if it requires intervention.
| Identifier: | hasStandard |
|---|---|
| Domain: | Indicator |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
The measured value of this indicator.
| Identifier: | hasValue |
|---|---|
| Domain: | Indicator |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies when a specific need has been identified.
| Identifier: | identifiedAt |
|---|---|
| Domain: | Need |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Free-text description of how the information about the demographic methodology, where the data came from, etc.
| Identifier: | provenanceInfo |
|---|---|
| Domain: | Population |
| Range: | http://www.w3.org/2000/01/rdf-schema#Literal |
Specifies the top of an age range for an AgeGroup (in years).
| Identifier: | toAge |
|---|---|
| Domain: | Age Group |
| Range: | http://www.w3.org/2001/XMLSchema#int |
| Identifier: | http://purl.org/dc/terms/description |
|---|---|
| Domain: | Situation |
| Range: | http://www.w3.org/2001/XMLSchema#string |
The following figure gives an overview of all classes and properties defined by HXL, and how they are connected. The ellipses represent classes, whereas the arrows represent properties: Dashed lines indicate a subclass relationship (e.g. Camp is a subclass of Site). Solid lines are labeled with the property that connects these two classes.
[click to enlarge]
We still need to decide under which license this vocabulary should be published.
This Vocabulary Specification relies on W3C's RDF technology, an open Web standard that can be freely used by anyone.
This visual layout and structure of the specification was adapted from the Open Provenance Model Vocabulary edited by Jun Zhao, SIOC Core Ontology Specification edited by Uldis Bojars and John G. Breslin and the Provenance Vocabulary Core Ontology Specification edited by Olaf Hartig and Jun Zhao.
Changes compared to the previous version of the vocabulary:
Changes compared to the previous version: