Capability Ontology

From TAPAS Wiki

Jump to: navigation, search

Capability Ontology (CapOnt) defines node, capability types, capability parameters and service management functions. This generic concept structure is denoted as Upper Capability Ontology, illustrated in the figure below.

General concepts of Capability Ontology
General concepts of Capability Ontology

Capability type defines entities with common characteristics.

Capability parameter describes the characteristics of a capability type.

Service management function is a capability-related action with constraints.

Capability Ontology can define both rule-based and non-rule-based concepts. The non-rule-based concepts are the node, capability types, non-rule-based capability parameters and their relations. The rule-based concepts are rule-based capability parameters and service management functions.

The non-rule-based concepts are expressed by OWL (Web Ontology Language), while the rule-based concepts are expressed by OWL/XDD (XML Declarative Description). OWL/XDD extends ordinary XML-based elements by incorporation of variables.

In general, the concepts of Managed objects information models in different network management frameworks are a subset of the CapOnt concepts, but represented by using different languages. Examples are SMI/ASN.1 for SNMP, Common Information Model (CIM/XML) for WBEM and YANG/XML for NETCONF. If SNMP MIB is considered, SNMP MIB managed objects will be projects to capability types and non-rule-based capability parameters in the CapOnt.

The generic non-rule-based concepts in an abstract syntax OWL file is available here

As an example, the CapOnt non-rule-based concepts, based on the interfaces MIB group in SNMP IF-MIB (RFC 2863), in an abstract syntax OWL file is available here

In some of our publications, Capability Ontology, capability types and capability parameters are prefixed with 'node', in order to prevent conflict between these and the NETCONF capability from NETCONF management framework.

Personal tools