Copyright ©

Abstract

The abstract should provide a concise overview of the semantic model, summarizing its scope, purpose, and key elements. The final content should explain what the model represents, its intended use, and the core concepts it covers. For instance, it should describe the main classes, relationships, and types of entities addressed, highlighting reusability, extensibility, and integration within a broader data ecosystem.

Introduction

The Introduction should provide context for the vocabulary, including the motivation for its creation, its intended audience, and the problems it aims to address. The section should give readers a high-level understanding of the model, including its scope, design principles, and how it fits within related specifications or standards.

Status

The Status section should explain the current standing of the specification, including its level of formal recognition, publication date, and any relevant approval or recommendation information. It should also summarize the development process, key decisions, and provide references to changelogs or historical versions. It is recommended to indicate the maturity levels of the specification.

This application profile has the status Draft and has been published on 2026-06-29.

History of changes to the project is available in Changelog.

License

The License section should outline the legal terms under which the vocabulary and associated materials may be used, shared, and modified. It should clearly indicate copyright ownership, applicable licenses, exceptions, and any obligations or restrictions for users and contributors.

This specification of prettyModel core is published under CC BY 4.0.

The Conformance section should define which parts of the specification are normative versus non-normative, and how compliance should be interpreted. It should explain the meaning of key terms such as MUST, MAY, and SHOULD, and it should provide guidance on how these rules should be applied when using or extending the vocabulary.

Terminology

The Terminology section defining the key concepts and terms used in the vocabulary.

Used Prefixes

No custom prefixes are defined in this project.

Overview

This document describes the usage of the following main entities for a correct usage of the vocabulary:
| Bicycle | Boat | Boring wheel | Car | Class for qual assoc | Contractor | Cycle | Fancy wheel | Insurance | Monocycle | Parts class | Rental company | Some other class | Vehicle | Wheel | Yet another C |

And supported by these datatypes:
| Date | Short | Long | Int |

Main Entities

The main entities are those that form the core of the vocabulary. Properties of entities are listed in a tabular form.

Bicycle

Definition
Subclass of
Cycle
Properties
This specification does not impose any additional requirements to properties for this entity.

Boat

Definition
Subclass of
Vehicle
Properties
For this entity the following properties are defined: has ins sub.
Property Range Card Definition Usage Reuse Feedback
has ins sub Insurance 2

Boring wheel

Definition
Subclass of
Wheel
Properties
This specification does not impose any additional requirements to properties for this entity.

Car

Definition
Subclass of
Vehicle
Properties
This specification does not impose any additional requirements to properties for this entity.

Class for qual assoc

Definition
Properties
For this entity the following properties are defined: target.
Property Range Card Definition Usage Reuse Feedback
target Some other class 0..*

Contractor

Definition
Properties
This specification does not impose any additional requirements to properties for this entity.

Cycle

Definition
Subclass of
Vehicle
Properties
For this entity the following properties are defined: colour.
Property Range Card Definition Usage Reuse Feedback
colour Short 1..3

Fancy wheel

Definition
Subclass of
Wheel
Properties
This specification does not impose any additional requirements to properties for this entity.

Insurance

Definition
Properties
For this entity the following properties are defined: for.
Property Range Card Definition Usage Reuse Feedback
for Vehicle 1..*

Monocycle

Definition
Subclass of
Cycle
Properties
This specification does not impose any additional requirements to properties for this entity.

Parts class

Definition
Properties
This specification does not impose any additional requirements to properties for this entity.

Rental company

Definition
Properties
For this entity the following properties are defined: lends, name.
Property Range Card Definition Usage Reuse Feedback
lends Vehicle 1..*
name Long 1..1

Some other class

Definition
Properties
For this entity the following properties are defined: has ins.
Property Range Card Definition Usage Reuse Feedback
has ins Insurance 0..*

Vehicle

Definition
Properties
For this entity the following properties are defined: engraved ID, name, nick name.
Property Range Card Definition Usage Reuse Feedback
engraved ID Int 1..1
name Short 1..1
nick name Long 1..1

Wheel

Definition
Properties
This specification does not impose any additional requirements to properties for this entity.

Yet another C

Definition
Properties
This specification does not impose any additional requirements to properties for this entity.

Supportive Entities

This vocabulary does not define any supportive entities.

Datatypes

The following datatypes are used within this specification.
Class Definition Feedback
Int

Usage Guidelines - change

Basic Usage

To use this vocabulary, follow these guidelines:

Example 1

Governance

Custom section - TEMPLATE_CUSTOM_2024

A custom section introduced in main template

Custom section from custom.j2

A custom section introduced in main template via include

Quick Reference of Classes and Properties

This section provides a condensed tabular overview of the mentioned classes and properties in this specification.
Class Class IRI Property type Property Property IRI
Boat
http://example.com/ex#Boat
 Mandatory has ins sub
http://example.com/ex#hasInsSub
Class for qual assoc
http://example.com/ex#ClassForQualAssoc
 Optional target
http://example.com/ex#target
Cycle
http://example.com/ex#Cycle
 Mandatory colour
http://example.com/ex#colour
Insurance
http://example.com/ex#Insurance
 Mandatory for
http://example.com/ex#for
Rental company
http://example.com/ex#RentalCompany
 Mandatory lends
http://example.com/ex#lends
Rental company
http://example.com/ex#RentalCompany
 Mandatory name
http://example.com/ex#name
Some other class
http://example.com/ex#SomeOtherClass
 Optional has ins
http://example.com/ex#hasIns
Vehicle
http://example.com/ex#Vehicle
 Mandatory engraved ID
http://example.com/ex#engravedID
Vehicle
http://example.com/ex#Vehicle
 Mandatory name
http://example.com/ex#name
Vehicle
http://example.com/ex#Vehicle
 Mandatory nick name
http://example.com/ex#nickName

Project resources

The following list provides links to semantic data specifications and other resources related to this vocabulary.