Objecttype libraries: Generic

Uit COINS2
Versie door Renzo van Rijswijk (Overleg | bijdragen) op 11 jul 2016 om 07:32 (Objecttype libraries scenarios)

(wijz) ← Oudere versie | Huidige versie (wijz) | Nieuwere versie → (wijz)
Ga naar: navigatie, zoeken

This page describes the Objecttype libraries

Objecttype libraries scenarios

There are a number of scenarios that you can run into when you want to define an objecttype library:

  • develop the library within Coins using the CataloquePart class
  • use an external library created by the client (e.g. OTL-RWS, OTL Spoor, CB-NL)
  • use your own internal library created in another system
  • a combination of these 3 scenario's.

Objecttype library within Coins

Within Coins you can develop your own library. This can be done by using an OWL-editor. First create a new OWL file. Import the Coins files into this file, so you can use the classes and properties. Now, you are able to create subclasses and subproperties. So for instance, create a subclass Bridge under cbim-2.0:Object. It is mandatory that you define this Bridge object as a cbim-2.0:CataloguePart as well. In this way, this Bridge is a rdfs:subClassof both an Object and a CataloguePart. This sample is further described on this Create objecttype library within Coins.

External and Internal library

Coins enables to create a reference to an external or internal library. This refering is further clarified on External and Internal library:Detail section.

Combination of libraries

You can use Coins as an intermediate between the internal and external library.

See also

Create objecttype library within Coins