IRI:
http://timbus.teco.edu/ontologies/DIO.owl
Version IRI:
http://timbus.teco.edu/ontologies/2014/10/DIO.owl
Other visualisation:
Ontology source

Table of Content

  1. Classes
  2. Object Properties
  3. Namespace Declarations

Classes

active structural aspectc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#ActiveStructuralAspect

has super-classes
structural aspectc

and junctionc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#AndJunction

has super-classes
junctionc

application collaborationc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#ApplicationCollaboration

has super-classes
archimate conceptc

application componentc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#ApplicationComponent

has super-classes
archimate conceptc

application functionc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#ApplicationFunction

has super-classes
archimate conceptc

application interactionc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#ApplicationInteraction

has super-classes
archimate conceptc

application interfacec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#ApplicationInterface

has super-classes
archimate conceptc

application layerc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#ApplicationLayer

has super-classes
layerc

application servicec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#ApplicationService

has super-classes
archimate conceptc

artifactc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Artifact

has super-classes
archimate conceptc

assessmentc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Assessment

has super-classes
archimate conceptc

behavioral aspectc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BehavioralAspect

has super-classes
aspectc

business actorc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessActor

has super-classes
archimate conceptc

business collaborationc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessCollaboration

has super-classes
archimate conceptc

business eventc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessEvent

has super-classes
archimate conceptc

business functionc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessFunction

has super-classes
archimate conceptc

business interactionc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessInteraction

has super-classes
archimate conceptc

business interfacec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessInterface

has super-classes
archimate conceptc

business layerc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessLayer

has super-classes
layerc

business objectc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessObject

has super-classes
archimate conceptc

business processc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessProcess

has super-classes
archimate conceptc

business rolec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessRole

has super-classes
archimate conceptc

business servicec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#BusinessService

has super-classes
archimate conceptc

communication pathc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#CommunicationPath

has super-classes
archimate conceptc

constraintc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Constraint

has super-classes
archimate conceptc

contractc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Contract

has super-classes
archimate conceptc

data objectc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#DataObject

has super-classes
archimate conceptc

deliverablec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Deliverable

has super-classes
archimate conceptc

devicec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Device

has super-classes
archimate conceptc

driverc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Driver

has super-classes
archimate conceptc

gapc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Gap

has super-classes
archimate conceptc

goalc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Goal

has super-classes
archimate conceptc

infrastructure functionc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#InfrastructureFunction

has super-classes
archimate conceptc

infrastructure interfacec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#InfrastructureInterface

has super-classes
archimate conceptc

infrastructure servicec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#InfrastructureService

has super-classes
archimate conceptc

junctionc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Junction

has super-classes
archimate conceptc
has sub-classes
and junctionc

locationc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Location

has super-classes
archimate conceptc

meaningc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Meaning

has super-classes
archimate conceptc

networkc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Network

has super-classes
archimate conceptc

nodec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Node

has super-classes
archimate conceptc

passive structural aspectc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#PassiveStructuralAspect

has super-classes
structural aspectc

plateauc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Plateau

has super-classes
archimate conceptc

principlec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Principle

has super-classes
archimate conceptc

productc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Product

has super-classes
archimate conceptc

representationc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Representation

has super-classes
archimate conceptc

requirementc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Requirement

has super-classes
archimate conceptc

stakeholderc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Stakeholder

has super-classes
archimate conceptc

structural aspectc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#StructuralAspect

has super-classes
aspectc
has sub-classes
active structural aspectc, passive structural aspectc

system softwarec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#SystemSoftware

has super-classes
archimate conceptc

technology layerc back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#TechnologyLayer

has super-classes
layerc

valuec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#Value

has super-classes
archimate conceptc

work packagec back to ToC or Class ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#WorkPackage

has super-classes
archimate conceptc

Object Properties

accessed byop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#accessedBy

is inverse of
accessesop

accessesop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#accesses

has super-properties
depends downop
is inverse of
accessed byop

aggregated byop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#aggregatedBy

is inverse of
aggregatesop

aggregatesop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#aggregates

has super-properties
depends downop
is inverse of
aggregated byop

assigned fromop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#assignedFrom

is inverse of
assigned toop

assigned toop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#assignedTo

has super-properties
depends downop
is inverse of
assigned fromop

associationop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#association

communicates withop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#communicatesWith

component ofop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#componentOf

has sub-properties
composesop
is inverse of
composed ofop

composed ofop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#composedOf

has super-properties
depends downop
is inverse of
component ofop

composesop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#composes

has characteristics: transitive

has super-properties
component ofop

depends downop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#dependsDown

has characteristics: transitive

has sub-properties
accessesop, aggregatesop, assigned toop, composed ofop, usesop
is inverse of
depends upop
has sub-property chains
specializesop o depends downop

depends upop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#dependsUp

has characteristics: transitive

has sub-properties
flow toop, realizesop, triggersop
is inverse of
depends downop

flow fromop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#flowFrom

has characteristics: transitive

is inverse of
flow toop

flow toop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#flowTo

has super-properties
depends upop
is inverse of
flow fromop

has aspectop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#hasAspect

has range
has aspectop some aspectc

has layerop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#hasLayer

has range
has layerop some layerc

has specializationop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#hasSpecialization

has sub-properties
specializationop
is inverse of
specializesop

realized byop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#realizedBy

is inverse of
realizesop

realizesop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#realizes

has super-properties
depends upop
is inverse of
realized byop

specializationop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#specialization

has super-properties
has specializationop

specializesop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#specializes

has characteristics: transitive

is inverse of
has specializationop

triggered byop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#triggeredBy

is inverse of
triggersop

triggersop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#triggers

has super-properties
depends upop
is inverse of
triggered byop

used byop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#usedBy

is inverse of
usesop

usesop back to ToC or Object Property ToC

IRI: http://timbus.teco.edu/ontologies/DIO.owl#uses

has super-properties
depends downop
is inverse of
used byop

Namespace Declarations back to ToC

default namespace
http://timbus.teco.edu/ontologies/DIO.owl#
10
http://timbus.teco.edu/ontologies/2014/10/
ontologies
http://timbus.teco.edu/ontologies/
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.