Archives: Templates

Templates and model types in the QualiWare platform.

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.

JourneyMap:EDGY

Purpose: The purpose the Journey Board is to promote an empathetic view of the people we are designing for/with and to share insight and data about people’s lives in a narrative scenario form that co-creators can relate to.

Core concerns: A brand is a symbolic representation of our enterprise and its products. It is designed to communicate our identity (especially how we are different from others) and to invoke a set of expectations in people about our enterprise and our products, particularly in relation to people’s own needs and desires.

The Activity Board is a part of the EDGY language created by the Intersection Group.

ContentMap:EDGY

Purpose: The purpose the Content Board is to capture key messages, media and formats used to convey identity, story and purpose to audiences, while setting a consistent ton of voice across formats, media and distribution channels to best engage people.

Core concerns: Content refers to data or information that is communicated between and towards people. It requires a medium to convey the underlying message to its audiences, such as audiovisual media like text, images or video, sound recordings or accessible alternatives. In an enterprise, various forms of content are being produced and maintained, exchanged and promoted.

The Content Board is a part of the EDGY language created by the Intersection Group.

ChannelMap:EDGY

Purpose: The purpose the Channel Board is to get an overview of where and how people interact with the enterprise or each other and make them connect.

Core concerns: Channels are the means of communication between people and the enterprise. They are where moments of interaction between people and the enterprise take place.

The Channel Board is a part of the EDGY language created by the Intersection Group.