Model Structure

Knowledge Model Management (KMM) comes with a predefined set of relationships and metadata elements. This set represent the most commonly used SKOS properties. Those properties are visible on the model structure page, and new properties can also be created and managed from that user interface.

This page covers tips and techniques to go beyond what is offered through the UI.

Visibility of existing properties

Properties are only shown in the KMM user interface in two cases:

1. When the property is a “DatatypeProperty”, its range is a valid datatype, and its domain is “skos:Concept” or sub-class of “skos:Concept”. For example:

    example:established
      rdf:type owl:DatatypeProperty ;
      rdfs:domain example:Company ;
      rdfs:label "established"@en ;
      rdfs:range xsd:date ;

2. If the domain of an existing property cannot be changed, when the property is a “DatatypeProperty”, its range is a valid datatype, and it carries the “sem:DefaultProperty” type. For example:

    skos:note
      rdf:type sem:DefaultProperty ;
      rdfs:range xsd:string ;

If the range of a property cannot be changed as well, you can add the “sem:uiRange” predicate to instruct KMM how to render values of such properties. The “sem:uiRange” value cannot reach beyond the existing “rdfs:range” it can only narrow its scope. For example the original range of “dcterms:created” property is “rdfs:Literal” but you can instruct KMM to render this “Literal” as a date by adding:

   dcterms:created
      rdf:type sem:DefaultProperty ;
      sem:uiRange xsd:date ;