Ontology Registry¶
This page lists all known ontologies included in the RITSO.
| Official IRI | Prefix | Description |
|---|---|---|
| http://purl.org/goodrelations/v1 | v1 | The GoodRelations ontology provides the vocabulary for annotating e-commerce offerings (1) to sell, lease, repair, dispose, or maintain commodity products and (2) to provide commodity services. GoodRelations allows describing the relationship between (1) Web resources, (2) offerings made by those Web resources, (3) legal entities, (4) prices, (5) terms and conditions, and the aforementioned ontologies for products and services (6). For more information, see http://purl.org/goodrelations/ Note: The base URI of GoodRelations is http://purl.org/goodrelations/v1. Please make sure you are only using element identifiers in this namespace, e.g. http://purl.org/goodrelations/v1#BusinessEntity. There may be copies of the ontology file on the Web which can be retrieved from other locations, BUT THOSE LOCATIONS MUST NOT BE USED AS THE BASIS OF IDENTIFIERS. If you use GoodRelations for scientific purposes, please cite our paper: Hepp, Martin: GoodRelations: An Ontology for Describing Products and Services Offers on the Web, Proceedings of the 16th International Conference on Knowledge Engineering and Knowledge Management (EKAW2008), September 29 - October 3, 2008, Acitrezza, Italy, Springer LNCS, Vol. 5268, pp. 332-347. PDF at http://www.heppnetz.de/publications/ |
| http://purl.org/goodrelations/v1/ | gr | The GoodRelations ontology provides the vocabulary for annotating e-commerce offerings (1) to sell, lease, repair, dispose, or maintain commodity products and (2) to provide commodity services. GoodRelations allows describing the relationship between (1) Web resources, (2) offerings made by those Web resources, (3) legal entities, (4) prices, (5) terms and conditions, and the aforementioned ontologies for products and services (6). For more information, see http://purl.org/goodrelations/ Note: The base URI of GoodRelations is http://purl.org/goodrelations/v1. Please make sure you are only using element identifiers in this namespace, e.g. http://purl.org/goodrelations/v1#BusinessEntity. There may be copies of the ontology file on the Web which can be retrieved from other locations, BUT THOSE LOCATIONS MUST NOT BE USED AS THE BASIS OF IDENTIFIERS. If you use GoodRelations for scientific purposes, please cite our paper: Hepp, Martin: GoodRelations: An Ontology for Describing Products and Services Offers on the Web, Proceedings of the 16th International Conference on Knowledge Engineering and Knowledge Management (EKAW2008), September 29 - October 3, 2008, Acitrezza, Italy, Springer LNCS, Vol. 5268, pp. 332-347. PDF at http://www.heppnetz.de/publications/ |
| http://purl.org/goodrelations/v1/gr-shacl | gr | SHACL node shapes that restate property domains and ranges from the GoodRelations ontology for documentation and validation tooling. |
| http://schema.org/ | schema | Schema.org is a collaborative, community activity with a mission to create, maintain, and promote schemas for structured data on the Internet. |
| http://www.opengis.net/ont/geosparql | geo | - |
| http://www.opengis.net/ont/geosparql/ | geo | An RDF/OWL vocabulary for representing spatial information |
| http://www.opengis.net/ont/geosparql/geo-shacl | geo | SHACL node shapes that restate property domains and ranges from the GeoSPARQL ontology for documentation and validation tooling. |
| http://www.w3.org/2001/XMLSchema/ | XMLSchema | Datatypes commonly used in RDF/OWL, drawn from the W3C XML Schema Definition Language. |
| http://www.w3.org/2003/01/geo/wgs84_pos/ | geo | A vocabulary for representing latitude, longitude and altitude information in the WGS84 geodetic reference datum. Version $Id: wgs84_pos.rdf,v 1.22 2009/04/20 15:00:30 timbl Exp $. See http://www.w3.org/2003/01/geo/ for more details. |
| http://www.w3.org/2006/time | time | - |
| http://www.w3.org/2006/time/ | time | - |
| http://www.w3.org/ns/org# | org | Vocabulario para describir organizaciones, adaptable a una amplia variedad de ellas. |
| http://www.w3.org/ns/org/ | org | Vocabolario per descrivere strutture organizzative, le quali possono essere specializzate in una vasta varietà di tipi di organizzazione |
| http://www.w3.org/ns/org/org-shacl | org | SHACL node shapes that restate property domains and ranges from the W3C Organization ontology for documentation and validation tooling. |
| http://www.w3.org/ns/prov# | prov | This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/ Archives/Public/public-prov-comments/). All feedback is welcome. |
| http://www.w3.org/ns/prov-aq# | prov-aq | 0.2 |
| http://www.w3.org/ns/prov-dc# | prov-dc | This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. |
| http://www.w3.org/ns/prov-dictionary# | prov-dictionary | This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. |
| http://www.w3.org/ns/prov-links# | prov-links | This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/ ). All feedback is welcome. |
| http://www.w3.org/ns/prov-o# | prov-o | This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/Archives/Public/public-prov-comments/). All feedback is welcome. |
| http://www.w3.org/ns/prov-o-inverses# | prov-o-inverses | - |
| http://www.w3.org/ns/prov/ | prov | This document is published by the Provenance Working Group (http://www.w3.org/2011/prov/wiki/Main_Page). If you wish to make comments regarding this document, please send them to public-prov-comments@w3.org (subscribe public-prov-comments-request@w3.org, archives http://lists.w3.org/ Archives/Public/public-prov-comments/). All feedback is welcome. |
| http://www.w3.org/ns/sosa/ | sosa | This ontology is based on the SSN Ontology by the W3C Semantic Sensor Networks Incubator Group (SSN-XG), together with considerations from the W3C/OGC Spatial Data on the Web Working Group. |
| http://www.w3.org/ns/ssn/ | ssn | This ontology describes sensors, actuators and observations, and related concepts. It does not describe domain concepts, time, locations, etc. these are intended to be included from other ontologies via OWL imports. |
| http://xmlns.com/foaf/0.1/ | 0.1 | The Friend of a Friend (FOAF) RDF vocabulary, described using W3C RDF Schema and the Web Ontology Language. |
| https://w3id.org/citydata/21972/v1 | i72 | Archived import of iso21972.owl on 13-Jan-2021 Draft version of the ISO 21972 Ontology. Includes a subset of the GCI Foundation ontology by: Fox, M.S. (2015) “The Role of Ontologies in Publishing and Analyzing City Indicators”, Computers, Environment and Urban Systems, Vol. 54, pp. 266-279. Includes a subset of the OM ontology by: Rijgersberg, H., Wigham, M., and Top, J.L., (2011), “How Semantics can Improve Engineering Processes: A Case of Units of Measure and Quantities”, Advanced Engineering Informatics, Vol. 25, pp. 276-287. and the GovStat ontology by: Pattuelli, M.C., (2003), “The GovStat Ontology: Technical Report”. The GovStat Project, Integration Design Laboratory, School of Information and Library Science, University of North Carolina at Chapel Hill, http://ils.unc.edu/govstat/papers/govstatontology.doc. |
| https://w3id.org/citydata/21972/v1/ | i72 | This ontology imports the ISO 21972 modules (core pattern, indicators pattern, and SHACL constraints). |
| https://w3id.org/citydata/21972/v1/CorePattern | i72 | Core organisational concepts for the ISO 21972 upper-level ontology for smart city indicators. |
| https://w3id.org/citydata/21972/v1/IndicatorsPattern | i72 | Concepts for quantities, units of measure, measurement scales, statistics, and smart city indicators from ISO 21972. |
| https://w3id.org/citydata/21972/v1/IndicatorsSHACL | i72 | Validation shapes derived from qualified cardinality restrictions in the Indicators pattern. |
| https://w3id.org/citydata/part1/v1/ | cdm1 | This ontology specifies the foundation-level concepts of the city data model. |
| https://w3id.org/citydata/part1/v1/ActivityPattern | cdm1 | This ontology specifies the foundation-level concepts related to the activity pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/ActivityPattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the activity pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/ActivityPattern/shacl | cdm1 | SHACL validation shapes for the Activity Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/AgentPattern | cdm1 | This ontology specifies the foundation-level concepts related to the agent pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/AgentPattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the agent pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/AgentPattern/shacl | cdm1 | SHACL validation shapes for the Agent Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/AgreementPattern | cdm1 | This ontology specifies the foundation-level concepts related to the agreement pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/AgreementPattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the agreement pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/AgreementPattern/shacl | cdm1 | SHACL validation shapes for the Agreement Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/ChangePattern | cdm1 | This ontology specifies the foundation-level concepts related to the change pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/ChangePattern/shacl | cdm1 | SHACL validation shapes for the Change Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/CityUnitsPattern | cdm1 | This ontology specifies the foundation-level concepts related to the city units pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/CityUnitsPattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the city units pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/CityUnitsPattern/shacl | cdm1 | SHACL validation shapes for the City Units Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/Core | cdm1 | This ontology specifies the foundation-level concepts that are used by all other patterns of the city data model. |
| https://w3id.org/citydata/part1/v1/Core/shacl | cdm1 | SHACL validation shapes for the Core pattern module. |
| https://w3id.org/citydata/part1/v1/CorePattern | cdm1 | This ontology specifies the foundation-level concepts that are used by all other patterns of the city data model. |
| https://w3id.org/citydata/part1/v1/GenericPropertiesPattern | cdm1 | This ontology specifies the foundation-level concepts related to the generic properties pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/GenericPropertiesPattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the generic properties pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/GenericPropertiesPattern/shacl | cdm1 | SHACL validation shapes for the Generic Properties Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/MereologyPattern | cdm1 | This ontology specifies the foundation-level concepts related to the mereology pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/MereologyPattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the mereology pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/MereologyPattern/shacl | cdm1 | SHACL validation shapes for the Mereology Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/OrganizationStructurePattern | cdm1 | This ontology specifies the foundation-level concepts related to the organization structure pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/OrganizationStructurePattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the organization structure pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/OrganizationStructurePattern/shacl | cdm1 | SHACL validation shapes for the Organization Structure Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/RecurringEventPattern | cdm1 | This ontology specifies the foundation-level concepts related to the recurring event pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/RecurringEventPattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the recurring event pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/RecurringEventPattern/shacl | cdm1 | SHACL validation shapes for the Recurring Event Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/ResourcePattern | cdm1 | This ontology specifies the foundation-level concepts related to the resource pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/ResourcePattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the resource pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/ResourcePattern/shacl | cdm1 | SHACL validation shapes for the Resource Pattern pattern module. |
| https://w3id.org/citydata/part1/v1/SpatialLocPattern | cdm1 | This ontology specifies the foundation-level concepts related to the spatial location pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/SpatialLocPattern/ | cdm1 | This ontology specifies the foundation-level concepts related to the spatial location pattern of the city data model. |
| https://w3id.org/citydata/part1/v1/SpatialLocPattern/shacl | cdm1 | SHACL validation shapes for the Spatial Loc Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/ | cdm2 | This ontology specifies the city-level concepts of the city data model. |
| https://w3id.org/citydata/part2/v1/AlertPattern | cdm2 | This ontology specifies the city-level concepts for the alert pattern of the city data model. |
| https://w3id.org/citydata/part2/v1/AlertPattern/shacl | cdm2 | SHACL validation shapes for the Alert Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/AlertSHACL | cdm2 | SHACL validation shapes for the Alert Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/BuildingPattern | cdm2 | This ontology specifies the city-level concepts for the building pattern of the city data model. A Building is a structure with some location in the urban system. The location of the Building in space may change due to construction, but the Parcel/Lot of land it is located on cannot. There may be many different types (subclasses) of buildings, such as House, Apartment Building, Office Building, and so on. |
| https://w3id.org/citydata/part2/v1/BuildingPattern/shacl | cdm2 | SHACL validation shapes for the Building Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/BuildingSHACL | cdm2 | SHACL validation shapes for the Building Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/BylawPattern | cdm2 | This ontology specifies the city-level concepts for the bylaw pattern of the city data model. |
| https://w3id.org/citydata/part2/v1/BylawPattern/shacl | cdm2 | SHACL validation shapes for the Bylaw Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/BylawSHACL | cdm2 | SHACL validation shapes for the Bylaw Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/CityPattern | cdm2 | This ontology specifies the city-level concepts for the city pattern of the city data model. The City pattern captures basic information about the geospatial aspects of the city. In particular it represents the different ways in which the city is administratively divided. |
| https://w3id.org/citydata/part2/v1/CityPattern/ | cdm2 | This ontology specifies the city-level concepts for the city pattern of the city data model. The City pattern captures basic information about the geospatial aspects of the city. In particular it represents the different ways in which the city is administratively divided. |
| https://w3id.org/citydata/part2/v1/CityPattern/shacl | cdm2 | SHACL validation shapes for the City Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/CityResidentPattern | cdm2 | This ontology specifies the city-level concepts for the city resident pattern of the city data model. As different cities have different definitions of who is that city's Resident, the City Resident Pattern must contain the properties required by each. Central to all of the definitions is the concept of residing. Variously referred to as a home or domicile in which the resident spends significant amounts of time. They may own it, rent it or just stay in it. Legally, “reside means to dwell permanently or continuously. It expresses an idea that a person keeps or returns to a particular dwelling place as his fixed, settled, or legal abode. The meaning of reside implies a continuous arrangement” ; reside has both a temporal and spatial dimension. The city of Toronto's definition of a city resident includes the concept of owning property or owning or operating a business in the city. For Beijing, nationality is a unique aspect. |
| https://w3id.org/citydata/part2/v1/CityResidentPattern/shacl | cdm2 | SHACL validation shapes for the City Resident Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/CityResidentSHACL | cdm2 | SHACL validation shapes for the City Resident Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/CityServicePattern | cdm2 | This ontology specifies the city-level concepts for the city service pattern of the city data model. Cities provide a variety of services to residents and businesses, including health and social services. The city service ontology, is based on the Canadian Government Reference Model (CGRM). See Wiseman, R. (2015). Canadian Governments Reference Models. In Service Systems Science (pp. 109-128). Springer, Tokyo. |
| https://w3id.org/citydata/part2/v1/CityServicePattern/shacl | cdm2 | SHACL validation shapes for the City Service Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/CityServiceSHACL | cdm2 | SHACL validation shapes for the City Service Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/CitySHACL | cdm2 | SHACL validation shapes for the City Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/CodePattern | cdm2 | This ontology specifies the city-level concepts for the code pattern of the city data model. The Code Pattern provides a structure to address the challenge of value enumeration with a general approach. In city data there are many classes of things that are intended to be instantiated using a set list of values (e.g., classification systems), however these values may change based on application or context. The Code Pattern introduces a generic set of classes and properties that can be used to extend such classes to define various classification systems in an integrated way. Instead of enumerating value sets for classes, values can be defined with an associated Code that specifies additional metadata about the value and its origins. |
| https://w3id.org/citydata/part2/v1/CodePattern/ | cdm2 | This ontology specifies the city-level concepts for the code pattern of the city data model. The Code Pattern provides a structure to address the challenge of value enumeration with a general approach. In city data there are many classes of things that are intended to be instantiated using a set list of values (e.g., classification systems), however these values may change based on application or context. The Code Pattern introduces a generic set of classes and properties that can be used to extend such classes to define various classification systems in an integrated way. Instead of enumerating value sets for classes, values can be defined with an associated Code that specifies additional metadata about the value and its origins. |
| https://w3id.org/citydata/part2/v1/CodePattern/shacl | cdm2 | SHACL validation shapes for the Code Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/CodeSHACL | cdm2 | SHACL validation shapes for the Code Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/ContactPattern | cdm2 | This ontology specifies the city-level concepts for the contact pattern of the city data model. |
| https://w3id.org/citydata/part2/v1/ContactPattern/shacl | cdm2 | SHACL validation shapes for the Contact Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/ContactSHACL | cdm2 | SHACL validation shapes for the Contact Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/ContractPattern | cdm2 | This ontology specifies the city-level concepts for the contract pattern of the city data model. A contract is a legal document that specifies some agreement(s) between two or more parties. The aim of the contract pattern is not to formalize the semantics of all possible involved legal concepts, but rather to enable to representation of the general structure and contents of a particular contract. The Contract Ontology adopts the definition of Contract specified in the Financial Business Ontology (FIBO) [8] specified at: https://spec.edmcouncil.org/fibo/ontology/FND/Agreements/Contracts/ with a key modification that a Contract is defined as a type of Document and is distinct from an Agreement (not a subclass, as specified in FIBO). |
| https://w3id.org/citydata/part2/v1/ContractPattern/shacl | cdm2 | SHACL validation shapes for the Contract Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/ContractSHACL | cdm2 | SHACL validation shapes for the Contract Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/Core | cdm2 | This ontology specifies the city-level concepts that are used by all other patterns of the city-level portion of the city data model. |
| https://w3id.org/citydata/part2/v1/Core/ | cdm2 | This ontology specifies the city-level concepts that are used by all other patterns of the city-level portion of the city data model. |
| https://w3id.org/citydata/part2/v1/Core/shacl | cdm2 | SHACL validation shapes for the Core pattern module. |
| https://w3id.org/citydata/part2/v1/CorePattern | cdm2 | This ontology specifies the city-level concepts that are used by all other patterns of the city-level portion of the city data model. |
| https://w3id.org/citydata/part2/v1/CoreSHACL | cdm2 | SHACL validation shapes for the Core pattern module. |
| https://w3id.org/citydata/part2/v1/HouseholdPattern | cdm2 | This ontology specifies the city-level concepts for the household pattern of the city data model. The Household pattern captures basic information about households within the city. In particular it represents the different types and structures of households. |
| https://w3id.org/citydata/part2/v1/HouseholdPattern/shacl | cdm2 | SHACL validation shapes for the Household Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/HouseholdSHACL | cdm2 | SHACL validation shapes for the Household Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/InfrastructurePattern | cdm2 | This ontology specifies the city-level concepts for the infrastructure pattern of the city data model. The Infrastructure pattern defines the concepts needed to capture various types of city infrastructure, such as buildings and roads. The Infrastructure pattern reuses the Spatial Location pattern (from ISO 5087-1) in order to capture the location of these infrastructure elements. |
| https://w3id.org/citydata/part2/v1/InfrastructurePattern/shacl | cdm2 | SHACL validation shapes for the Infrastructure Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/InfrastructureSHACL | cdm2 | SHACL validation shapes for the Infrastructure Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/LandUsePattern | cdm2 | This ontology specifies the city-level concepts for the land use pattern of the city data model. The Land Use Pattern captures concepts related to land use and cover over time. Land Use Classifications provide a means of describing the land cover/use in a standard way. Various classification systems are used to identify types of land use. Currently, we include LBCS, CLUMP, and AAFC. The ontology reuses and extends the Land Based Classification Standards (LBCS) Ontology presented by (Montenegro, Gomes, Urbano, and Duarte, 2011) for this purpose. |
| https://w3id.org/citydata/part2/v1/LandUsePattern/ | cdm2 | This ontology specifies the city-level concepts for the land use pattern of the city data model. The Land Use Pattern captures concepts related to land use and cover over time. Land Use Classifications provide a means of describing the land cover/use in a standard way. Various classification systems are used to identify types of land use. Currently, we include LBCS, CLUMP, and AAFC. The ontology reuses and extends the Land Based Classification Standards (LBCS) Ontology presented by (Montenegro, Gomes, Urbano, and Duarte, 2011) for this purpose. |
| https://w3id.org/citydata/part2/v1/LandUsePattern/shacl | cdm2 | SHACL validation shapes for the Land Use Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/LandUseSHACL | cdm2 | SHACL validation shapes for the Land Use Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/OrganizationPattern | cdm2 | This ontology specifies the city-level concepts for the organization pattern of the city data model. The Organization pattern is an extension of the Organization Structure pattern defined in ISO/IEC 5087-1 that introduces city-specific concepts related to Organizations such as Students and Employees. |
| https://w3id.org/citydata/part2/v1/OrganizationPattern/shacl | cdm2 | SHACL validation shapes for the Organization Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/OrganizationSHACL | cdm2 | SHACL validation shapes for the Organization Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/PersonPattern | cdm2 | This ontology specifies the city-level concepts for the person pattern of the city data model. |
| https://w3id.org/citydata/part2/v1/PersonPattern/shacl | cdm2 | SHACL validation shapes for the Person Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/PersonSHACL | cdm2 | SHACL validation shapes for the Person Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/TransportInfrastructurePattern | cdm2 | This ontology specifies the city-level concepts for the transport infrastructure pattern of the city data model. The Transportation Infrastructure pattern defines the concepts that are relevant in describing the physical transportation infrastructure and their characteristics. This includes the concepts of a Road, Bridge, and Tunnel. The Infrastructure Pattern is reused here, as these transportation structures are all defined as types of (subclasses) Infrastructure Elements. |
| https://w3id.org/citydata/part2/v1/TransportInfrastructurePattern/shacl | cdm2 | SHACL validation shapes for the Transport Infrastructure Pattern pattern module. |
| https://w3id.org/citydata/part2/v1/TransportInfrastructureSHACL | cdm2 | SHACL validation shapes for the Transport Infrastructure Pattern pattern module. |
| https://w3id.org/citydata/part3/v1/ | cdm3 | This ontology specifies the service-level concepts defined for the transport service of the city data model. |
| https://w3id.org/citydata/part3/v1/Core/ | cdm3 | This ontology specifies the service-level concepts defined for the transport service of the city data model. |
| https://w3id.org/citydata/part3/v1/CoreSHACL | cdm3 | SHACL validation shapes for the Core pattern module, including reusable cardinality shapes. |
| https://w3id.org/citydata/part3/v1/MicromobilityNetworkPattern/ | cdm3 | This ontology specifies the micromobility network pattern of the transport service of the city data model. |
| https://w3id.org/citydata/part3/v1/MicromobilityNetworkSHACL | cdm3 | SHACL validation shapes for the MicromobilityNetwork Pattern module. |
| https://w3id.org/citydata/part3/v1/PedestrianNetworkPattern/ | cdm3 | This ontology specifies the pedestrian network pattern of the transport service in the city data model. |
| https://w3id.org/citydata/part3/v1/PedestrianNetworkSHACL | cdm3 | SHACL validation shapes for the PedestrianNetwork Pattern module. |
| https://w3id.org/citydata/part3/v1/PublicTransportSystemPattern/ | cdm3 | This ontology specifies the service-level concepts for transport in the city data model. |
| https://w3id.org/citydata/part3/v1/PublicTransportSystemSHACL | cdm3 | SHACL validation shapes for the PublicTransportSystem Pattern module. |
| https://w3id.org/citydata/part3/v1/RailNetworkPattern/ | cdm3 | This ontology specifies the service-level concepts for rail transport in the city data model. |
| https://w3id.org/citydata/part3/v1/RailNetworkSHACL | cdm3 | SHACL validation shapes for the RailNetwork Pattern module. |
| https://w3id.org/citydata/part3/v1/RoadNetworkPattern/ | cdm3 | This ontology specifies the service-level concepts for road transport in the city data model. |
| https://w3id.org/citydata/part3/v1/RoadNetworkSHACL | cdm3 | SHACL validation shapes for the RoadNetwork Pattern module. |
| https://w3id.org/citydata/part3/v1/TransportAlertPattern/ | cdm3 | This ontology specifies the city-level concepts for the transport alert pattern for the transport domain. |
| https://w3id.org/citydata/part3/v1/TransportAlertSHACL | cdm3 | SHACL validation shapes for the TransportAlert Pattern module. |
| https://w3id.org/citydata/part3/v1/TransportNetworkPattern/ | cdm3 | This ontology specifies the transport network pattern of the transport service of the city data model. |
| https://w3id.org/citydata/part3/v1/TransportNetworkSHACL | cdm3 | SHACL validation shapes for the TransportNetwork Pattern module. |
| https://w3id.org/citydata/part3/v1/TravelCorridorPattern/ | cdm3 | This ontology specifies the service-level concepts for the travel corridor pattern in the city data model. |
| https://w3id.org/citydata/part3/v1/TravelCorridorSHACL | cdm3 | SHACL validation shapes for the TravelCorridor Pattern module. |
| https://w3id.org/itsdata/agent/v1/ | its-agent | This ontology defines concepts related to ITS agents. |
| https://w3id.org/itsdata/core/v1/ | its-core | This ontology defines core concepts related to intelligent transport systems (ITS). |
| https://w3id.org/itsdata/core/v1/CoreSHACL | its-core | Reusable SHACL shapes shared across ITS ontology topic areas. |
| https://w3id.org/itsdata/location/v1/AreaPattern | its-location | Methodology module for area-based locations and area location geometries. |
| https://w3id.org/itsdata/location/v1/AreaSHACL | its-location | SHACL shapes for area-based locations and area geometries. |
| https://w3id.org/itsdata/location/v1/ItineraryPattern | its-location | Methodology module for itineraries (ordered sets of features) and itinerary geometries. |
| https://w3id.org/itsdata/location/v1/ItinerarySHACL | its-location | SHACL shapes for itineraries and itinerary geometries. |
| https://w3id.org/itsdata/location/v1/ItsLocation | its-location | Ontology that imports pattern modules (core, point, linear, area, and itinerary) that define the concepts for location referencing. |
| https://w3id.org/itsdata/location/v1/LinearPattern | its-location | Methodology module for linear elements, linear locations, and linear location geometries. |
| https://w3id.org/itsdata/location/v1/LinearSHACL | its-location | SHACL shapes for linear elements, linear locations, and linear geometries. |
| https://w3id.org/itsdata/location/v1/LocationCorePattern | its-location | Core abstractions for spatial concepts, including features, geometries, and feature collections used across multiple location-referencing methodologies. |
| https://w3id.org/itsdata/location/v1/LocationCoreSHACL | its-location | SHACL shapes for core location domain abstractions (features, geometries, coded geometry, and collections). |
| https://w3id.org/itsdata/location/v1/PointPattern | its-location | A module of the ITS Location Ontology that defines concepts for point-based locations and geometries of those locations. |
| https://w3id.org/itsdata/location/v1/PointSHACL | its-location | SHACL shapes for point-based locations and point geometries. |
| https://w3id.org/itsdata/regulation/v1/ConditionPattern | its-regulation | This ontology defines concepts related to traffic regulations. |
| https://w3id.org/itsdata/regulation/v1/ConditionSHACL | its-regulation | Validation shapes for traffic regulation condition concepts. |
| https://w3id.org/itsdata/regulation/v1/ConditionVehicleAlignment | its-regulation | Alignment axioms that classify selected ITS vehicle code classes as specializations of ConditionCode for use in traffic regulation conditions. The vehicle classes remain defined in its-vehicle; this module only asserts their use as condition codes. |
| https://w3id.org/itsdata/regulation/v1/CorePattern | its-regulation | This document defines the core concepts related to the Traffic Regulation topic area of the ITS Ontology. |
| https://w3id.org/itsdata/regulation/v1/ITSRegulation/ | its-regulation | This ontology imports the Traffic Regulation topic area modules (core, patterns, and constraints). |
| https://w3id.org/itsdata/regulation/v1/PermitPattern | its-regulation | This ontology defines concepts related to permits. |
| https://w3id.org/itsdata/regulation/v1/PermitSHACL | its-regulation | Validation shapes for traffic regulation permit concepts. |
| https://w3id.org/itsdata/regulation/v1/RegulationSHACL | its-regulation | Validation shapes for traffic regulation concepts. |
| https://w3id.org/itsdata/regulation/v1/TrafficControlDevicePattern | its-regulation | This ontology defines concepts related to traffic control devices. |
| https://w3id.org/itsdata/regulation/v1/TrafficControlDeviceSHACL | its-regulation | Validation shapes for traffic control device concepts. |
| https://w3id.org/itsdata/regulation/v1/TrafficRegulationPattern | its-regulation | This ontology defines concepts related to traffic regulations. |
| https://w3id.org/itsdata/time/v1/ | its-time | This ontology imports the concepts from the various Time Ontology for ITS patterns and bundles them into a single ontology. |
| https://w3id.org/itsdata/time/v1/CorePattern | its-time | This ontology defines core concepts related to time within Intelligent Transportation Systems (ITS). This module is used to import the core concepts from the various Time Ontology for ITS patterns. |
| https://w3id.org/itsdata/time/v1/FuzzyTimePattern | its-time | This ontology defines concepts related to fuzzy time within Intelligent Transportation Systems (ITS). This pattern is one module of the Time Ontology for ITS. |
| https://w3id.org/itsdata/time/v1/FuzzyTimeSHACL | its-time | This ontology defines the SHACL rules for concepts related to fuzzy time within Intelligent Transportation Systems (ITS). |
| https://w3id.org/itsdata/time/v1/ReqView | ReqView | This ontology defines the identifiers used by ReqView to manage traceability and use of ontology concepts within ITS. |
| https://w3id.org/itsdata/time/v1/SchedulePattern | its-time | This ontology defines concepts related to schedules for temporal validity in traffic and transport situations. This pattern is one module of the Time Ontology for ITS. |
| https://w3id.org/itsdata/time/v1/ScheduleSHACL | its-time | This ontology defines the SHACL rules for concepts related to schedules within Intelligent Transportation Systems (ITS). |
| https://w3id.org/itsdata/transport-network/v1/ItsTransportNetwork | its-tn | Ontology that imports the transport-network pattern modules for transport-network, road, rail, pedestrian, micromobility, public transport, travel corridor, and alerts. All transport network elements are derived from geo:Feature via imports of the ITS Location ontology. |
| https://w3id.org/itsdata/transport-network/v1/MicromobilityNetworkPattern | its-tn | This pattern defines micromobility network concepts, which are derived from ITS Location features and can be presented with multiple geometries. |
| https://w3id.org/itsdata/transport-network/v1/MicromobilityNetworkSHACL | its-transport-network | SHACL node shapes for micromobility-network classes, which inherit constraints from the ITS Location ontology. |
| https://w3id.org/itsdata/transport-network/v1/PedestrianNetworkPattern | its-tn | This pattern defines pedestrian network concepts, which are derived from ITS Location features and can be presented with multiple geometries. |
| https://w3id.org/itsdata/transport-network/v1/PedestrianNetworkSHACL | its-transport-network | SHACL node shapes for pedestrian-network classes, which inherit constraints from the ITS Location ontology. |
| https://w3id.org/itsdata/transport-network/v1/PublicTransportSystemPattern | its-tn | This pattern defines public transport system concepts, which are derived from ITS Location features and can be presented with multiple geometries. |
| https://w3id.org/itsdata/transport-network/v1/PublicTransportSystemSHACL | its-transport-network | SHACL node shapes for public-transport-system classes, which inherit constraints from the ITS Location ontology. |
| https://w3id.org/itsdata/transport-network/v1/RailNetworkPattern | its-tn | This pattern defines rail network concepts, which are derived from ITS Location features and can be presented with multiple geometries. |
| https://w3id.org/itsdata/transport-network/v1/RailNetworkSHACL | its-transport-network | SHACL node shapes for rail-network classes, which inherit constraints from the ITS Location ontology. |
| https://w3id.org/itsdata/transport-network/v1/RoadNetworkPattern | its-tn | This pattern defines road network concepts, which are derived from ITS Location features and can be presented with multiple geometries. |
| https://w3id.org/itsdata/transport-network/v1/RoadNetworkSHACL | its-transport-network | SHACL node shapes for road-network classes, which inherit constraints from the ITS Location ontology. |
| https://w3id.org/itsdata/transport-network/v1/TransportAlertPattern | its-tn | Transport alert concepts that are relevant to the transport network. |
| https://w3id.org/itsdata/transport-network/v1/TransportAlertSHACL | its-transport-network | SHACL node shapes for transport-alert classes. |
| https://w3id.org/itsdata/transport-network/v1/TransportNetworkPattern | its-tn | Core abstractions shared across transport network pattern modules (road, rail, pedestrian, micromobility, public transport, travel corridor, alerts), grounded on the ITS Location ontology features and geometries. |
| https://w3id.org/itsdata/transport-network/v1/TransportNetworkSHACL | its-transport-network | SHACL node shapes for core transport-network classes shared across pattern modules. |
| https://w3id.org/itsdata/transport-network/v1/TravelCorridorPattern | its-tn | Travel corridor concepts that are derived from ITS Location features and can be presented with multiple geometries. |
| https://w3id.org/itsdata/transport-network/v1/TravelCorridorSHACL | its-transport-network | SHACL node shapes for travel-corridor classes, which inherit constraints from the ITS Location ontology. |
| https://w3id.org/itsdata/vehicle/v1/ITSVehicle | its-vehicle | This ontology imports the Vehicle topic area modules. |
| https://w3id.org/itsdata/vehicle/v1/VehicleCharacteristicsPattern | its-vehicle | This ontology defines patterns for vehicle characteristics. |
| https://w3id.org/itsdata/vehicle/v1/VehicleCharacteristicsSHACL | its-vehicle | Validation shapes for vehicle characteristics concepts. |