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

From TDWG Terms Wiki
Jump to: navigation, search
Line 45: Line 45:
 
*:(Note: vann:termGroup relates to the skos concept collection (label in picklist is "skos: collection"); skos has not property from concept to collection (only the inverse))
 
*:(Note: vann:termGroup relates to the skos concept collection (label in picklist is "skos: collection"); skos has not property from concept to collection (only the inverse))
 
*:(Note: we chose to present a pseudo-property "skos: collection" to the user)
 
*:(Note: we chose to present a pseudo-property "skos: collection" to the user)
* rdfs: subclass of   -- autocomplete on namespace: Category // THIS MAY NEED DISCUSSION, SHOULD RATHER SELECT FROM ARTICLE NAMESPACE
+
 
* rdfs: subproperty of -- autocomplete on namespace: Property // THIS MAY NEED DISCUSSION, SHOULD RATHER SELECT FROM ARTICLE NAMESPACE
+
Note: rdfs: subclass of and rdfs: subproperty of are no longer set to specific autocompletes, to avoid workflow complications (e.g. a skos concept may not yet have been defined as property or class)
  
  

Revision as of 08:29, 23 October 2012

This is a documentation subpage for Template:Concept 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.

Template “Concept relation” sets relations which are further analysed/displayed in Template: Concept. Results appear in a floating fact box of a concept page (=a page having template: Concept on it).

Usage

On Concept pages (using Template/Form:Concept) the following The template call can be repeated any number of times:

 {{Concept relation 
 | relation = …
 | internal page = …
 }}
or relating
to an URI
 {{Concept relation 
 | relation = …
 | uri = …
 }}
 {{Concept relation 
 | relation = …
 | uri = {{Concept to imported URI|Article namespace Wiki page of imported concept}}
 }}

Use Template: Concept to imported URI if you reuse an imported page and want to relate to the imported URI.

Parameter “relation” can be any of the strings displayed in column Display text:

GroupDisplay textProperty page
1skos: collectionvann:termGroup
10dcterms: has partdcterms:hasPart
10dcterms: is part ofdcterms:isPartOf
10rdfs: see alsordfs:seeAlso
10rdfs: subclass ofrdfs:subClassOf
10rdfs: subproperty ofrdfs:subPropertyOf
10skos: has broader matchskos:broadMatch
10skos: has close matchskos:closeMatch
10skos: has exact matchskos:exactMatch
10skos: has narrower matchskos:narrowMatch
10skos: has related matchskos:relatedMatch
10skos: is in mapping relation withskos:mappingRelation
20owl: disjoint withowl:disjointWith
20owl: equivalent classowl:equivalentClass
20owl: equivalent propertyowl:equivalentProperty
20owl: inverse ofowl:inverseOf
30biorel: adjacent tobiorel:adjacent to
30biorel: aligned withbiorel:aligned with
30biorel: connected tobiorel:connected to
30biorel: derived by descent frombiorel:derived by descent from
30biorel: derives frombiorel:derives from
30biorel: develops frombiorel:develops from
30biorel: develops from part ofbiorel:develops from part of
30biorel: develops inbiorel:develops in
30biorel: develops intobiorel:develops into
30biorel: has habitatbiorel:has habitat
30biorel: has partbiorel:has part
30biorel: has participantbiorel:has participant
30biorel: has site ofbiorel:has site of
30biorel: is bearer ofbiorel:is bearer of
30biorel: is preceded bybiorel:is preceded by
30biorel: occurs inbiorel:occurs in
30biorel: overlapsbiorel:overlaps
30biorel: part ofbiorel:part of
30biorel: participates inbiorel:participates in
30biorel: precedesbiorel:precedes
30biorel: produced bybiorel:produced by
30biorel: producesbiorel:produces
30biorel: spatially disjoint frombiorel:spatially disjoint from
30biorel: surroundsbiorel:surrounds
30biorel: variant ofbiorel:variant of


Some relations have special auto-complete functions:

Note: rdfs: subclass of and rdfs: subproperty of are no longer set to specific autocompletes, to avoid workflow complications (e.g. a skos concept may not yet have been defined as property or class)


Technical documentation

Concept relation
 ├ Template:Concept relation/return listelement from query return a list element to format an #ask-query with “format = template“ in an #ask-query 
 ├ Template:Concept relation/relation to property (map relation-string from template input to correct property page, add new relations here)
 └ Template:Concept relation/doc

For displaying data in a fact box of template: Concept other templates are used:

Those templates #ask for property values set on property pages that (re)define relations. These are display- and sorting properties:

Auto-generated list for Form Concept

Auto-generated list of relation values for Form:Concept (field: relation):

skos: collection, dcterms: has part, dcterms: is part of, rdfs: see also, rdfs: subclass of, rdfs: subproperty of, skos: has broader match, skos: has close match, skos: has exact match, skos: has narrower match, skos: has related match, skos: is in mapping relation with, owl: disjoint with, owl: equivalent class, owl: equivalent property, owl: inverse of, biorel: adjacent to, biorel: aligned with, biorel: connected to, biorel: derived by descent from, biorel: derives from, biorel: develops from, biorel: develops from part of, biorel: develops in, biorel: develops into, biorel: has habitat, biorel: has part, biorel: has participant, biorel: has site of, biorel: is bearer of, biorel: is preceded by, biorel: occurs in, biorel: overlaps, biorel: part of, biorel: participates in, biorel: precedes, biorel: produced by, biorel: produces, biorel: spatially disjoint from, biorel: surrounds, biorel: variant of

Dependencies

See also