Pattern stOTTR 🛈 stOTTR serialisation of the template without annotation instances.
inter:AssetTaxonomy[
owl:NamedIndividual ?funcLocation,
xsd:string ?descr,
xsd:string ?eqdescr,
owl:Class ?eqcode
] :: {
tmp:Asset(?funcLocation, ?descr, ?eqdescr, ?eqcode)
} . 🛈 The pattern of the template is illustrated by expanding a generated instance. Below the generated instance is shown in different serialisations, and its expansion is presented in different formats.
Generated instance stOTTR inter:AssetTaxonomy(x:argument1, _:argument2, _:argument3, x:argument4) RDF/wOTTR
[ ottr:of inter:AssetTaxonomy ;
ottr:values ( x:argument1
[]
[]
x:argument4
)
] . Visualisation of expanded RDF graph 🛈 Each resource node is linked to its IRI. Type relationships are not visualised, rather each node contains its type.
Hierarchical horizontal layout (dot)
%3
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>
x:argument4
x:argument1
argument3 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument3 : LUB<rdfs:Resource>
fmea:EquipmentTypeDescription
argument2 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument2 : LUB<rdfs:Resource>
fmea:Description
Hierarchical vertical layout (dot)
%3
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>
x:argument4
x:argument1
argument3 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument3 : LUB<rdfs:Resource>
fmea:EquipmentTypeDescription
argument2 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument2 : LUB<rdfs:Resource>
fmea:Description
Spring model layout (neato)
%3
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>
x:argument4
x:argument1
argument3 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument3 : LUB<rdfs:Resource>
fmea:EquipmentTypeDescription
argument2 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument2 : LUB<rdfs:Resource>
fmea:Description
Spring model layout (fdp)
%3
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>
x:argument4
x:argument1
argument3 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument3 : LUB<rdfs:Resource>
fmea:EquipmentTypeDescription
argument2 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument2 : LUB<rdfs:Resource>
fmea:Description
Radial layout (twopi)
%3
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>
x:argument4
x:argument1
argument3 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument3 : LUB<rdfs:Resource>
fmea:EquipmentTypeDescription
argument2 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument2 : LUB<rdfs:Resource>
fmea:Description
Circular layout (circo)
%3
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>
x:argument4
x:argument1
argument3 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument3 : LUB<rdfs:Resource>
fmea:EquipmentTypeDescription
argument2 : LUB<rdfs:Resource>
http://example.ottr.xyz/argument/argument1 : LUB<ottr:IRI>->argument2 : LUB<rdfs:Resource>
fmea:Description
Expanded RDF graph
x:argument1 rdf:type x:argument4 ;
fmea:Description [] ;
fmea:EquipmentTypeDescription [] . Interactive expansion 🛈 Click the list to expand/contract one list element. Click 'expand/contact all' to expand/contract all elements. Note that the interactive expansion is not correct for instances that are marked by list expanders.
inter:AssetTaxonomy(x:argument1, _:argument2, _:argument3, x:argument4)
tmp:Asset(x:argument1, _:argument2, _:argument3, x:argument4)
ottr:Triple(x:argument1, fmea:EquipmentTypeDescription, _:argument3)
tmp:CodeDescription(x:argument1, _:argument2)
ottr:Triple(x:argument1, fmea:Description, _:argument2)
o-rdf:Type(x:argument1, x:argument4)
ottr:Triple(x:argument1, rdf:type, x:argument4)
Dependencies Dependency graph 🛈 The graph shows all the templates that this template depends on. The colour of the node indicates its namespace. Each node is linked to its documentation page.
Hierarchical horizontal layout (dot)
%3
inter:AssetTaxonomy
inter:AssetTaxonomy
tmp:Asset
tmp:Asset
inter:AssetTaxonomy->tmp:Asset
ottr:Triple
ottr:Triple
tmp:Asset->ottr:Triple
tmp:CodeDescription
tmp:CodeDescription
tmp:Asset->tmp:CodeDescription
o-rdf:Type
o-rdf:Type
tmp:Asset->o-rdf:Type
tmp:CodeDescription->ottr:Triple
o-rdf:Type->ottr:Triple
Hierarchical vertical layout (dot)
%3
inter:AssetTaxonomy
inter:AssetTaxonomy
tmp:Asset
tmp:Asset
inter:AssetTaxonomy->tmp:Asset
ottr:Triple
ottr:Triple
tmp:Asset->ottr:Triple
tmp:CodeDescription
tmp:CodeDescription
tmp:Asset->tmp:CodeDescription
o-rdf:Type
o-rdf:Type
tmp:Asset->o-rdf:Type
tmp:CodeDescription->ottr:Triple
o-rdf:Type->ottr:Triple
Spring model layout (neato)
%3
inter:AssetTaxonomy
inter:AssetTaxonomy
tmp:Asset
tmp:Asset
inter:AssetTaxonomy->tmp:Asset
ottr:Triple
ottr:Triple
tmp:Asset->ottr:Triple
tmp:CodeDescription
tmp:CodeDescription
tmp:Asset->tmp:CodeDescription
o-rdf:Type
o-rdf:Type
tmp:Asset->o-rdf:Type
tmp:CodeDescription->ottr:Triple
o-rdf:Type->ottr:Triple
Spring model layout (fdp)
%3
inter:AssetTaxonomy
inter:AssetTaxonomy
tmp:Asset
tmp:Asset
inter:AssetTaxonomy->tmp:Asset
ottr:Triple
ottr:Triple
tmp:Asset->ottr:Triple
tmp:CodeDescription
tmp:CodeDescription
tmp:Asset->tmp:CodeDescription
o-rdf:Type
o-rdf:Type
tmp:Asset->o-rdf:Type
tmp:CodeDescription->ottr:Triple
o-rdf:Type->ottr:Triple
Radial layout (twopi)
%3
inter:AssetTaxonomy
inter:AssetTaxonomy
tmp:Asset
tmp:Asset
inter:AssetTaxonomy->tmp:Asset
ottr:Triple
ottr:Triple
tmp:Asset->ottr:Triple
tmp:CodeDescription
tmp:CodeDescription
tmp:Asset->tmp:CodeDescription
o-rdf:Type
o-rdf:Type
tmp:Asset->o-rdf:Type
tmp:CodeDescription->ottr:Triple
o-rdf:Type->ottr:Triple
Circular layout (circo)
%3
inter:AssetTaxonomy
inter:AssetTaxonomy
tmp:Asset
tmp:Asset
inter:AssetTaxonomy->tmp:Asset
ottr:Triple
ottr:Triple
tmp:Asset->ottr:Triple
tmp:CodeDescription
tmp:CodeDescription
tmp:Asset->tmp:CodeDescription
o-rdf:Type
o-rdf:Type
tmp:Asset->o-rdf:Type
tmp:CodeDescription->ottr:Triple
o-rdf:Type->ottr:Triple
List of dependencies 🛈 The number in parenthesis is the number of instances of each template.
inter:AssetTaxonomy tmp:Asset (1) ottr:Triple (1) tmp:CodeDescription (1) ottr:Triple (1) o-rdf:Type (1) ottr:Triple (1)
Depending templates 🛈 The templates in this library that depend on this template.
None found.
Serialisations stOTTR inter:AssetTaxonomy[
owl:NamedIndividual ?funcLocation,
xsd:string ?descr,
xsd:string ?eqdescr,
owl:Class ?eqcode
] :: {
tmp:Asset(?funcLocation, ?descr, ?eqdescr, ?eqcode)
} . RDF/wOTTR
inter:AssetTaxonomy rdf:type ottr:Template ;
ottr:parameters ( [ ottr:type owl:NamedIndividual ;
ottr:variable _:b0
]
[ ottr:type xsd:string ;
ottr:variable _:b1
]
[ ottr:type xsd:string ;
ottr:variable _:b2
]
[ ottr:type owl:Class ;
ottr:variable _:b3
]
) ;
ottr:pattern [ ottr:of tmp:Asset ;
ottr:values ( _:b0
_:b1
_:b2
_:b3
)
] . 🛈 Prefixes are removed from all listings on this page for readability, but are listed here in RDF Turtle format.
@prefix ottr: <http://ns.ottr.xyz/0.4/>.
@prefix tmp: <http://tpl.ottr.xyz/p/asset-maintenance/general/0.1/>.
@prefix inter: <http://tpl.ottr.xyz/p/asset-maintenance/interface/0.1/>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix owl: <http://www.w3.org/2002/07/owl#>.