Fork me on GitHub

The SEAS Architecture ontology

The SEAS Architecture Ontology models the concepts from the SRAM Architecture model.

See deliverable SEAS D1.3.

Classes

SEAS Core Entity

IRI: https://w3id.org/seas/CoreEntity

SEAS core entities are SEAS nodes that belong to the SEAS core domain.

The SEAS core domain is where all SEAS core entities, group managers, and SEAS core services can be interconnected.

Interconnections within the SEAS core domain all rely on the Internet Protocol.

SEAS core entities can be connected to other SEAS core entities in a peer-to-peer basis, and exchange information.

SEAS core entities can be connected to SEAS field entities, provided that they have sufficient access right.

Core Entity Connection

IRI: https://w3id.org/seas/CoreEntityConnection

The class of SEAS core entity connections between SEAS core entities. SEAS core entity connections describe potential information flows between the SEAS core entities it connects.

For example, the following RDF graph states that a SEAS core entity connection connects a home management system with an aggregator and the transaction server:

<connection> a seas:ElectricalConnection ;
   seas:connectsSystem <home_management_system> , <aggregator> , <transaction_server> .

Only SEAS core entities are connected through a SEAS core entity connection.

A connection between SEAS core entities is not necessarily a SEAS core entity connection.

Direct Access Connection

IRI: https://w3id.org/seas/DirectAccessConnection

The class of SEAS direct access connections between a SEAS core entity and one or more SEAS field entities it directly accesses.

Direct access connections describe potential control of the SEAS core entity to the SEAS field entities.

For example, the following RDF graph states that a SEAS direct access connection connects a distribution system operator with a solar panel:

<connection> a seas:DirectAccessConnection ;
   seas:connectsSystem <distribution_system_operator> , <solar_panel> .
Only SEAS entities are connected through a direct access connection.
A connection between SEAS entities is not necessarily a direct access connection.

Direct Management Connection

IRI: https://w3id.org/seas/DirectManagementConnection

The class of SEAS direct management connections between a SEAS group manager entity and each of the entities it directly manages (i.e., the group).

Direct management connections describe the management of the SEAS field entities by the SEAS group manager.

For example, the following RDF graph states that a home management system manages a group of field entities composed of a solar panel and a battery:

<connection> a seas:DirectManagementConnection ;
   seas:connectsSystem <home_management_system> , <solar_panel> , <battery> .

Only SEAS entities and SEAS field entities are connected through a direct management connection.

A connection between SEAS entities is not necessarily a direct management connection.

End User

IRI: https://w3id.org/seas/EndUser

The class of end user entities, that own SEAS field entities.

SEAS Entity

IRI: https://w3id.org/seas/Entity

The class SEAS entity represents the abstract class of communicating nodes.

Entity Access Point

IRI: https://w3id.org/seas/EntityAccessPoint

The class of access points of SEAS entities, at which they may access or be accessed by other entities.

For example, a solar panel may have an access point where smart grid management systems can access the latest information about its electricity production.

An entity access point describes the APIs that one may use to access the system.

An entity access point only belongs to one entity, and connects it through entity connections.

A connection point of an entity is not necessarily an entity access point.

Entity Connection

IRI: https://w3id.org/seas/EntityConnection

The class of entity connections between SEAS entities.

SEAS Field Entity

IRI: https://w3id.org/seas/FieldEntity

SEAS field entities are SEAS nodes that belong to the SEAS field domain.

The SEAS field domain is the link with the physical world.

SEAS field entities can be connected to other SEAS field entities in a client-server basis.

SEAS field entities can belong to one or several SEAS groups.

Every SEAS group is managed by exactly one group manager.

Field entities participate in the management of the group.

SEAS Gateway

IRI: https://w3id.org/seas/Gateway

SEAS Gateways are network nodes equipped for interfacing with entities in a field that use different communication protocols.

SEAS Group Manager

IRI: https://w3id.org/seas/GroupManager

SEAS group managers are both field and core entities. They manage exactly one group.

Ontology Entity

IRI: https://w3id.org/seas/OntologyEntity

The class of entities that provide the SEAS core ontology services for SEAS core entities.

A SEAS core ontology service is an API that exposes media types descriptions, notably information about:

  • how to validate a document with a specific media type;
  • how to lift a document with a specific media type to RDF;
  • how to validate a RDF Graph;
  • how to lower a RDF Graph to a document with a specific media type.

The complete specification of the SEAS core ontology services is available in SEAS Deliverable X.X.

Registration Entity

IRI: https://w3id.org/seas/RegistrationEntity

The class of entities that provide the SEAS core registration services for SEAS core entities.

A SEAS registration service is an API that enables SEAS core services to register themselves along with their capabilities for others to find them.

The complete specification of the SEAS core registration services is available in SEAS Deliverable X.X.

Security Entity

IRI: https://w3id.org/seas/SecurityEntity

The class of entities that provide the SEAS core security services for SEAS core entities.

A SEAS core security service is an API that enable:

  • SEAS core entities to communicate their access control preferences;
  • SEAS core entities to control the access rights of other SEAS core entities for some type information.

The complete specification of the SEAS core security services is available in SEAS Deliverable X.X.

Transaction Entity

IRI: https://w3id.org/seas/TransactionEntity

The class of entities that provide the SEAS core transaction services for SEAS core entities.

A SEAS core transaction service is an API that connects SEAS core entities to banks and payment systems, and acts as a trusted notary to enable compensation for participation in SEAS field entities management.

The complete specification of the SEAS core transaction services is available in SEAS Deliverable X.X.

Object Properties

directly accesses by

IRI: https://w3id.org/seas/directlyAccessedBy

Links a SEAS field entity to a core entity that directly accesses it.

This property can be qualified using class seas:DirectAccessConnection, which connects the core entity and the field entity.

For example, for a flexibility operator to directly access a solar panel, then it must have a direct access connection to it:

<flexibility_operator> a seas:CoreEntity .
<solar_panel> a seas:FieldEntity .
<solar_panel> seas:accessesDirectly <flexibility_operator> . 

If there is a direct access connection between a core entity and a field entity, then one may infer the core entity can directly access the field entity.

directly accesses

IRI: https://w3id.org/seas/directlyAccesses

Links a SEAS core entity to a SEAS field entity it has direct access to.

This property can be qualified using class seas:DirectAccessConnection, which connects the core entity and the field entity.

For example, for a flexibility operator to directly access a solar panel, then it must have a direct access connection to it:

<flexibility_operator> a seas:CoreEntity .
<solar_panel> a seas:FieldEntity .
<flexibility_operator> seas:accessesDirectly <solar_panel> . 

If there is a direct access connection between a core entity and a field entity, then one may infer the core entity can directly access the field entity.

directly managed by

IRI: https://w3id.org/seas/directlyManagedBy

Links a SEAS field entity to the group manager that directly manages it.

This property can be qualified using class seas:DirectManagementConnection, which connects the group manager and the field entities it directly manages.

For example, for a home management system to directly manage a smart fridge, then it must have a management connection to it:

<home_management_system> a seas:GroupManager .
<smart_fridge> a seas:FieldEntity .
<home_management_system> seas:directlyManages <smart_fridge> . 

If there is a direct management connection between a group manager and a field entity, then one may infer the group manager directly manage the field entity.

directly manages

IRI: https://w3id.org/seas/directlyManages

Links a SEAS group manager to a SEAS field entity it directly manages.

This property can be qualified using class seas:DirectManagementConnection, which connects the group manager and the field entities it directly manages.

For example, for a home management system to directly manage a smart fridge, then it must have a management connection to it:

<home_management_system> a seas:GroupManager .
<smart_fridge> a seas:FieldEntity .
<home_management_system> seas:directlyManages <smart_fridge> . 

If there is a direct management connection between a group manager and a field entity, then one may infer the group manager directly manages the field entity.

exchanges information with

IRI: https://w3id.org/seas/exchangesInformationWith

Links a SEAS core entity to another SEAS core entity it exchanges information with.

This property can be qualified using class seas:CoreEntityConnection, which connects (at least) the two core entities.

For example, for information to flow between a system operator and a market operator, then they must share a core entity connection:

<system_operator> a seas:CoreEntity .
<market_operator> a seas:CoreEntity .
<system_operator> seas:exchangesInformationWith <market_operator> . 

If there is a core entity connection between several core entities, then one may infer these core entities can exchange information.