Velkommen til utstillingsrommet med demoinformasjonbsmodeller, som demonstrerer bruken av ModellDCAT-AP-NO!
ModellDCAT-AP-NO ⧉ er den norske applikasjonsprofilen av DCAT-AP-NO ⧉, for beskrivelse av informasjonsmodeller og kataloger av informasjonsmodeller.
Resten av teksten er kun på engelsk.
Purpose
This showroom is meant to
-
demonstrate how to describe an information model in accordance with ModellDCAT-AP-NO;
-
demonstrate how to describe relations between information models, in accordance with ModellDCAT-AP-NO;
-
demonstrate cross-references between information models and some other resources demonstrated in some of the other showrooms;
-
provide reusable, machine-readable RDF-based model descriptions, for testing and demonstration purposes.
Disclaimer: The machine-readable demo information models are meant for demo purposes only. They do not represent any real world fenomena at all. On the other hand, they are supposed to syntactically conform to ModellDCAT-AP-NO.
Demo resources in this showroom
In this showroom we have a a catalog with several demo information models:
-
The demo information models are automatically harvested to and thus findable via the demo portal ⧉. Note: the demo portal has some bugs such that not all properties are currently shown in the portal.
-
There are four demo information models:
-
"Demo model 1" contains "Demo model 2" and "Demo model 3", and "Demo model 4" illustrates the usage of all syntactically possible relations that an information model may have with other information models, in accordance with ModellDCAT-AP-NO.
-
All four demo models have graphical representations, which are referred to from the description.
-
Except for "Demo model 1", the other three demo models are described only at the model level, i.e., without descriptions of the model elements in the models, in compliance with ModellDCAT-AP-NO.
-
Simply put: you don’t need to describe all the details in your information model, before you can tell the world that you have an information model.
-
-
-
"Demo model 1" also illustrates in particular the following:
-
"Demo model 1" has four model elements ⧉, which are object types ⧉ (classes in UML): "Demo Class 1", "Demo Class 2", "Demo Class 3" and "Demo Class 4".
-
"Demo Class 1" has an association (in UML) to "Demo Class 2", which is a role ⧉ in ModellDCAT-AP-NO.
-
"Demo Class 3" and "Demo Class 4" are subclasses of "Demo Class 1", described as specializations ⧉ in ModellDCAT-AP-NO.
-
"Demo Class 1" has an attribute ⧉ named "demo attribute 11".
-
This attribute uses a code list as its value range.
-
The code list, "Demo Code List 1", is an external code list with reference to our "Demo classification 1" demonstrated in our showroom with demo classifications.
-
-
Click for mapping to ModellDCAT-AP-NO.
The UML-elements in "Demo model 1" shown in Figur 1 are mapped to ModellDCAT-AP-NO as shown in Tabell 1.
Element (number) |
UML |
ModellDCAT-AP-NO |
1 |
Information model (modelldcatno:InformationModel) |
|
2 |
Class |
Object type (modelldcatno:ObjectType) |
3 |
Generalization |
Specialization (modelldcatno:Specialization) |
4 |
Association |
Role (modelldcatno:Role) |
5 |
Attribute |
Attribute (modelldcatno:Attribute) |
6 |
Enumeration |
Code list (modelldcatno:CodeList) |
Some cross-references with other demo resources
Note: Not all possible cross-references are demonstrated in this showroom. The lists are thus not exhaustive.
Information models and classifications, for example:
-
When describing an information model, and where coded values are used, the coded values should preferably be chosen from controlled vocabularies (i.e., classifications).
-
Examples of properties with coded values are status (adms:status) ⧉ and type (dct:type) ⧉, which are demonstrated by e.g. "Demo model 1".
-
Classifications should therefore be made available, also machine-readably.
-
-
An information model may use classifications (controlled vocabularies, code lists etc.) as "datatype/range specification" for its "attributes".
-
This is demonstrated by "Demo model 1", where "demo attribute 11" refers to (by using the property has value from (modelldcatno:hasValueFrom) ⧉) a code list. The code list it refers to is our "Demo controlled vocabulary 1" which is demonstrated in our showroom with demo classifications.
-
Classifications should therefore be made available, also machine-readably.
-
Information models and concepts, for example:
-
An information model may refer to concepts that the information model represents or concepts that are relevant for understanding the information model.
-
This is demonstrated by "Demo model 1", where its "Demo Class 1" refers to (by using the property subject (skos:Concept) ⧉) our "demo concept 1" which is demonstrated in our showroom with demo concepts.
-
In general, an information model ⧉ itself, its model elements ⧉ (object types, code lists etc.) and properties ⧉ (attributes, associations etc.) may all refer to concepts, using the property
subject (skos:Concept)in accordance with ModellDCAT-AP-NO.
-
Information models and datasets, for example:
-
A dataset (and/or its distributions, data services) may conform to one or more standards (incl. information models).
-
This is demonstrated in our showroom with demo datasets.
-
Information models should therefore be made available, also machine-readably.
-
Information models and services/events, for example:
-
An evidence needed to execute a service, is a dataset and thus may conform to one or more standards (incl. information models).
-
This is demonstrated in our showroom with demo services and events.
-
Information models should therefore be made available, also machine-readably.
-