Concept
type: Class

alternative label
comment: The range of skos:altLabel is the class of RDF plain literals.
comment: skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.
sub property of: label
definition: An alternative lexical label for a resource.

has broader
comment: Broader concepts are typically rendered as parents in a concept hierarchy (tree).
sub property of: Transitive
definition: Relates a concept to a concept that is more general in meaning.

definition
sub property of: note
definition: A statement or formal explanation of the meaning of a concept.

editorial note
sub property of: note
definition: A note for an editor, translator or maintainer of the vocabulary.

is in scheme
definition: Relates a resource (for example a concept) to a concept scheme in which it is included.

preferred label
comment: skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.
comment: The range of skos:prefLabel is the class of RDF plain literals.
comment: A resource has no more than one value of skos:prefLabel per language tag.
sub property of: label
definition: The preferred lexical label for a resource, in a given language.

has related
comment: skos:related is disjoint with skos:broaderTransitive
sub property of: semanticRelation
definition: Relates a concept to a concept with which there is an associative semantic relationship.

SoServe-Thesau
type: Dataset
type: Concept
type: ConceptGroup
type: ConceptScheme

Methoden
type: ConceptGroup
member: resource model

Methoden Service Engineering
type: Concept
narrower: resource model

capability level
type: Concept
preferred label: Potenzialdimension @de
related: resource model

resources
type: Concept
preferred label: Ressourcen @de
related: resource model

resource model
type: Concept
alternative label: Ressourcenkonzept @de
broader: Methoden Service Engineering
definition: "Im Ressourcenmodell werden die für die Leistungserbringung notwendigen personellen und sonstigen Mittel sowie deren Eigenschaften erfasst, so dass [sic.] die intendierte Zustandsveränderung adäquat beschrieben werden kann." Die beteiligten Ressourcen können sowohl technischer, sachlicher oder humaner Natur sein und können "innerhalb des Leistungssystems verschiedene Zugriffs- und Nutzungsrechte haben". @de
editorial note: Meyer, Kyrill; Zinke, Christian (2018): Service Engineering – eine Standortbestimmung. In: Kyrill Meyer, Stephan Klingner und Christian Zinke (Hg.): Service Engineering, Bd. 30. Wiesbaden: Springer Fachmedien Wiesbaden, S. 3–17 (8) @de
is in scheme: SoServe-Thesau
preferred label: Ressourcenmodell @de
related: capability level
related: resources