• Tidak ada hasil yang ditemukan

GML CR - replace dictionary schema with SKOS

N/A
N/A
Protected

Academic year: 2017

Membagikan "GML CR - replace dictionary schema with SKOS"

Copied!
7
0
0

Teks penuh

(1)

Open Geospatial Consortium

OGC Doc 08-111r2

CR-Form-v3

CHANGE REQUEST

GML CR 08-111

 rev

2

 Current version: 3.2.1 

For

HELP

 

on using this form, see bottom of this page or look at the pop-up text over the  symbols.

Proposed change affects:  AS Imp Spec X Best Practices Paper Other

Title:  Replace GML Dictionary/Definition components with SKOS

Source:  CSIRO, JRC

Work item code:Date:  2009-12-03

Category:C

Use one of the following categories:

F (Critical correction)

A (corresponds to a correction in an earlier release)

B (Addition of feature),

C (Functional modification of feature)

D (Editorial modification)

Detailed explanations of the above categories can be found in the TC Policies and Procedures.

Reason for change:A generic Definition and Dictionary encoding was included in GML. It was

developed as a stop-gap, pending the availability of a suitable general purpose dictionary model. Users are directed towards other tools for dictionary applications by this note in 15.1:

"

However, the GML dictionary components are not intended to provide direct support for complex taxonomies, ontologies or thesauri.

Specialized XML tools are available to satisfy the more sophisticated requirements."

Like the rest of GML it is defined in XML Schema.

Since the GML Dictionary schema was developed, standards on this topic within the broader web community have emerged and matured. In particular the Simplified Knowledge Organization System (SKOS) is an OWL/RDF-based encoding for concepts grouped in concept-schemes and collections with thesaurus-type relationships supported directly. SKOS is functional replacement for GML Dictionary/Definition, with significant support for vocabulary maintenance (e.g. Protégé plugin, TopBraid composer) and persistence and query (Jena, Sesame triple stores; SPARQL query language) and growing adoption in the web community. The GML community would benefit from adopting a mainstream tool for this purpose, and save itself the burden of maintaining a bespoke standard.

Note, however, that the GML Units of Measure and Coordinate Reference Systems schemas are implemented as extensions of the GML Definition schema. In order to continue to support the functionality of these components, more specific solutions will be required.

(2)

secondary example below, but there is active work in this area by authoritative groups outside of OGC (one initiative includes Gunther Schadow who is the principal developer of UCUM which we already use). It is likely that there will be a suitable RDF-based model available on the timescale required for GML v4, so full resolution of this issue should be deferred.

In the case of CRS, where our community does have expertise that is not duplicated externally, we have a responsibility to define the encoding. The simplest approach would be a standard encoding of the ISO 19111 UML following the Annex E encoding rule. However, this should be removed from the core GML specification and specified in a separate document and namespace, as suggested in CR 08-114.

Summary of change: (GML 4)

Add the following to the normative references (clause 3): SKOS Simple Knowledge Organization System Reference W3C Recommendation 18 August 2009.

http://www.w3.org/TR/skos-reference

Turtle - Terse RDF Triple Language W3C Team Submission 14 January 2008

http://www.w3.org/TeamSubmission/turtle/

Replace Clause 15 .with the following: 15. Definitions and Dictionaries

Terms and their definitions are OFTEN required in GML instance data. Standard methods to formalize and serialize these are available by the Semantic Web framework provided by W3C. In particular SKOS [SKOS] offers functionality that covers the scope of most ‘controlled vocabulary’ applications that are likely to be used in gml applications.

NOTE Earlier versions of GML specified a dictionary and definition schema. The widespread adoption of OWL and SKOS has now made this redundant, so GML v4 no longer provides a dictionary encoding. The following illustrates how the dictionary example provided in GML v3 may be represented in SKOS using ‘turtle’ syntax [TURTLE]:

# $Id: GMLDictionarySKOS.turtle,v 1.0 2008/08/01 sjdc Exp $

@prefix skos: <http://www.w3.org/2004/02/skos/core#>. @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. @prefix dc: <http://purl.org/dc/elements/1.1/>.

@prefix gml: <http://www.opengis.net/gml/3.2/>.

gml:AbridgedGMLdictionary rdf:type skos:ConceptScheme; dc:title "GML Dictionary";

dc:description "Abridged GML dictionary"; skos:prefLabel "GML Dictionary".

gml:term4_1 rdf:type skos:Concept;

skos:prefLabel "application schema";

(3)

applications";

skos:inScheme gml:AbridgedGMLdictionary.

gml:term4_2 rdf:type skos:Concept;

skos:prefLabel "GML application schema";

skos:definition "application schema written in XML Schema in accordance with the rules specified in ISO 19136";

skos:inScheme gml:AbridgedGMLdictionary.

gml:term4_3 rdf:type skos:Concept; skos:prefLabel "association";

skos:definition "semantic relationship between two or more classifiers that specifies connections among their instances";

skos:inScheme gml:AbridgedGMLdictionary.

gml:term4_4 rdf:type skos:Concept; skos:prefLabel "attribute";

skos:definition "name-value pair contained in an element"; skos:inScheme gml:AbridgedGMLdictionary.

An extension of SKOS schema for units of measure is shown in the the next example:

# $Id: GMLUnitsSKOS.turtle,v 1.0 2008/08/03 sjdc Exp $

@prefix skos: <http://www.w3.org/2004/02/skos/core#>. @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xs: <http://www.w3.org/2001/XMLSchema#> . @prefix gml: <http://www.opengis.net/gml/3.2/>.

gml:UnitDefinition rdf:type rdfs:Class; rdfs:subClassOf skos:Concept.

gml:quantityType rdf:type rdfs:Property;

rdfs:subPropertyOf skos:semanticRelation; rdfs:domain gml:UnitDefinition.

gml:symbol rdf:type rdfs:Property; rdfs:subPropertyOf skos:label; rdfs:domain gml:UnitDefinition.

(4)

rdfs:subClassOf gml:UnitDefinition.

#use skos:inScheme for unitsSystem

gml:DerivedUnit rdf:type rdfs:Class;

rdfs:subClassOf gml:UnitDefinition.

gml:derivationUnit rdf:type rdfs:Property; rdfs:range gml:UnitExponent; rdfs:domain gml:DerivedUnit; rdfs:domain gml:ConventionalUnit.

gml:UnitExponent rdf:type rdfs:Class.

gml:unit rdf:type rdfs:Property;

rdfs:domain gml:UnitExponent; rdfs:domain gml:UnitFactor; rdfs:range gml:UnitDefinition.

gml:exponent rdf:type rdfs:Property; rdfs:domain gml:UnitExponent; rdfs:range xs:integer.

gml:ConventionalUnit rdf:type rdfs:Class; rdfs:subClassOf gml:UnitDefinition.

gml:conversionToPreferredUnit rdf:type rdfs:Property; rdfs:range gml:UnitFactor;

rdfs:domain gml:ConventionalUnit.

gml:UnitFactor rdf:type rdfs:Class.

gml:factor rdf:type rdfs:Property; rdfs:domain gml:UnitFactor; rdfs:range xs:double.

The units schema above is illustrated in the following sample dictionary of units of measure.

gml:Units rdf:type skos:Collection;

skos:prefLabel "Units Dictionary";

(5)

skos:member gml:SIDerivedUnits; skos:member gml:ConventionalUnits.

gml:SIBaseUnits rdf:type skos:ConceptScheme; skos:prefLabel "SI Base Units";

skos:note "The Base Units from the SI units system"; skos:hasTopConcept gml:m.

gml:SIDerivedUnits rdf:type skos:ConceptScheme; skos:prefLabel "SI Derived Units";

skos:note "The Derived Units from the SI units system. These are all derived as a product of SI Base Units, except degrees Celsius in which the conversion formaula to the SI Base Unit (kelvin) involves an offset. ";

skos:hasTopConcept gml:rad.

gml:ConventionalUnits rdf:type skos:ConceptScheme; skos:prefLabel "Conventional Units";

skos:note "A collection of Conventional Units. These are units of measure which are either widely used or important within a specific community. For most of these there is

1. a known derivation from more primitive units, which may or may not be SI Base Units, or

2. a known conversion to a preferred unit, which may or may not be an SI Base or Derived unit, through rescaling and offset,

or both.".

gml:m rdf:type gml:BaseUnit; skos:prefLabel "metre";

skos:prefLabel "meter"@en_US;

skos:definition "The metre is the length of the path travelled by light in vacuum during a time interval of 1/299 792 458 of a second";

skos:inScheme gml:SIBaseUnits; gml:symbol "m";

gml:quantityType "length".

gml:rad rdf:type gml:DerivedUnit; skos:prefLabel "radian";

skos:definition "The metre is the length of the path travelled by light in vacuum during a time interval of 1/299 792 458 of a second";

skos:inScheme gml:SIDerivedUnits; gml:symbol "rad";

(6)

[ gml:unit gml:m; gml:exponent "1"]; gml:derivationUnit

[ gml:unit gml:m; gml:exponent "-1"].

gml:m3 rdf:type gml:DerivedUnit; skos:prefLabel "cubic metre";

skos:inScheme gml:ConventionalUnits; gml:symbol "m3";

gml:quantityType "volume"; gml:derivationUnit

[ gml:unit gml:m; gml:exponent "3"].

gml:l rdf:type gml:ConventionalUnit; skos:prefLabel "litre";

skos:inScheme gml:ConventionalUnits; gml:symbol "l";

gml:quantityType "volume"; gml:conversionToPreferredUnit

[ gml:unit gml:m3; gml:factor "0.001"].

Remove Clause 16.2

(GML 3.3) Deprecate GML Dictionary and Definition.

Consequences if

not approved: GML vocabularies and definitions not compatible with mainstream tools.

Clauses affected:  3, 15, 16.2

Other specs  Other core specifications  Affected: Abstract specifications

Best Practices Document Supporting Doc. 

Other comments:Status

Disposition

How to create CRs using this form: Comprehensive

(7)

create CRs can be found at:

https://portal.open geospatial.org/files /?

artifact_id=10678. Below is a brief summary:

Fill out the above form. The symbols above marked 

contain pop-up help information about the field that they are closest to.

Obtain the latest version for the release of the specification to which the change is proposed. Use the MS Word "revision marks" feature (also known as "track changes") when making the changes. All Open GIS specifications can be downloaded from the OGC server under

http://www.opengeospa tial.org/specs/

If a Word version of the document is not available, please contact the TCC or his designee.

Referensi

Dokumen terkait

perlakuan pada ayam, dan peralatan laboratorium yang digunakan untuk analisis.. kadar lemak daging dan

Hasil penelitian menunjukkan bahwa rataan masing – masing perlakuan dengan penambahan jintan hitam dan vitamin C dalam ransum pada ayam broiler terhadap bobot

Knowledge of certifications available in technical professions Knows how technical information and skills connect to careers and workplace practices Inspires students'

Although problem decomposition and recomposition are crucial strategies in engineering design, the results of this study showed that there was no difference between freshman dyads

Peternakan dengan populasi tinggi memungkinkan dalam perkawinan terutama terhadap sapi dara dilakukan secara bersamaan untuk dapat lebih efisien.. Sinkronisasi dilakukan

Secara parsial luas lahan dan jumlah biaya tenaga kerja berpengaruh nyata terhadap jumlahproduksi sedangkan jumlah biaya pupuk berpengaruh tidak nyata terhadap jumlah biaya pupuk

Tujuan dari penelitian ini adalah untuk mengevaluasi pengaruh pektin dari kulit jeruk terhadap sifat-sifat fisik sherbet yang meliputi overrun, resistensi pelelehan,

SPSS Mann-Whitney U test was conducted with significant level, p=0.05 to evaluate the difference in development level for communication skill (CS); critical thinking and