Difference between revisions of "Template:Concept scheme relation/doc"

From TDWG Terms Wiki
Jump to: navigation, search
(Created page with "{{Documentation/subpage}} On Concept pages (using Form:Concept) the following can be repeated any number of times: <nowiki>{{Concept scheme relation | scheme = ← Page nam...")
 
m (→‎TODO: update of TODO, link to Template talk:Concept scheme relation)
 
(9 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{Documentation/subpage}}
 
{{Documentation/subpage}}
 +
=== Background ===
 +
Originally, the [[skos:inScheme|inScheme]] relation was part of the general relations (see [[template: Concept relation]]). It was separated, because we desire to express constraints (range, domain, cardinality) about concepts. The complication here is that consensus exists to define "base-schemes" with as few constraints as possible, which are then re-used in more constraining schemes. This means that constraints for a concept are not universal properties of the concept itself, but rather of their re-use.
  
−
On Concept pages (using Form:Concept) the following can be repeated any number of times:
+
=== Usage ===
  
−
<nowiki>{{Concept scheme relation  
+
On [[:Category: Concept|Concept pages]] (using [[Form:Concept]]) the following can be repeated any number of times ('''bold'''=mandatory parameter):
−
| scheme = ← Page name of a concept scheme
+
<div class="no-pre-border no-pre-margin no-pre-padding" style="margin-left:1.5em;">
−
| property domain = if present concept is a property, a domain constraint defined within that scheme. The constraints of the original scheme are most relevant, but other schemes may define other constraints. This maps to rdfs:domain if the skos concept is applied as an rdfs/owl ontology.
+
<nowiki>{{</nowiki>Concept scheme relation  
−
| property range  = if present concept is a property, a range constraint defined within that scheme. The constraints of the original scheme are most relevant, but other schemes may define other constraints. This maps to rdfs:domain if the skos concept is applied as an rdfs/owl ontology.
+
| <b>scheme</b> = &lt;!-- page name of a concept scheme -->
−
| property cardinality = if present concept is a property, a cardinality constraint defined within that scheme. Values are 0..1 (optional single occurrence), 1..1 (mandatory single occurrence), 0..n (optional multiple occurrence), 1..n (mandatory multiple occurrence). The constraints of the original scheme are most relevant, but other schemes may define other constraints. For example "1..1" maps to owl:minCardinality "1" owl:maxCardinality "1" if the skos concept is applied as an rdfs/owl ontology.
+
| property domain =&lt;!-- a domain constraint defined within that scheme -->
−
}}
+
| property range  =&lt;!-- a range constraint defined within that scheme -->
−
</nowiki>
+
| property cardinality =&lt;!-- one value of: "0..1", "0..n", "1..1", "1..n" -->
 +
<nowiki>}}</nowiki>
 +
</div>
 +
'''Parameter in detail:'''
  
−
<!--
+
<code>scheme=</code> age name of a concept scheme
−
=== Usage ===
+
 
 +
<code>property domain =</code> if present concept is a property, a domain constraint defined within that scheme. A domain defines the class of subject resources, to which a property may be applied. The constraints of the original scheme are most relevant, but other schemes may define other constraints. This maps to [[property: rdfs:domain |rdfs:domain]] if the skos concept is applied as an rdfs/owl ontology.
 +
 
 +
<code>property range =</code> if present concept is a property, a range constraint defined within that scheme. A range declares the class or datatype of the values or objects that are assigned to a property (the right side in the triple). The constraints of the original scheme are most relevant, but other schemes may define other constraints. This maps to [[property: rdfs:range |rdfs:range]]<ref name="check">is [[property: rdfs:range |rdfs:range]] correct? --[[User:Andreas Plank|Andreas Plank]] 17:32, 25 October 2012 (CEST)</ref> if the skos concept is applied as an rdfs/owl ontology.
 +
 
 +
<code>property cardinality =</code> if present concept is a property, a cardinality constraint defined within that scheme. Values are:
 +
* 0..1 (optional single occurrence)
 +
* 0..n (optional multiple occurrence)
 +
* 1..1 (mandatory single occurrence)
 +
* 1..n (mandatory multiple occurrence).
 +
The constraints of the original scheme are most relevant, but other schemes may define other constraints. For example "1..1" maps to [[property: owl:minCardinality |owl:minCardinality]] "1" [[property: owl:maxCardinality |owl:maxCardinality]] "1" if the skos concept is applied as an rdfs/owl ontology.
 +
----
 +
<references />
 +
 
 +
 
 +
=== TODO ===
 +
* decide for a self-explanatory pagename property for #set_internal’s first argument (see [[Template talk:Concept scheme relation]])
 +
* revise layout + semantic properties
  
 
=== See also ===
 
=== See also ===
−
-->
+
* [[Template talk:Concept scheme relation/doc|Talk page (doc)]]
−
<includeonly></includeonly>
+
* [[template: Concept relation]]
 +
* [[form: Concept]]
 +
<includeonly>
 +
<!-- CATEGORIES AND INTERWIKIS HERE, THANKS -->
 +
[[Category: Helper tool for ontologies]]
 +
</includeonly>

Latest revision as of 10:33, 26 October 2012

This is a documentation subpage for Template:Concept scheme relation (see that page for the template itself).
It contains usage information, categories and other content that is not part of the original template page.

Background

Originally, the inScheme relation was part of the general relations (see template: Concept relation). It was separated, because we desire to express constraints (range, domain, cardinality) about concepts. The complication here is that consensus exists to define "base-schemes" with as few constraints as possible, which are then re-used in more constraining schemes. This means that constraints for a concept are not universal properties of the concept itself, but rather of their re-use.

Usage

On Concept pages (using Form:Concept) the following can be repeated any number of times (bold=mandatory parameter): 

{{Concept scheme relation 
| scheme = <!-- page name of a concept scheme -->
| property domain =<!-- a domain constraint defined within that scheme -->
| property range  =<!-- a range constraint defined within that scheme -->
| property cardinality =<!-- one value of: "0..1", "0..n", "1..1", "1..n" -->
}}

Parameter in detail:

scheme= age name of a concept scheme

property domain = if present concept is a property, a domain constraint defined within that scheme. A domain defines the class of subject resources, to which a property may be applied. The constraints of the original scheme are most relevant, but other schemes may define other constraints. This maps to rdfs:domain if the skos concept is applied as an rdfs/owl ontology.

property range = if present concept is a property, a range constraint defined within that scheme. A range declares the class or datatype of the values or objects that are assigned to a property (the right side in the triple). The constraints of the original scheme are most relevant, but other schemes may define other constraints. This maps to rdfs:range[1] if the skos concept is applied as an rdfs/owl ontology.

property cardinality = if present concept is a property, a cardinality constraint defined within that scheme. Values are:

  • 0..1 (optional single occurrence)
  • 0..n (optional multiple occurrence)
  • 1..1 (mandatory single occurrence)
  • 1..n (mandatory multiple occurrence).

The constraints of the original scheme are most relevant, but other schemes may define other constraints. For example "1..1" maps to owl:minCardinality "1" owl:maxCardinality "1" if the skos concept is applied as an rdfs/owl ontology.

  1. ↑ is rdfs:range correct? --Andreas Plank 17:32, 25 October 2012 (CEST)


TODO

See also

Retrieved from "https://terms.tdwg.org/w/index.php?title=Template:Concept_scheme_relation/doc&oldid=7405"