@prefix rdfs: . @prefix skos: . a skos:Concept ; rdfs:seeAlso ; skos:definition "Application Schema content may be contributed through an OWL file (typically generated from a UML->OWL converter such as ShapeChange). URIs must conform to relevant OGC-NA policies. Currently this is in an experimental phase and support for URIs with root http(s)://www.opengis.net/def/schema/{wg}/{model}/{package} are required." ; skos:inScheme ; skos:prefLabel "Application Schema"@en . a skos:Concept ; rdfs:seeAlso ; skos:definition """The OGC Definitions Server publishes a range of resources managed by the OGC, and identified by unique stable web addresses (IRIs or URIs). These are determined through a set of policies managed by the OGC Naming Authority and managed through normal operational processes.\r \r The knowledge graph behind the definitions server is flexible and extensible, and the OGC will continue to register new terms and improve the cross-linkages between terms.\r \r Definitions are made available in an interoperable form using the SKOS vocabulary (or "taxonomy") model in both human- and machine-readable forms.\r \r Some definitions have richer information models with alternative profiles of the content available.\r \r Vocabularies are managed in sets called "ConceptSchemes", and definitions can usually be accessed individually as "Concepts" or via the containing set.\r \r The "alternate profiles" will provide a complete list of the available resources per definition.\r \r See the Definitions Server About Page for more information about the OGC Definitions Server.""" ; skos:inScheme ; skos:prefLabel "--- Overview"@en ; skos:topConceptOf . a skos:Concept ; skos:broader ; skos:definition """Access to the definition server is open, supported for both HTTP and HTTPS (depending on resource identifiers), and negotiated via HTTP 303 redirects. Access to download formats is managed via Content-negotiation-by-profile - and is generally available for individual concept schemes.\r \r If required, access to other views and service APS, such as SPARQL endpoints, can be negotiated via the OGC Naming Authority.""" ; skos:inScheme ; skos:prefLabel "Access"@en . a skos:Concept ; skos:broader ; skos:definition """The Definitions Server does not make any assumptions about the client software that may be used now or in the future to access definitions, other than the use of HTTP protocols. This enhances accessibility for different environments making it “platform-agnostic”.\r \r The "web-friendly" way of using an identifier (i.e. a URL) to get more information is augmented by "content negotiation" - the Definitions Server can deliver both user-friendly web pages and other forms of resource representations, e.g. JSON-LD or Turtle (TTL).""" ; skos:inScheme ; skos:prefLabel "Accessible"@en . a skos:Concept ; skos:broader ; skos:definition "Browse and search across specifications using the relationships between specifications and OGC activities." ; skos:inScheme ; skos:prefLabel "Browse specifications"@en . a skos:Concept ; skos:broader ; skos:definition "Codelists are vocabularies published as part of Application Schemas - they are generally indented to be directly implemented in data. These are treated as vocabularies, however additional metadata to relate codelists to application schemas is present. Import tools are provided for GML encoded codelists." ; skos:inScheme ; skos:prefLabel "Codelists"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "Content Negotation By Profile"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "Contributing content"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "Cross References"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "Data models"@en . a skos:Concept ; skos:broader ; skos:definition "Discover and describe available human or machine readable resources to support use of OGC specifications." ; skos:inScheme ; skos:prefLabel "Discover Implementation Resources"@en . a skos:Concept ; skos:broader ; skos:definition "Resolve a term specified with an unambiguous URI by the OGC Naming Authority or other hosted set of terms to retrieve available explanation and related terms." ; skos:inScheme ; skos:prefLabel "Explain term"@en . a skos:Concept ; skos:broader ; skos:definition """The Definitions Server is implemented using Linked Data principles - so the combination of stable URIs allows references to be made from outside, and "follow your nose" navigation via links from one term to related terms which provides enhanced findability.\r \r Currently OGC provides a limited search capability over Concept definitions, however the content is indexable by external search engines.""" ; skos:inScheme ; skos:prefLabel "Findable"@en . a skos:Concept ; skos:broader ; skos:definition "Data schemas do not typically provide much information about the semantics of the elements they contain. To determine if two schema elements are equivalent, or other information about meaning and usage, they may both be described via mapping implementation models to conceptual models. Initially this may be supported by identifying the relationship of the schema element to schema, its relationship to an implementation specification, and the relationship between that and a conceptual model. Over time fine-grained mappings of concepts to implementation schema elements may be included to provide direct links to specific concepts." ; skos:inScheme ; skos:prefLabel "Find Conceptual Basis for schema element"@en . a skos:Concept ; skos:broader ; skos:definition "A conceptual model or a concept defined by it is found, possibly starting with an alternative implementation. Implementations of the conceptual model are discoverable by links from either the specification or specific Conformance Classes (modules) defined in the specification." ; skos:inScheme ; skos:prefLabel "Find Implementations of Conceptual Model Elements"@en . a skos:Concept ; skos:broader ; skos:definition "A term, such as a schema element, API parameter etc. is discovered by either dereferencing its URI form or performing a search. The description of the term includes a link to the specification that defines it, and various forms of resource for that specification are hence discovered." ; skos:inScheme ; skos:prefLabel "Finding Specification Defining a Term"@en . a skos:Concept ; skos:broader ; skos:definition """The definitions server has a facility to import GML and ISO GMX (XML) dictionary formats into the content management system as SKOS Concept Schemes, and hence publish to the Definitions Server.\r Contact the OGC Naming Authority for assistance in this process, as batch publishing of multiple dictionaries can be arranged.""" ; skos:inScheme ; skos:prefLabel "GML dictionary import"@en . a skos:Concept ; skos:broader ; skos:definition """The interoperability of these term URI behaviours and the resources they provide access to is a key goal. There are several aspects of this handled using different mechanisms:\r \r Content model: can the client understand how \r the data is structured?\r \r Encoding: can the client parse the response?\r \r Interaction: how can a client ask for the form it needs?""" ; skos:inScheme ; skos:prefLabel "Interoperable"@en . a skos:Concept ; skos:broader ; skos:definition "Access machine readable forms of terms to support interoperability. These can be directly accessed by content type and information profile as required." ; skos:inScheme ; skos:prefLabel "Get machine readable forms"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "Resources for data models"@en . a skos:Concept ; skos:broader ; skos:definition "About the OGC Naming Authority Role" ; skos:inScheme ; skos:prefLabel "OGC Naming Authority"@en . a skos:Concept ; skos:broader ; skos:definition "Publishing OWL ontologies is handled by set of entailment rules that extract convenience views from the models - specifically an SKOS view and a ISO 19103 Feature Type view if possible - converting complex OWL restrictions into a simple Feature/Property frame. A set of resources is expected to be located in the OGC Naming Authority git repository to allow discovery and reuse of models. These include HTML renderings of model documentation, JSON-LD context documents etc." ; skos:inScheme ; skos:prefLabel "OWL ontologies"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "Profiles"@en . a skos:Concept ; skos:broader ; skos:definition "The OGC Naming Authority manages the Definitions Server to ensure all term URIs are stable with transparent governance. These identifiers can thus be safely used in external context. All content is freely available for reuse. Reuse is envisaged largely through the machine-readable versions." ; skos:inScheme ; skos:prefLabel "Reusable"@en . a skos:Concept ; skos:broader ; skos:definition """Registry Owner: OGC\r Registry Manager: OGC Naming Authority delegation\r Register Owner(s): OGC Standards Working Groups\r Register Manager: SWG delegations\r Control Body: OGC Naming authority""" ; skos:inScheme ; skos:prefLabel "Roles (ISO 19135)"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "Search"@en . a skos:Concept ; skos:broader ; skos:definition "The OGC Definitions Server uses available standards for service interfaces to maximise stability. Functionality is under the control of the OGC Naming Authority, and non-backwards compatible changes will be proposed and discussed within this forum in advance of changes. Additional capabilities may be added at any time. Dependencies on functionality should be notified, to allow for consultation and testing around changes in future. Bugs will be fixed as required. Users should not rely on non-standard behaviours, but instead report these to the Naming Authority for prompt resolution." ; skos:inScheme ; skos:prefLabel "Service behaviour"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "SKOS - (vocabulary)"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "SPARQL"@en . a skos:Concept ; skos:broader ; skos:inScheme ; skos:prefLabel "Vocabularies"@en . a skos:Concept ; rdfs:seeAlso ; skos:definition "The OGC Definitions Server is managed by the OGC Naming Authority (\"Registry Owner\" under ISO19135 model). Most content is published through OGC processes which involve registration of URIs (\"names\") for concepts defined by the OGC. The Naming Authority works via delegation to the Specification Working Group (as the \"Control Body\" for each set of resources - i.e. a \"Register\"), and acts as the \"Register Manager\" as part of its review process." ; skos:inScheme ; skos:narrower , , ; skos:prefLabel "Governance"@en ; skos:topConceptOf . a skos:Concept ; skos:broader ; skos:inScheme ; skos:narrower , ; skos:prefLabel "Supported data import options"@en . a skos:Concept ; skos:definition """The OGC Definitions server offers all content using the SKOS vocabulary, and any additional forms relevant to the content type.\r \r It handles a range of different data types in special ways, allowing additional resources to be made available to offer definitions in forms more relevant to the content. For example data models may be exposed as OWL, JSON contexts, XML schemas etc.""" ; skos:inScheme ; skos:narrower , , , ; skos:prefLabel "Content types"@en ; skos:topConceptOf . a skos:Concept ; skos:definition "FAIR principles address the aspects of resource publishing that support adoption by communities of practice. Each sub-topic represents one of these principles and examines how the Definitions Server design implements the principle." ; skos:inScheme ; skos:narrower , , , ; skos:prefLabel "FAIR principles"@en ; skos:topConceptOf . a skos:Concept ; skos:definition "Use Cases for the Definition Server" ; skos:inScheme ; skos:narrower , , , , , , ; skos:prefLabel "Use Cases"@en ; skos:topConceptOf . a skos:Concept ; skos:definition "Technical concepts provide for detailed explanations about the workings of specific aspects of the system." ; skos:inScheme ; skos:narrower , , , , , , , , ; skos:prefLabel "Technical details"@en ; skos:topConceptOf . a skos:ConceptScheme ; skos:definition """Documentation about different aspects of the OGC Definition Server. \r \r Individual topics may be linked to specific types of resource as a starting point for discovery.""" ; skos:prefLabel "About topics" .