Archives: Templates

Templates and model types in the QualiWare platform.

OntologyDiagram:OWL

An ontology diagram shows classes, object properties and datatype properties, as well as rules (especially set rules). 

Symbols (Classes, Set Rules, Datatypes and Instances) are dragged from the palette into the drawing canvas. 

Connections (subClassOf, SetRelation, ObjectProperty, DatatypeProperty and Instantiation) connect the appropriate symbols.

The ontology diagram symbols palette provides the set of symbols and links which are used to graphically represent the ontology:

  • Class (symbol for a Class which may be automatically colored based on the Class characteristics)
  • Union, Intersection, Disjioint and Complement (symbols for set Rules)
  • owlDataType (symbol for defining the data type of a data Property defining a Class)
  • Instance (symbol for instances of a given Class)
  • subClassOf (connector linking a Class as subClass to its superClass Class)
  • SetRelation (connector linking a Class or a set Rule to a set Rule; composite rules can be formalized)
  • ObjectProperty (connector linking a Class or Set Rule to a Class or a set Rule defining the entertained relationship)
  • DatatypeProperty (connector linking a Class oa setRule to a Datatype)

owlInstanciation (connector linking a Class or a setRule to corresponding Instances)

As in any QualiWare diagram, connecting 2 symbols is achieved by selecting the connector, then the source symbol, then the target symbol, then giving it a name.

The coloring of the Class symbol is achieved based on the Class characteristics.

A class can be:

  • A Thing
  • A standard owl Class defined in the current ontology edited in the currentontology diagram
  • External to the concerned ontology (the one edited in the diagram)
  • A rdfs Class
  • A Resource
  • A deprecated Class

Since it is contextual to the edited diagram, defining a Class as being external to an ontology is achieved by selecting the classes which are external to the ontology depicted in the diagram copying them and pasting them in the “External Classes” field of the definition template of the diagram.

 

The same can be achieved for ObjectProperties which are external to the edited ontology.

 

A same Class (unique in the repository) can be a standard owl Class in the ontology defining it (and appearing pale blue in the diagram depicting this ontology) and dark blue (since external) in possibly many other diagrams depicting other ontologies referencing to this Class.

Same for ObjectProperties.

 

When closing a diagram, the corresponding Ontology instance (the one which refers to the diagram) is updated. Its contained Classes and Object Properties fields are updated.

The instances of Class, ObjectProperty, DatatypeProperty and set Rules instances edited in the diagram are also updated (see corresponding paragraphs)

Ontology:OWL

The ontology Annotations

Annotations are used to associate information with ontologies. These provide meaningful definitions to the ontology.

An ontology is defined and described with:

  • A Name (here “foaf”)
  • A Title
  • An IRI (Internationalized Resource Indicator) which points to its documentation on the web
  • A Short description
  • A Version number and its pointer to the file describing it (Version IRI)
  • Some History dates (first issued, and last modified)
  • Creators (names of its creator(s))
  • A License reference and its Publisher
  • Its Source (the target to its definition)
  • A Prefix

A Namespace definition

The “Prefix” is used as the reference to the described ontology, when its defined classes are referenced from another ontology. In the referring ontology the referenced classes appear as prefixed with this term. Supposing an ontology referencing “Person” (as defined in FOAF), this class will be prefixed as “foaf:Person” explicating that in the context of this ontology, “Person” must be understood as defined in FOAF.

 

An ontology refers

An ontology refers:

  • Possibly an external document (See also)
  • Referred ontologies (used for defining the prefixes used to refer to these ontologies)

 

Diagrams (one or more diagrams presenting graphically the ontology)

Diagrams are based on the OntologyDiagram:owl template (see below in the “OntologyDiagram” paragraph).

 

An ontology is described with content

An ontology contains (is described with) :

  • Classes (these are the Class:owl instances which appear in the Ontology Diagram)

Object Properties (these are the ObjectProperty:owl instances which appear in the Ontology Diagram)

These two fields are automatically filled at close of the Ontology Diagram which is referred to by the Ontology.

 

The ontology detailed Description

An ontology has a detailed description

 

Note

These Annotation fields described above are edited by the ontology engineer when creating his/her ontology.

The ontology example (FOAF) we use to show these Annotations populated with content is an “up level” ontology and is published on the web.

Loading automatically these published ontologies makes sense. We used a semi-automatic way to load it.

 

Currently there is no fully automated load of ontology source document. We are working on it and will deliver this automatic load soon.

ObjectProperty:OWL

The ObjectProperty:owl template contains definitions, descriptions, and ontology characteristics according to the ontology diagrams which contain it. This content is synchronized at close of the diagram.

In the future, when there will be a rdf/owl (and possibly turtle and json) loader from a text source defining ontologies, these properties will be filled automatically, and the ontology diagram will also be generated.

An ObjectProperty associates two classes. It is described with:

  • A Short description
  • A Domain (the source class of the relationship)
  • A Range (the target class of the relationship)
  • The ObjectProperty it is defined as Inverse of

It can be Qualified as :

  • Base or functional or inverse functional or transitive or symmetric

These characteristics determine the appearance of the ObjectProperty in the diagram

It can bear restrictions :

  • Some or Only or Min or Exactly or Max
  • The four last restrictions combine with Cardinality

MilkyWayEnterpriseMap:EDGY

Purpose: The purpose of the MilkyWayEnterpriseMap diagram is to map the different elements into one diagram, creating a view of the enterprise

Core concerns: The MilkyWay enables you to collect objects of the different facets in the EDGY language in one diagram.

 

From the center and outwards, the milkyway shows:

  • the identity elements (Purpose and Story)
  • the Organization
  • the architecture elements (Capability and Process)
  • the Product
  • the experience elements (Task and Journey)
  • the Brand

DatatypeProperty:OWL

The DatatypeProperty:owl template contains definitions, descriptions, and ontology characteristics according to the ontology diagrams which contain it. This content is synchronized at close of the diagram.

In the future, when there will be a rdf/owl (and possibly turtle and json) loader from a text source defining ontologies, these properties will be filled automatically, and the ontology diagram will also be generated.

A DatatypeProperty associates a class with a datatype, defining a property of the class . It is described with :

  • A Short description
  • A Class which it is the DataType for (the source or domain class of the relationship)
  • A Datatype which the class Has Datatype (the target or range Datatype of the relationship)

 

 

Class:OWL

The Class:owl template contains definitions, descriptions, and ontology characteristics according to the ontology diagrams which contain it. This content is synchronized at close of the diagram.

In the future, when there will be a rdf/owl (and possibly turtle and json) loader from text source defining ontologies, these properties will be filled automatically, and the ontology diagram will also be generated.

 

A class is described with:

  • Other classes it could be Equivalent to
  • A Short description

It can be:

  • A Thing
  • An owl class
  • a rdfs Class
  • a Resource
  • a deprecated Class

These five options determine the appearance of the class in the diagram.

 

The class hierarchy

These fields are synchronized with the diagrams which the class appears in.

 

A class is part of a class hierarchy as :

  • A subclass of Parent classes
  • A superclass of Child classes

The class participates to set rules

These fields are synchronized with the diagrams which the class appears in, when it participates to set rules.

When participating to a disjoint rule, the classes which the class is Disjoint with are listed here.

 

When participating to an intersection rule, the classes which the class is in Intersection with are listed here.

 

When participating to a complement rule, the classes which the class is Complement for are listed here.

 

When participating to a union rule, the classes which the class is in Union with are listed here.

 

The ObjectProperties of the class

This field is synchronized with the diagrams which the class appears in.

A class has Properties.

 

The DataTypeProperties of the class

This field is synchronized with the diagrams which the class appears in.

A class has Datatype Properties.

These are the DataTypeProperties which the class is Domain for (source of the relationship).

 

The Instances of the class

This field is synchronized with the diagrams which the class appears in.

A class has Instances.

These are the declared instances of the class.