tekom iiRDS Standard

intelligent information Request and Delivery Standard

Version 1.0 Release Date

Editors:
Frauke Becker (parson)
Sebastian Göttel (SCHEMA)
Martin Kreutzer (Empolis)
Win Nuding (cognitas)
Jan Oevermann (ICMS)
Ulrike Parson (parson)
Jürgen Sapara (tecteam)
Mark Schubert (parson)
Achim Steinacker (intelligent views)
Markus Wiedenmaier (practice innovation)
Author:
iiRDS Consortium (List of contributors)
Implementation:
iiRDS Core RDF Schema
iiRDS Machinery Domain RDF Schema
iiRDS Software Domain RDF Schema
Previous Version:
Request for Comments
Next Version:
iiRDS 1.0.1
Other Resources:
Website
Consortium
License

Abstract

This document defines the intelligent information Request and Delivery Standard: iiRDS.

Status of This Document

This document is published by the iiRDS Consortium and specifies version 1.0 of iiRDS.

If you wish to make comments regarding this document, please send them to comment.iirds@tekom.de.

1. Conformance

Sections marked as non-normative, as well as all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.

The keywords MAY, MUST, MUST NOT, OPTIONAL, RECOMMENDED, REQUIRED, and SHALL are to be interpreted as described in [rfc2119].

2. Introduction

This section is non-normative.

2.1 About iiRDS

iiRDS is a standard for the delivery of intelligent information in the scope of user assistance for products. The information is provided with the product for the purpose of assisting the users in setting up, operating, and maintaining the product. Intelligent information is defined as technical documentation content enriched with metadata.

iiRDS consists of:

iiRDS provides a common vocabulary for technical documentation content that enables users and applications to search and retrieve content based on common terms. Examples are standardized terms for product lifecycle phases (such as maintenance and operation) and information types (such as task and learning). iiRDS does not standardize terms that are defined by the manufacturer or supplier of the product, such as component names or product features. For these cases, iiRDS provides docking points that enable iiRDS Generators to add their custom vocabulary.

iiRDS is capable of processing many file formats and different levels of granularity, for example classic PDF files, 3D animations, as well as highly structured XML topics. The intelligent part (i.e. contextualization) of iiRDS is not achieved by structured content but by metadata.

For the content files delivery in the package, iiRDS Generators use arbitrary content formats or the restricted iiRDS HTML5 format. The restricted format consists of a predefined set of XHTML elements and media formats for maximum compatibility between iiRDS Consumers. Packages with this format are called iiRDS/A packages. See iiRDS XHTML5 Format.

2.1.1 Purpose of iiRDS

iiRDS is a standard for delivering packages with user assistance content that include both content and metadata. The metadata are delivered in an RDF file and use the iiRDS vocabulary. iiRDS Generators can extend the predefined iiRDS vocabulary with custom classes and instances, according to the rules for proprietary extensions. See iiRDS Domains and Proprietary Extensions.

iiRDS enables the exchange and assembly of digital user assistance content across systems and manufacturers. iiRDS Consumers use the common iiRDS vocabulary to find and assemble information according to information types, target audience, and working task. iiRDS supports update scenarios for digital user assistance. Depending on the format of the content in the iiRDS package, iiRDS Consumers adapt the content to the end device.

iiRDS does not stipulate any requirements regarding the tools and formats used for authoring the content.

Package information in iiRDS/A is suitable for long-term archiving. iiRDS Generators can use iiRDS/A packages that have predefined, restricted content formats and are self-contained.

2.1.2 iiRDS in the Context of Other Standardization Initiatives

iiRDS uses metadata from the following international standard:

  • DIN EN 82045-2: Document management – Part 2: Metadata elements and information reference model. See [IEC82045-2].

Other initiatives include:

2.2 Who defines iiRDS?

Starting 2016, iiRDS was developed by volunteers of the working group "Information 4.0" of tekom, the German Association for Technical Communication. In January 2018, the newly founded iiRDS Consortium took over the work and is now responsible for the further development of iiRDS.

2.2.1 Individual Contributors

Bader, Sebastian (Karlsruhe Institute of Technology), Bartsch, Jannik (t3), Baumgart, Elmar (t3), Baur, Manuel (Voith), Börsig, Rainer (FCT), Fisher, Rochelle, Fritz, Michael (tekom), Gentz, Stefan (Adobe), Göttel, Sebastian (SCHEMA), Günter, Andreas (Trumpf), Haldimann, Ralf (ABB), Hallwachs, Judith (tekom), Heidel, Roland (Kommunikationslösungen), Hellfritsch, Edgar (doctima), Hieber, Melanie (tekom), Klinnert, Norbert (noxum), Kreutzer, Martin (Empolis), Kuprat, Torsten (Acolada), Leukert, Sven (SAP), Machert,Torsten (Atexis), Nanz, Philipp (Docufy), Nuding, Win (cognitas), Oevermann, Jan (ICMS), Parson, Ulrike (parson), Rath, Hans Holger (Docufy), Reißenweber, Uwe (Docufy), Robers, Ralf (Siemens), Römisch, Volker (noxum), Sapara, Jürgen (tecteam), Schaffner, Michael (BIOS), Schiele, Gregor (University of Duisburg-Essen), Schubert, Mark (parson), Schuebeler, Johann-Joergen (SMA), Steinacker, Achim (intelligent views), Steurer, Stephan (ICMS), Suárez-Figueroa, Mari Carmen (Technical University of Madrid), Walker, John (Semaku), Weber, Joachim (ZF), Wiedenmaier, Markus (practice innovation), Ziegler, Wolfgang (Karlsruhe University of Applied Sciences)

Special thanks to all members of the tekom Working Group on Terminology

2.2.2 Consortium Members

2.2.2.1 Founding Members

Adobe, Atexis GmbH, cognitas GmbH, docufy GmbH, Empolis Information Management GmbH, Endress+Hauser Group Services – Mestra AG, Fischer Computertechnik fct AG, ICMS GmbH, gds GmbH, Goldwind Science & Technology Co., Ltd., HansemEUG, Huawei Technologies Co., Ltd., intelligent views GmbH, ISE Information System Engineering Inc., Noxum GmbH, pantopix GmbH & Co. KG, parson AG, practice innovation, reinisch GmbH, SDL plc, SCHEMA Gruppe, STAR AG, T3 GmbH, tcworld GmbH, tecteam GmbH

2.2.2.2 Contributing Members

kothes GmbH

2.2.2.3 Sponsors

Semcon

3. Scope

This standard specifies the package and metadata formats for the exchange of technical documentation. It does not specify how the formats are implemented on the generator or consumer side.

4. Terms and Definitions

This section is non-normative.

For the purposes of this document, the following terms and definitions apply.

Note: For definitions and explanations of the iiRDS schema, see iiRDS RDF Schema Reference.

5. iiRDS Package and Container

5.1 iiRDS Package

An iiRDS package is a bundle of information units including content and metadata for delivery from an iiRDS Generator to an iiRDS Consumer. An iiRDS package MUST implement an iiRDS ZIP archive.

5.2 iiRDS Container

An iiRDS container is a directory structure that includes all files of an iiRDS package.

An iiRDS container MUST have a single root directory.

5.2.1 Metadata Location

An iiRDS container MUST have a directory META-INF. The directory is exclusively used for metadata on the iiRDS package and its contents.

The META-INF directory MUST contain the file metadata.rdf containing all metadata in RDF 1.1 XML syntax (see [rdf-syntax-grammar]). It is RECOMMENDED for iiRDS Consumers to ignore any other files in the META-INF directory.

5.2.2 Content Location

All other files (content, like PDF, HTML, media, Javascript, CSS) MUST be stored in arbitrary subdirectories below the root directory. Content files MUST NOT be placed in the root directory or in META-INF directory.

iiRDS Container

Figure 1 iiRDS Container Structure

5.2.3 Names of Files and Directories

For file and directory names, all Unicode characters [UNICODE] MAY be used, with the exception of the following characters:

  • /,”*:<,>\
  • the DEL character (U+007F)
  • characters from the ranges U+0000 to U+001F and U+0080 to U+009F
  • characters from the private use Unicode areas

File names are case-sensitive and MUST be unique within their parent directories. The length of file names is limited to 255 characters. Full path names (file names including the full directory path from the root) MUST NOT exceed 260 characters).

Limits have been chosen based on limits of commonly used file systems.

5.3 iiRDS ZIP Archive

An iiRDS ZIP archive is an iiRDS container implementation using a ZIP archive, e.g. for transportation and exchange between systems. The iiRDS ZIP archive is the default implementation of the iiRDS container. All processing applications MUST support this implementation. The file name of the iiRDS ZIP archive MUST have the file name extension .iirds.

iiRDS ZIP archive

Figure 2 iiRDS ZIP Archive Structure

The ZIP archive file format is defined in [ZIP].

In addition to the iiRDS container specifications, the root directory of the ZIP file MUST contain a file named mimetype. It MUST contain the following ASII-encoded text in a single line, without any line delimiters such as CR or LF:

application/iirds+zip

The file MUST be the first entry in the ZIP file and it MUST be stored uncompressed (“Stored” mode). By doing so, file types contained in iiRDS ZIP archives can be detected automatically without having to unpack the archive.

5.3.1 Mimetype of iiRDS

iiRDS ZIP archives are associated with the MIME type application/iirds+zip.

5.3.2 Content Encoding

In the ZIP archive, all file and directory names are UTF-8 encoded according to [ZIP].

All other files in the ZIP are either uncompressed (“Stored” compression mode) or compressed in “Deflated” mode. The ZIP archive MUST use the ZIP64™ extension [ZIP] if the file size is bigger than 4 GB or the package has more than 65536 file entries.

The iiRDS ZIP archive MUST NOT be encrypted.

6. The iiRDS Metadata Model in the RDF Schema

6.1 The iiRDS RDF Schema and Identifiers

iiRDS provides a vocabulary for documentation metadata as an RDF schema. The RDF schema contains the vocabulary and docking points for proprietary extensions.

The iiRDS vocabulary uses the following identifiers:

.

6.2 Information Units

6.2.1 Subclasses of iirds:InformationUnit

The iirds:InformationUnit is an abstract base class for pieces of intelligent information. Information units link user assistance content to metadata; they represent a specific set of metadata for a piece of information. iiRDS Generators MUST NOT use the iirds:InformationUnit class directly but MUST use one of the subclasses. An instance of an iirds:InformationUnit subclass MUST have an IRI and MUST NOT be a blank node.

The class iirds:InformationUnit has the following subclasses:

  • iirds:Document is a collection of information for an audience and a specific purpose.

  • iirds:Topic is self-contained piece of information which deals with a single subject. The reader understands a topic without additional information.

  • iirds:Fragment is a piece of information that a reader understands only with additional context information.

  • iirds:Package is a collection of iirds:InformationUnits bundled with the corresponding metadata within an iiRDS package. Each iiRDS package MUST have exactly one corresponding iirds:Package instance in the metadata. Information units point to the package that they belong to with the property iirds:is-part-of-package. The corresponding iirds:Package instance of an iiRDS package MUST NOT be a member of another iiRDS package expressed by the property iirds:is-part-of-package.

The subclasses iirds:Document, iirds:Topic, and iirds:Fragment represent metadata sets for intelligent information in different granularities: from the document to the fragment.

iirds:Document, iirds:Topic, and iirds:Fragment MAY refer to a physical file or a part of a file in the iiRDS package. But iirds:Document, iirds:Topic, and iirds:Fragment MAY also model abstract entities without a physical file in the iiRDS package.

6.2.2 InformationUnit Identifier

The subclasses of iirds:InformationUnit contain instances that link metadata to pieces of technical information. The property rdf:about identifies these instances using an internationalized resource identifier ([rfc3987]).

It is RECOMMENDED to use absolute IRIs in rdf:about. Additionally, it is RECOMMENDED to generate IRIs as follows:

  • Keep the IRI of rdf:about globally unique.
  • Keep the IRI of rdf:about stable over packages and time if the IRI identifies the same subject.
  • If the source system has a meaningful identifier such as a unique ID from the CMS, use it to generate an IRI for rdf:about.
Example 4: Topic and fragment with a globally unique resource identifier.
<iirds:Topic rdf:about="https://myCompany.com/iiRDS/myPackage/2017-07-22/123e4567-e89b-12d3-a456-426655440000">
    <iirds:format>text/html</iirds:format>
</iirds:Topic>

<iirds:Fragment rdf:about="urn:uuid:6e8bc430-9c3a-11d9-9669-0800200c9a66">
    <iirds:format>text/html</iirds:format>
</iirds:Fragment>

6.2.3 Information Objects

Information objects are instances of the iirds:InformationObject class. They group information units that logically contain the same information and only differ in language or revision. Information units that are language variants or revisions of another information unit have a relation to the same information object via the iirds:is-version-of property.

Information units MAY be related to information objects. If information objects are used, each information unit MUST only be related to exactly one information object via iirds:is-version-of.

An information object MUST have an absolute IRI and MAY be related to additional identifications via the iirds:has-identity property.

Example 5: An Information object with two language variants. The English variant has two revisions, the German only one.
<rdf:RDF
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns:iirds="http://iirds.tekom.de/iirds#"
 xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">

<iirds:InformationObject rdf:about="http://myCompany.com/informationobjects/io_1"/>

<iirds:Topic rdf:about="http://myCompany.com/versions/io_1/en/1">
  <iirds:title>Mounting the rotor</iirds:title>
  <iirds:language>en</iirds:language>
  <iirds:revision>1</iirds:revision>
  <iirds:is-version-of rdf:resource="http://myCompany.com/informationobjects/io_1"/>
  <iirds:has-topic-type rdf:resource="http://iirds.tekom.de/iirds#Task"/>
  <iirds:has-rendition>
    <iirds:Rendition>
      <iirds:format>application/html</iirds:format>
      <iirds:source>rendition/mounting_en_1.html</iirds:source>
    </iirds:Rendition>
  </iirds:has-rendition></iirds:Topic>

<iirds:Topic rdf:about="http://myCompany.com/versions/io_1/en/2">
  <iirds:title>Mounting the rotor</iirds:title>
  <iirds:language>en</iirds:language>
  <iirds:revision>2</iirds:revision>
  <iirds:is-version-of rdf:resource="http://myCompany.com/informationobjects/io_1"/>
  <iirds:has-topic-type rdf:resource="http://iirds.tekom.de/iirds#Task"/>
  <iirds:has-rendition>
    <iirds:Rendition>
      <iirds:format>application/html</iirds:format>
      <iirds:source>rendition/mounting_en_2.html</iirds:source>
      </iirds:Rendition>
    </iirds:has-rendition></iirds:Topic>

<iirds:Topic rdf:about="http://myCompany.com/versions/io_1/de/1">
  <iirds:title>Rotor montieren</iirds:title>
  <iirds:language>de</iirds:language>
  <iirds:revision>1</iirds:revision>
  <iirds:is-version-of rdf:resource="http://myCompany.com/informationobjects/io_1"/>
  <iirds:has-topic-type rdf:resource="http://iirds.tekom.de/iirds#GenericTask"/>
  <iirds:has-rendition>
    <iirds:Rendition>
      <iirds:format>application/html</iirds:format>
      <iirds:source>rendition/mounting_de_1.html</iirds:source>
    </iirds:Rendition>
  </iirds:has-rendition>
</iirds:Topic>

</rdf:RDF>

6.3 Content References of Information Units

Information units are abstract entities that assign metadata to content. Renditions of the content are stored as files in an iiRDS package. An iirds:InformationUnit MAY reference files in an iiRDS package by the property iirds:has-rendition.

iirds:Rendition refers to the physical file in the package. To identify the physical file, the property iirds:source MUST relate the rendition to the URL of the physical file. The URL MUST be relative to the root folder of the iiRDS package. An iirds:Rendition MUST also have the property iirds:format.

Example 6: A topic with reference to a file
<iirds:Topic rdf:about="http://myCompany.com/iiRDS/myProject/myPackage/topic_1">
    <iirds:has-rendition>
        <iirds:Rendition>
            <iirds:format>application/xml</iirds:format>
            <iirds:source>rendition/general_safety.xml</iirds:source>
        </iirds:Rendition>
    </iirds:has-rendition>
</iirds:Topic>

An information unit MAY have one or more physical renditions in an iiRDS package. To reference multiple renditions, an information unit has multiple iirds:has-rendition properties. For each rendition, an information unit MAY reference the whole file or select a part or range.

6.3.1 Reference Part of File by Selector

The class iirds:Selector references parts of files. The property iirds:has-selector relates iirds:Rendition to an iirds:Selector. iirds:Rendition MUST NOT directly use iirds:Selector but MUST use one of its subclasses to reference parts of a file. The class iirds:Selector has the following subclasses:

  • iirds:FragmentSelector
    Selects a part of a file by a single identifier.
  • iirds:RangeSelector
    Selects a part of a file by a start and an end identifier.

To select parts of a file, an iirds:Selector MUST have an rdf:value and dcterms:conformsTo. The value MUST conform to the standard specified by the property dcterms:conformsTo. Only a standard from the following list of fragment selectors MUST be used: [https://www.w3.org/TR/annotation-model/#fragment-selector].

6.3.1.1 Reference Part with Single Identifier

The iirds:FragmentSelector refers to a single identifier in a file.

Depending on the file format and the associated standard, a single identifier of a fragment selector MAY select a range in a file.

6.3.1.2 Reference Part with Start and End Identifier

The iirds:RangeSelector points to the part of a file by a start and end selector. The range selector MUST be used to identify a range in a file if the file format or the associated standard do not permit selecting a range directly. The range selector references the start selector and end selector by the properties iirds:has-start-selector and iirds:has-end-selector.

6.3.2 Media Files

iiRDS represents media files as instances of information units. As iiRDS is not file-centered but content-centered, a media file is modeled depending on its actual content.

If a media file is not self-contained, then it MUST be modeled as iirds:Fragment.

Example 12: Fragment rendered as an image in an HTML page
<iirds:Fragment rdf:about="http://myCompany.com/iiRDS/myProject/myPackage/topic_786">
    <iirds:has-rendition>
        <iirds:Rendition>
            <iirds:format>text/html</iirds:format>
            <iirds:source rdf:resource="rendition/general_concepts.html"/>
            <iirds:has-selector>
                <iirds:FragmentSelector>
                    <dcterms:conformsTo rdf:resource="http://tools.ietf.org/rfc/rfc3023"/>
                    <rdf:value>#overview</rdf:value>
                </iirds:FragmentSelector>
            </iirds:has-selector>
        </iirds:Rendition>
    </iirds:has-rendition>
</iirds:Fragment>

6.4 Relations of InformationUnits

iiRDS relation properties link information units with information types, documentation metadata, and administrative metadata. iirds:InformationUnit MAY use relation properties.

For a list of all relation properties, see the iiRDS RDF Schema Reference.

6.5 Information Types

6.5.1 Types of Documents and Topics

In order to support user searches for specific types of information, iiRDS provides standardized document and topic types.

Instances of the iirds:Document class MUST have one or more relation to one of the standardized iirds:DocumentTypes defined in iirds:InformationType > iirds:DocumentType.

It is RECOMMENDED to create more than one relation to iirds:DocumentType for documents with mixed content.

All instances of the iirds:InformationUnit subclasses MAY have one or more relations to one of the standardized topic types defined in iirds:InformationType > iirds:TopicType. iirds:TopicType MAY also be used for fragments.

Instances of the iirds:Topic and iirds:Fragment classes MAY have a relation of type iirds:applicable-for-document-type to one of the standardized document types defined in iirds:InformationType > iirds:DocumentType.

6.5.2 Information Subjects

iiRDS information subjects describe the nature of the content, what the content is about. They represent typical information types and usage scenarios for technical documentation.

The property iirds:has-subject relates an iirds:InformationUnit to an information subject. An iirds:InformationUnit MAY have multiple iirds:has-subject relations to multiple information subjects.

6.6 Documentation Metadata

iiRDS iirds:DocumentationMetadata describes the relevance of the content and additional filter conditions related to the content.

iiRDS distinguishes between iirds:FunctionalMetadata and iirds:ProductMetadata:

iirds:DocumentationMetadata subclasses without further subclasses are docking points. A docking point MAY be extended by proprietary subclasses and instances to model company- or industry-specific resources.

6.6.1 Functional Metadata

iirds:FunctionalMetadata enables iiRDS Consumers to implement advanced content delivery scenarios. An iiRDS package MAY contain iirds:FunctionalMetadata.

The following subclasses are available:

  • iirds:Event: Represents events in the technical equipment. Instances of the iirds:Event class MUST have the following properties: iirds:eventCode and iirds:eventType. The iirds:Event class is a docking point for iiRDS Generators to link documentation content with event information code according to a standard like OPC-UA or a custom convention. The property iirds:relates-to-event links iirds:InformationUnit with iirds:Event.

  • iirds:Supply: Describes tools, spare parts, and supplies for a task. The property iirds:relates-to-supply links iirds:InformationUnit with iirds:Supply.

  • iirds:PlanningTime: Planning times describe intervals or periods of time required for or resulting from specific working tasks. The property iirds:has-planning-time links iirds:InformationUnit with iirds:PlanningTime.

  • iirds:Qualification: Describes industry- or company-specific vocational qualifications, certificates, training, and roles. iiRDS does not provide standardized terms for these concepts because the terms vary largely between countries and industries. The property iirds:relates-to-qualification links iirds:InformationUnit with iirds:Qualification.

6.6.2 Product Metadata

iirds:ProductMetadata contains classes for storing information on products, components, lifecycle phases, and product features. Subproperties of iirds:relates-to-product-metadata link iirds:ProductMetadata to iirds:InformationUnit.

The subclasses iirds:ProductVariant and iirds:Component are docking points. The class iirds:ProductFeature contains the subclasses iirds:ProductProperty and iirds:ProductFunction as additional docking points. A docking point MAY be extended by proprietary subclasses and instances to model company- or industry-specific resources.

iiRDS subclasses of iirds:ProductLifeCyclePhase represent standard product lifecycle phases.

6.7 Products and Components in iiRDS

iiRDS models products and components as metadata for technical documentation. The metadata iirds:Component or iirds:ProductVariant MAY have a relation to the physical product or component.

The properties iirds:relates-to-component and iirds:relates-to-product-variant relate an information unit to an instance of iirds:Component or iirds:ProductVariant. The instances MUST be part of a proprietary iiRDS extension.

6.7.1 Component Trees in the Package

An iiRDS package MAY model a component tree. The property iirds:has-component defines part-of relations for products and their components. The component tree is a proprietary iiRDS extension, it MUST be stored in the metadata.rdf of the iiRDS package.

Note

iiRDS does not differentiate between components and products when modeling component trees.

6.7.2 External Product Ontology

In addition to a component tree within a package, some parties MAY have a full-fledged external product ontology. A proprietary iiRDS extension MAY map the metadata labels in the package to the external product ontology. The product ontology MUST NOT be a proprietary iiRDS extension and MAY use another vocabulary than RDF and RDFS.

Note

While iiRDS product metadata represents metadata labels for information units, the products and components in the external product ontology represent the physical items.

An iiRDS package MUST NOT use an external product ontology directly. If an external product ontology is available and used in the iiRDS package, then the iiRDS package MUST also contain metadata labels as instances of iirds:Component.

An iiRDS package with iirds:Component MAY use iirds:has-component relations to model a component tree.

To map the component tree in the iiRDS package to the external product ontology, a mapping ontology MUST use the property rdfs:seeAlso.

The property rdfs:seeAlso MUST relate the instance of the component in the iiRDS package to the external product ontology. The property rdfs:seeAlso MAY be part of the file metadata.rdf in the iiRDS package or part of the external product ontology.

6.7.3 Product Variants

iiRDS provides the class iirds:ProductVariant for extending the iiRDS vocabulary and adding proprietary product variants. As product variants are a proprietary iiRDS extension, they MUST be present in the metadata.rdf of the iiRDS package.

Example 23: Definition of a proprietary product variant
<iirds:ProductVariant rdf:about="http://myCompany.com/iirds/myProject/myPackage#FreshDelightE61">
    <rdfs:label xml:lang="en">Fresh Delight E61</rdfs:label>
</iirds:ProductVariant>

To map product variants in the iiRDS package to an external product ontology, a mapping ontology MUST use the property rdfs:seeAlso.

The property rdfs:seeAlso MUST relate the instance of the product variant in the iiRDS package to the external product ontology. The property rdfs:seeAlso MAY be part of the file metadata.rdf in the iiRDS package or part of the external product ontology.

6.8 Administrative Metadata

All administrative metadata classes are subclasses of the class iirds:AdministrativeMetadata and group administrative information.

Administrative information is often used and stored in document management systems (DMS) or component content management systems (CCMS) for administrative purposes and MAY be added to an iiRDS entity.

Administrative metadata in iiRDS MAY be used in compliance with [IEC82045-2] and [VDI2770]. For further information, see the corresponding standard documents.

6.8.1 Complex Identity

Instances of the iirds:Identity class are unambiguous identifications of entities in the scope of a given domain. Instances of the classes iirds:ProductVariant, iirds:Component, iirds:InformationObject, and iirds:InformationUnit MAY have iirds:has-identity relations to iirds:Identity instances.

An iirds:Identity instance consists of two parts: the value and the domain. The value MUST be provided as a non-empty string in the iirds:identifier property. An identity MUST point to exactly one domain by the iirds:has-identity-domain property. The domain is an instance of the iirdsIdentityDomain class.

Instances of class iirds:IdentityDomain MUST have an absolute IRI and MAY link to the custodian of the domain via the iirds:has-party property. Custodians are contained in instances of the iirds:Party class.

Example 26: Identities of an information object and a topic
<rdf:RDF
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:iirds="http://iirds.tekom.de/iirds#"
    xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
    xmlns:vcard="http://www.w3.org/2006/vcard/ns#">


<iirds:IdentityDomain rdf:about="http://myCompany.com/cms1/modules"/>

<iirds:IdentityDomain rdf:about="http://myCompany.com/cms1/versions"/>

<iirds:IdentityDomain rdf:about="http://myCompany.com/cms1/pubs"/>

<iirds:InformationObject rdf:about="http://myCompany.com/informationobjects/io_1">
  <iirds:has-identity>
    <iirds:Identity>
      <iirds:identifier>89761</iirds:identifier>
      <iirds:has-identity-domain rdf:resource="http://myCompany.com/cms1/modules"/>
    </iirds:Identity>
  </iirds:has-identity>
</iirds:InformationObject>

<iirds:Topic rdf:about="http://myCompany.com/versions/io_1/en/1">
  <iirds:has-identity>
    <iirds:Identity>
      <iirds:identifier>4531</iirds:identifier>
      <iirds:has-identity-domain rdf:resource="http://myCompany.com/cms1/versions"/>
    </iirds:Identity>
  </iirds:has-identity>
  <iirds:has-identity>
    <iirds:Identity>
      <iirds:identifier>V6952</iirds:identifier>
      <iirds:has-identity-domain rdf:resource="http://myCompany.com/pubs"/>
    </iirds:Identity>
  </iirds:has-identity>
  <iirds:title>Mounting the rotor</iirds:title>
  <iirds:revision>1</iirds:revision>
  <iirds:has-topic-type rdf:resource="http://iirds.tekom.de/iirds#GenericTask"/>

  <!-- omitted -->

</iirds:Topic>

</rdf:RDF>
Example 27: Product with an identity used for an item number
<iirds:ProductVariant rdf:about="http://myCompany.com/products/TableFan">
  <iirds:has-identity>
    <iirds:Identity>
      <iirds:identifier>871321</iirds:identifier>
      <iirds:has-identity-domain rdf:resource="http://myCompany.com/products/Items"/>
    </iirds:Identity>
  </iirds:has-identity>
  <rdf:label>Table fan</rdf:label>
</iirds:ProductVariant>
Example 28: Identity domain with party information
<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:iirds="http://iirds.tekom.de/iirds#"
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
  xmlns:vcard="http://www.w3.org/2006/vcard/ns#">

  <iirds:IdentityDomain rdf:about="http://myCompany.com/supplier/SupCo/products">
    <rdf:label xml:lang="en">SupCo Product IDs</rdf:label>

    <iirds:relates-to-party>
      <iirds:Party rdf:about="http://myCompany.com/supplier/SupCo">
        <iirds:has-party-role rdf:resource="http://iirds.tekom.de/iirds#Supplier"/>
        <iirds:relates-to-vcard>
          <vcard:Organizationc rdf:about="http://supco.com/about">
            <vcard:fn>SupCo Ltd.</vcard:fn>
          </vcard:Organizationc>
        </iirds:relates-to-vcard>
      </iirds:Party>
    </iirds:relates-to-party>
  </iirds:IdentityDomain>
</rdf:RDF>

6.8.2 Content Lifecycle Status

An iirds:InformationUnit MAY have iirds:has-content-lifecycle-status relations to one or multiple iirds:ContentLifecyleStatus instances to describe different status or status transitions in the administrative content lifecycle.

An iirds:ContentLifecyleStatus MUST have an iirds:ContentLifecyleStatusValue which is assigned by the iirds:has-content-lifecycle-status-value property. It MAY have additional associated dates or annotations.

Example 29: Topic with content lifecycle metadata
<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:iirds="http://iirds.tekom.de/iirds#"
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">

  <iirds:Topic rdf:about="http://myCompany.com/io/1312">
    <iirds:title>Mounting the rotor</iirds:title>
    <iirds:language>en</iirds:language>
    <iirds:revision>1</iirds:revision>
    <iirds:has-topic-type rdf:resource="http://iirds.tekom.de/iirds#GenericTask"/>

    <iirds:has-content-lifecycle-status>
      <iirds:ContentLifeCycleStatus>
        <iirds:dateOfStatus>2018-04-10T15:28:09+01:00</iirds:dateOfStatus>
        <iirds:statusComment>Updated information on the mounting process.</iirds:statusComment>
        <iirds:has-content-lifecycle-status-value rdf:resource="http://iirds.tekom.de/iirds#Approved" />      </iirds:ContentLifeCycleStatus>
    </iirds:has-content-lifecycle-status>

    <iirds:has-rendition>
      <iirds:Rendition>
        <iirds:format>application/html</iirds:format>
        <iirds:source>rendition/mounting_en_1.html</iirds:source>
      </iirds:Rendition>
    </iirds:has-rendition>
  </iirds:Topic>
</rdf:RDF>

An iirds:ContentLifecyleStatus MAY also be related to an iirds:Party with a specific iirds:Role. The iirds:Party indicates the performer of the status transition.

Example 30: Content lifecylce status with party information
<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:iirds="http://iirds.tekom.de/iirds#"
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
  xmlns:vcard="http://www.w3.org/2006/vcard/ns#">

  <iirds:Topic rdf:about="http://myCompany.com/io/1312">
    <iirds:title>Mounting the rotor</iirds:title>
    <iirds:has-topic-type rdf:resource="http://iirds.tekom.de/iirds#GenericTask"/>

    <iirds:has-content-lifecycle-status>
      <iirds:ContentLifeCycleStatus>
        <iirds:has-content-lifecycle-status-value rdf:resource="http://iirds.tekom.de/iirds#PerfomedBy" /> 
        <iirds:dateOfStatus>2018-04-10T15:28:09+01:00</iirds:dateOfStatus>
        <iirds:statusComment>Updated information on the mounting process.</iirds:statusComment> 
        <iirds:relates-to-party>
          <iirds:Party rdf:about="http://myCompany.com/authors/jdo001">
            <iirds:has-party-role rdf:resource="http://iirds.tekom.de/iirds#Author"/>
            <iirds:relates-to-vcard>
              <vcard:Individual rdf:about="http://myCompany.com/u/jdo001">
                <vcard:fn>Jane Doe</vcard:fn>
                <vcard:hasEmail rdf:resource="mailto:jdoe@myCompany.com"/>
              </vcard:Individual>
            </iirds:relates-to-vcard>
          </iirds:Party>
        </iirds:relates-to-party>
      </iirds:ContentLifeCycleStatus>
    </iirds:has-content-lifecycle-status>

    <!-- omitted -->

  </iirds:Topic>
</rdf:RDF>

6.8.3 Parties and Roles

An iirds:Party MAY be assigned to any iirds:InformationUnit, iirds:ContentLifecycleStatus, iirds:Component, iirds:ProductVariant or iirds:IdentityDomain to express the relation to an associated actor with a specific role in this context.

An iirds:Party MUST have a related iirds:Role that is assigned by the property iirds:has-party-role, such as author, supplier or manufacturer.

In addition to the role, an iirds:Party MUST also have an associated description of itself as compliant vcard:kind object which is assigned via iirds:has-related-vcard.

6.9.1 Directory Nodes

Navigation sequences and hierarchies of InformationUnits MUST be modeled as linked lists of instances of the class iirds:DirectoryNode. In a linked list, a iirds:DirectoryNode references the following node by the property iirds:has-next-sibling. Each node of an iiRDS linked list MAY reference an iirds:InformationUnit by the property iirds:references-information-unit.

To model closed lists, the last node in a list level MUST have the property iirds:has-next-sibling relating to an instance of the class iirds:nil.

The property iirds:has-directory-structure-type determines the type of the directory structure. The root node of a directory structure MUST have one property iirds:has-directory-structure-type. Only root nodes of a directory structure MUST have the property iirds:has-directory-structure-type.

Example 33
Note

There is no direct relation between information units that represent navigation structures. For example, topic 1 has no direct relation to its successor topic 2. With no direct reference, iiRDS models reuse of information units in different contexts.

6.9.2 Hierarchical Navigation

To model hierarchy levels in the navigation structure, a iirds:DirectoryNode instance MUST reference a iirds:DirectoryNode instance on the next lower level by the property iirds:has-first-child. The directory node on the next lower level MUST be the first item of another linked list.

The property rdfs:label adds a title to a directory node. Blank nodes are used to add navigation titles that do not represent a topic.

7. iiRDS Domains and Proprietary Extensions

7.1 iiRDS Extension Scenarios

Additional classes and instances MAY extend the iiRDS core vocabulary. iiRDS supports the following extension scenarios:

A party that generates or processes an iiRDS package MAY combine iiRDS domains and proprietary iiRDS extensions.

All proprietary extensions that are used in a package MUST be contained in the file metadata.rdf in the iiRDS package. The file metadata.rdf MUST NOT contain the iiRDS schema or iiRDS domain extensions.

7.2 iiRDS Domain Extensions

iiRDS domain extensions are additional classes and instances that extend the iiRDS core vocabulary. iiRDS domain extensions are part of the standard iiRDS.

Instances and classes of iiRDS domain extensions are contained in sub-namespaces of iiRDS. The following iiRDS domain extensions are used:

Note

The iiRDS standard does not stipulate how to combine iiRDS core vocabulary with extension vocabulary.

7.3 Proprietary iiRDS Extensions

By using proprietary iiRDS extensions, iiRDS vocabulary MAY be extended. Proprietary iiRDS extensions contain project-specific instances, classes, and properties.

A proprietary iiRDS extension MUST fulfill the following conditions:

Proprietary iiRDS extensions MUST only use RDF and RDFS vocabulary in their extension ontology. If OWL DL is used in an additional ontology, then the ontology is not iiRDS-compliant but MAY be mapped to the iiRDS vocabulary by means of the seeAlso property. For details read section External Product Ontology.

7.3.1 Adding a Proprietary Instance

Proprietary iiRDS extensions MAY add instances directly as an instance of an iiRDS class.

Example 38: Adding a proprietary instance to iiRDS class
<rdf:RDF xml:lang="de" xmlns:iirds="http://iirds.tekom.de/iirds#"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
    <iirds:Role rdf:about="http://myCompany.com/myProject#ServiceTechnician">
        <rdfs:label xml:lang="en">Service Technician</rdfs:label>
        <rdfs:label xml:lang="de">Servicetechniker</rdfs:label>
    </iirds:Role>
</rdf:RDF>

7.3.2 Adding a Proprietary Class

Proprietary iiRDS extensions MAY add classes directly as subclasses to an iiRDS class. The following example adds the proprietary class Error to the iiRDS class iirds:Event as a subclass. A proprietary implementation adds its proprietary instances to the Error class and an iiRDS Consumer finds them by searching for instances of the iirds:Event class.

Example 39: Adding a proprietary subclass to an iiRDS class
<rdf:RDF xml:lang="de" xmlns:iirds="http://iirds.tekom.de/iirds#"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#">
    <rdfs:Class rdf:about="http://myCompany.com/myProject#Error">
        <rdfs:label xml:lang="en">Error</rdfs:label>
        <rdfs:label xml:lang="de">Fehler</rdfs:label>
        <rdfs:subClassOf rdf:resource="http://iirds.tekom.de/iirds#Event"/>
    </rdfs:Class>
</rdf:RDF>

Proprietary iiRDS extensions MAY add proprietary classes as equivalent classes. The property rdfs:subClassOf expresses equivalence of classes.

Example 40: Adding a proprietary class as an equivalent class
<rdfs:Class rdf:about="http://myCompany.com/myProject#ProductPart">
    <rdfs:subClassOf rdf:resource="http://iirds.tekom.de/iirds#Component"/>
</rdfs:Class>
<rdf:Description rdf:about="http://iirds.tekom.de/iirds#Component">
    <rdfs:subClassOf rdf:resource="http://myCompany.com/myProject#ProductPart"/>
</rdf:Description>

7.3.3 Adding a Proprietary Property

Proprietary iiRDS extensions MAY add proprietary properties as a subproperty of an iiRDS property. Proprietary properties MUST comply with domain and range of the iiRDS property. The following example shows a proprietary property that relates iirds:InformationUnit to iirds:ProductLifeCyclePhase.

Example 41: Adding a proprietary property as a subproperty of an iiRDS property
<rdf:Property rdf:about="http://www.myCompany.com/iirds/myExtension#has-maintenance-interval">
    <rdfs:subPropertyOf rdf:resource="http://iirds.tekom.de/iirds#has-planning-time"/>
    <rdfs:domain rdf:resource="http://iirds.tekom.de/iirds#InformationUnit"/>
    <rdfs:range rdf:resource="http://iirds.tekom.de/iirds#MaintenanceInterval"/>
</rdf:Property>

8. Content formats in iiRDS

8.1 Unrestricted iiRDS vs. iiRDS/A

An unrestricted iiRDS package MAY include any kind of content files. An iiRDS/A package MUST only include content files with a restricted set of formats.

Type and purpose of the content file are described by the iiRDS metadata. The use of metadata is the same for the restricted and the unrestricted set of content formats.

An iiRDS/A package MUST fulfill all of the following criteria::

Example 42: Usage of the formatRestriction property
<iirds:Package rdf:about="urn:uuid:0d6f0611-e0bd-42c0-a842-b38617d46988">
    <iirds:iiRDSVersion>1.0</iirds:iiRDSVersion>
    <iirds:formatRestriction>A</iirds:formatRestriction>
</iirds:Package>

8.2 Self-contained iiRDS/A Packages

An iiRDS package is self-contained if all URIs used in the iiRDS XHTML5 files point to local resources contained in the package except for the following cross-reference mechanisms:

attribute href
references attribute id on element a
references attribute id on element area
references attribute id on element link
attribute cite
references attribute id on element q

iiRDS Consumers MAY omit these cross-references, e.g. if there is no internet access, and the content MUST be still consumable.

9. iiRDS/A Media Formats

Media in iiRDS/A packages MUST use the formats listed in this section. An unrestricted iiRDS package uses any media format.

9.1 Text Formats

iiRDS XHTML5

Structured textual content MUST be encoded as iiRDS XHTML5. The file extension MUST be .xhtml.

PDF/A

Structured textual content MAY be encoded as PDF/A-3 (ISO 19005-3:2012). Non-structured textual content MUST be encoded this way. The file extension MUST be .pdf.

9.2 Graphics Formats

9.2.1 Raster Formats

PNG / JPEG

Raster graphics MUST be encoded as

  • PNG 1.2 (ISO/IEC 15948:2003) or higher using the file extension .png.

OR

  • JPEG (ISO/IEC 10918-1:1994) or higher using the file extension .jpg.

9.2.2 Vector Formats

SVG

Vector graphics MUST be encoded as restricted SVG 1.1 (W3C Scalable Vector Graphics (SVG) 1.1 (Second Edition) 2011). The file extension MUST be .svg for non-compressed files and .svgz for gzip-compressed files.

The following restrictions apply to the SVG format:

  • Only static language features of SVG that correspond to the feature string http://www.w3.org/TR/SVG11/feature#SVG-static MUST be used.
  • All linked resources (e.g. CSS, graphics, fonts) MUST be included in the iiRDS/A package.
  • Only JPG and PNG graphics according to this section MUST be used.
  • Reference to SVG media in iiRDS XHTML5 MUST use <img src="[filename]"/>.

9.3 Video Formats

MP4 (AVC/H.264)

Video content MUST be encoded as MP4 (ISO/IEC 14496-12 and -14) as container format and MPEG-4 Part 10 (AVC/H.264), MPEG-4 Part 3 as codecs. The file extension MUST be .mp4.

9.4 Audio Formats

MP3

Audio content MUST be encoded as MP3 (ISO/IEC 11172-3, ISO/IEC 13818-3). The file extension MUST be .mp3.

10. iiRDS XHTML5 Format

10.1 Overview

iiRDS XHTML5 is a profile of HTML5 for use in the context of iiRDS/A packages.

The XHTML document type defined by this specification is based on XHTML5. For details on HTML5 vs. XHTML5, see https://www.w3.org/TR/2014/REC-html5-20141028/introduction.html#html-vs-xhtml. Thus iiRDS XHTML5 inherits all definitions of semantics, structure and processing behaviors from the HTML5 specification unless otherwise specified.

Note

A similar approach to define a subset of HTML5 for a specific purpose is HTMLBook. See https://oreillymedia.github.io/HTMLBook/ for details.

As such, iiRDS XHTML5 is characterized in the following ways:

Note

The scope of iiRDS XHTML5 is to provide an easy to generate content transport and exchange format.

iiRDS XHTML5 is not meant as a presentation format. HTML5-capable browsers display a typical iiRDS XHTML5 file without additional effort but for state-of-the-art visualization and navigation, the content delivery relies on additional transformations or stylesheets. Because on purpose of iiRDS is supporting the aggregation of content and harmonized access to content from different sources, this is a conscious decision. Consequently, HTML5 elements that control navigation, display, interactivity, etc. are omitted from the iiRDS XHTML5 definition. Examples of omitted elements are <script>, <nav>, and <iframe>.

Unfortunately, so far there is no official XML schema for HTML5. See https://www.w3.org/TR/2014/REC-html5-20141028/the-xhtml-syntax.html#parsing-xhtml-documents for details. Respectively, there is no official XML schema for iiRDS XHTML5 either.

10.2 iiRDS XHTML5

This section defines a profile of [HTML5] for creating iiRDS XHTML5 content. An instance of an XML document that conforms to this profile is referred to as an iiRDS XHTML content in this specification.

Unless otherwise specified, this specification inherits all definitions of semantics, structure, and processing behaviors from the [HTML5] specification.

Only elements mentioned in this specification are part of iiRDS XHTML5.

If no content model or attributes are specified explicitly, then iiRDS XHTML5 MUST comply with the [HTML5] specification.

10.3 Conformance Criteria

iiRDS XHTML5 content MUST fulfill all of the following criteria:

10.4 Global Attributes

Global attributes are attributes common to all HTML elements. They MAY be applied to all elements.

Only the following subset of "Global attributes" from the HTML5 specification (https://www.w3.org/TR/html5/dom.html#global-attributes) MUST be used in iiRDS XHTML5 elements:

The global-attribute data-role is permitted for some specific elements.

The HTML5 specification for the attribute 'class' points out that “authors are encouraged to use values that describe the nature of the content, rather than values that describe the desired presentation of the content.” In contrast, iirds:class in iiRDS XHTML5 MUST only be used for styling. An iiRDS XHTML5 consumer MUST be able to ignore or modify class values without loss of meaning.

10.5 Elements

The following sections list the complete set of HTML5 elements availabe in iiRDS XHTML5. The element names are each linked to the HTML5 recommendation.

Attributes: Only global attributes and element-specific attributes specified in the iiRDS XHTML5 specification MUST be used.

10.5.1 Main Root

<html>

10.5.2 Document Metadata

<head> , <title> , <link>

The element <link> MUST be used only with the content attribute rel="stylesheet". Link types are always ASCII case-insensitive and MUST be compared as such. Relations usually represented by the element <link> in HTML MUST be expressed by means of RDF in iiRDS.

10.5.3 Sections

<body>, <h1–h6> , <section>

10.5.4 Grouping Content

<dd> , <div> , <dl> , <dt> , <figcaption> , <figure> , <li> , <ol> , <p> , <pre> , <ul>

Element-specific Content Attributes

Element Attribute
li (only inside ol) value
ol reversed
ol start
ol type

10.5.5 Text-Level Semantics

<a> , <abbr> , <b> , <bdi> , <bdo> , <br> , <code> , <em> , <i> , <kbd> , <q> , <s> , <samp> , <small> , <span> , <strong> , <sub>, <sup> , <u> , <wbr>

Element-specific Content Attributes

Element Attribute
a href
q cite

10.5.6 Embedded Content

<area> , <audio> , <img> , <map> , <source> , <track> , <video>

Element-specific Content Attributes

Element Attribute
area alt
area coords
area href
area shape
audio, img, video autoplay (not img)
audio, img, video alt (only img)
audio, img, video controls (not img)
audio, img, video height (not audio)
audio, img, video loop (not img)
audio, img, video mediagroup (not img)
audio, img, video muted(not img)
audio, img, video poster (only video)
audio, img, video preload (not img)
audio, img, video src (img), src (audio,video)
audio, img, video usemap (only img)
audio, img, video width (not audio)
map name
source src
track default
track kind
track label
track src
track srclang

10.5.7 Scripting

Scripting MUST NOT be used in iiRDS XHTML5.

10.5.8 Edits

<ins> , <del>

10.5.9 Tabular Data

<caption> , <col> , <colgroup> , <table> , <tbody> , <td> , <tfoot> , <th> , <thead> , <tr>

Element-specific Content Attributes

Element Attribute
col span
colgroup span
table border
td,th colspan
td,th headers
td,th rowspan
th scope
th abbr

10.5.10 Forms

Forms MUST NOT be used in iiRDS XHTML5.

10.5.11 SVG, MathML and IFrames

The elements <svg>, <math> and <iframe> MUST NOT be used in iiRDS XHTML5 content.

10.6 Additional Semantic Tagging of Content

The attribute data-role on HTML5 elements MAY express semantics of elements. Tagging with data-role MUST only be used with hazard statements.

If an iiRDS package contains content with hazard statements, then the iiRDS package MUST always provide the applicable safety alert symbols and signal words.

Note

The major objective of semantic tagging with data-role is to enable iiRDS Consumers to render information correctly on a display device. Hazard statements have a predefined structure not sufficiently reflected by the HTML5 element structure. A hazard statement consists of a safety alert symbol, a signal word, a message panel, and a symbol panel.

The data-role attribute MUST be used only in the situations described here. The attribute values given in the following table MUST be used.

Content Attributes Specific to Hazard Statements

data-role Value(s) Element Usage
caution, warning, danger, notice div Tags a div element to contain a hazard statement with the severity identified by the value.
signalword-panel div Tags a signal word panel of a hazard statement.
safety-alert-symbol img Tags a safety alert symbol of a hazard statement. The img element MUST be a child of the signal word panel. Only one safety alert symbol MUST be included.
signalword p Tags the signal word in the signal word panel of a hazard statement.
symbol-panel div Tags a panel that contains additional hazard symbols.
message-panel img Tags the message panel within a hazard statement.
Example 43: Tagging
<div data-role="caution">
    <div data-role="signalword-panel">
        <img data-role="safety-alert-symbol" src="..."></img>
        <p data-role="signalword">Caution</p>
    </div>
    <div data-role="symbol-panel">
        <img src="..."></img>
    </div>
    <div data-role="message-panel">
        <ul>
            <li>...</li>
            <li>...</li>
            <li>...</li>
        </ul>
    </div>
</div>

10.7 Styling

CSS stylesheet files MAY be referenced from the XHTML5 files for additional markup.

iiRDS XHTML5 is designed as an exchange format for structured content. It is RECOMMENDED for iiRDS Consumers to pre-process iiRDS XHTML5 content before displaying it.

An additional CSS stylesheet MAY be included, but processing of the content MUST NOT rely on the stylesheet. It is not specified how to mesh up accompanying CSS stylesheets and target-system CSS stylesheets.

A. iiRDS RDF Schema Reference

A.1 Core

A.1.1 Class Definitions

iirds:AdministrativeMetadata

Term Description
URI: http://iirds.tekom.de/iirds#AdministrativeMetadata
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Administrative metadata
Subclass Of: iirds:iirdsDomainEntity
Definition: Parent class for administrative metadata, such as status and identifier.
Description: Not intended to be used directly. Use the subclasses instead.

iirds:AfterUse

Term Description
URI: http://iirds.tekom.de/iirds#AfterUse
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: After use
Subclass Of: iirds:ProductLifeCyclePhase
Definition: Parent class for iiRDS standard definitions of product lifecycle phases that occur after the active use of the product.
Description: Not intended to be used directly. Use the subclasses instead. For lifecycle phases not covered by the iiRDS standard subclasses, define custom subclasses.
IRI: REQUIRED

iirds:Collection

Term Description
URI: http://iirds.tekom.de/iirds#Collection
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Collection
Subclass Of: iirds:InformationSubject
Definition: Parent class for information subjects representing collections of specific information, such as list of spare parts or maintenance plan.
Description: Not intented to be used directly. Use the subclasses instead. For collection subjects not covered by the iiRDS standard subclasses, define custom subclasses.
IRI: REQUIRED

iirds:Component

Term Description
URI: http://iirds.tekom.de/iirds#Component
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Component
Subclass Of: iirds:ProductMetadata
Definition: Describes a component of the technical system that the documentation refers to.
Description: Components MAY have relations to other components so that iiRDS Generators can build up a simple component hierarchy with iiRDS structures. The iirds#Component MAY also be used as a docking point for external component definitions.
IRI: REQUIRED
Properties: 0..⃰  iirds:has-component properties - iirds:Component
  0..⃰  iirds:has-identity properties - iirds:Identity
  0..1  iirds:relates-to-party property - iirds:Party

iirds:Concept

Term Description
URI: http://iirds.tekom.de/iirds#Concept
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Concept
Subclass Of: iirds:TopicType
Definition: Class of topic types that provide background that helps readers understand essential information about a product, interface, or task.
Description: Conceptual information helps users to map their existing knowledge to tasks and other essential information about a product or system.
IRI: REQUIRED

iirds:Conformity

Term Description
URI: http://iirds.tekom.de/iirds#Conformity
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Conformity
Subclass Of: iirds:InformationSubject
Definition: Parent class for information subjects that describe content related to applicable standards or the conformity of the product.
Description: Not intended to be used directly. Use the subclasses instead. For information subjects not covered by the iiRDS standard subclasses, define custom subclasses.
IRI: REQUIRED

iirds:ContentLifeCycleStatus

Term Description
URI: http://iirds.tekom.de/iirds#ContentLifeCycleStatus
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Information unit lifecycle status
Subclass Of: iirds:AdministrativeMetadata
Definition: Content lifecycle status of an information unit.
Description: The status value is referenced using has-content-lifecycle-status-value.
IRI: OPTIONAL
Properties: 0..1  iirds:dateOfEffect property - http://www.w3.org/2001/XMLSchema#dateTimeStamp
  0..1  iirds:dateOfExpiry property - http://www.w3.org/2001/XMLSchema#dateTimeStamp
  0..1  iirds:dateOfStatus property - http://www.w3.org/2001/XMLSchema#dateTimeStamp
  0..⃰  iirds:statusComment properties - http://www.w3.org/2000/01/rdf-schema#Literal
  1  iirds:has-content-lifecycle-status-value property - iirds:ContentLifeCycleStatusValue
  0..1  iirds:purpose property - http://www.w3.org/2000/01/rdf-schema#Literal
  0..1  iirds:relates-to-party property - iirds:Party

iirds:ContentLifeCycleStatusValue

Term Description
URI: http://iirds.tekom.de/iirds#ContentLifeCycleStatusValue
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Value of the information unit lifecycle status
Subclass Of: iirds:AdministrativeMetadata
Definition: Value of an information unit's lifecycle status. The value is set by involved parties, such as the manufacturer or supplier.
Description: The value refers to the content status, for example whether it is approved or withdrawn.
IRI: REQUIRED

iirds:DesignAndRealization

Term Description
URI: http://iirds.tekom.de/iirds#DesignAndRealization
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Design and realization
Subclass Of: iirds:ProductLifeCyclePhase
Definition: Parent class for subclasses that describe product lifecycle phases related to the design, construction, and realization of a product.
Description: Not intended to be used directly. Use the subclasses instead. For lifecycle phases not covered by the iiRDS standard subclasses, define custom subclasses.
IRI: REQUIRED

iirds:DirectoryNode

Term Description
URI: http://iirds.tekom.de/iirds#DirectoryNode
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Directory node
Subclass Of: iirds:iirdsDomainEntity
Definition: A node in a directory
Description: A directory is a tree-like, ordered collection of information units. Directory nodes are the entries in the directory. Directories help the user to navigate through the information units. A table of contents is a typical example of a directory.
IRI: OPTIONAL
Properties: 0..1  iirds:has-directory-structure-type property - iirds:DirectoryNodeType
  0..1  iirds:has-first-child property - iirds:DirectoryNode
  0..1  iirds:has-next-sibling property - iirds:DirectoryNode

iirds:DirectoryNodeType

Term Description
URI: http://iirds.tekom.de/iirds#DirectoryNodeType
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Directory node type
Subclass Of: iirds:InformationType
Definition: Directory type
Description: A directory represented by a directory root node and its sub nodes has a type such as 'table of contens' or 'list of figures'.
IRI: REQUIRED

iirds:Document

Term Description
URI: http://iirds.tekom.de/iirds#Document
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Document
Subclass Of: iirds:InformationUnit
Definition: A unit of information in an iiRDS package that represents a complete document.
Description: A document consists of one or more files. It can consist of topics. The resource is either a blank node (when there is no file representing the document) or a file in the iiRDS package.
IRI: REQUIRED
Properties: 1..⃰  iirds:has-document-type properties - iirds:DocumentType

iirds:DocumentationMetadata

Term Description
URI: http://iirds.tekom.de/iirds#DocumentationMetadata
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Documentation metadata
Subclass Of: iirds:iirdsDomainEntity
Definition: Parent class for functional metadata and product metadata.
Description: Not intended to be used directly. Use the subclasses instead.

iirds:DocumentType

Term Description
URI: http://iirds.tekom.de/iirds#DocumentType
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Document type
Subclass Of: iirds:InformationType
Definition: The type of a document.
Description: Document types define the intended purpose of a document.
IRI: REQUIRED

iirds:DownTime

Term Description
URI: http://iirds.tekom.de/iirds#DownTime
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Down time
Subclass Of: iirds:PlanningTime
Definition: Type of planning time: Period of time during which a technical system is stopped, especially during setup for an operation or when making repairs.
IRI: OPTIONAL

iirds:Event

Term Description
URI: http://iirds.tekom.de/iirds#Event
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Event
Subclass Of: iirds:FunctionalMetadata
Definition: Describes events that happen in the technical system
Description: Examples are errors, malfunctions, and warnings. Use the relates-to-event property to create a reference from an information unit to an event.
IRI: REQUIRED
Properties: 0..1  iirds:has-event-code property
  0..1  iirds:has-event-type property

iirds:Form

Term Description
URI: http://iirds.tekom.de/iirds#Form
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Form
Subclass Of: iirds:TopicType
Definition: Class of topic types that contain information in pre-defined form fields.
Description: Examples of forms are service reports, field reports, and user feedback.
IRI: REQUIRED

iirds:Formality

Term Description
URI: http://iirds.tekom.de/iirds#Formality
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Formality
Subclass Of: iirds:InformationSubject
Definition: Parent class for information subjects that describe content related to official or legal documents.
Description: Examples of formality subjects are license terms and warranty conditions.
IRI: REQUIRED

iirds:Fragment

Term Description
URI: http://iirds.tekom.de/iirds#Fragment
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Fragment
Subclass Of: iirds:InformationUnit
Definition: A piece of information within a document or topic.
Description: Sections, tables, lists, paragraphs, and hazard statements are examples of fragments. Fragments assign metadata to parts of topic or document files in an iiRDS package. The parts are identified by a fragment selector.
IRI: REQUIRED

iirds:FragmentSelector

Term Description
URI: http://iirds.tekom.de/iirds#FragmentSelector
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Fragment selector
Subclass Of: iirds:Selector
Definition: Points to a fragment in a physical resource.
IRI: OPTIONAL

iirds:Functionality

Term Description
URI: http://iirds.tekom.de/iirds#Functionality
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Functionality
Subclass Of: iirds:InformationSubject
Definition: Parent class for information subjects that describe content related to specific functionalities of the product.
IRI: REQUIRED

iirds:FunctionalMetadata

Term Description
URI: http://iirds.tekom.de/iirds#FunctionalMetadata
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Functional metadata
Subclass Of: iirds:DocumentationMetadata
Definition: Parent class for metadata supporting advanced content delivery scenarios and content assemblies for specific purposes.
Description: Not intended to be used directly. Use the subclasses instead.

iirds:Identity

Term Description
URI: http://iirds.tekom.de/iirds#Identity
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Identity
Subclass Of: iirds:AdministrativeMetadata
Definition: Complex identifier of an iiRDS domain entity. Each identifier MUST be related to the identity domain within which it is unambiguous.
Description: Complex identifiers MAY be assigned to information objects, information units, product variants, and components. Typically, identities are used to provide IDs from other systems. Examples: serial numbers for components and module IDs from content management systems for topics.
IRI: OPTIONAL
Properties: 1  iirds:identifier property - http://www.w3.org/2000/01/rdf-schema#Literal
  1  iirds:has-identity-domain property - iirds:IdentityDomain

iirds:IdentityDomain

Term Description
URI: http://iirds.tekom.de/iirds#IdentityDomain
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Identity domain
Subclass Of: iirds:AdministrativeMetadata
Definition: Domain of an identifier that is assigned to an iiRDS domain entity.
Description: An identity domain relates to a party, meaning a company or organization. The party is the owner or custodian of the domain.
IRI: REQUIRED
Properties: 0..1  iirds:relates-to-party property - iirds:Party

iirds:iirdsDomainEntity

Term Description
URI: http://iirds.tekom.de/iirds#iirdsDomainEntity
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: iirdsDomainEntity
Definition: An entity of the iiRDS domain
Description: Not intended to be used directly. Use the subclasses instead.
Properties: 0..⃰  iirds:description properties - http://www.w3.org/2000/01/rdf-schema#Literal
  0..⃰  iirds:synonym properties - http://www.w3.org/2000/01/rdf-schema#Literal
  0..⃰  iirds:iirdsRelationConcept properties - iirds:iirdsDomainEntity
  0..⃰  iirds:relates-to-administrative-metadata properties - iirds:AdministrativeMetadata

iirds:InformationObject

Term Description
URI: http://iirds.tekom.de/iirds#InformationObject
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Information object
Subclass Of: iirds:iirdsDomainEntity
Definition: A version-independent and language-independent equivalent to an information unit.
Description: Only used if a version/language-independent equivalent to an information unit is REQUIRED. The versioned information unit references the information object.
IRI: REQUIRED
Properties: 0..⃰  iirds:has-identity properties - iirds:Identity

iirds:InformationSubject

Term Description
URI: http://iirds.tekom.de/iirds#InformationSubject
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Information subject
Subclass Of: iirds:InformationType
Definition: Type of information. Abstract base class of subjects that an information unit covers.
Description: Not intented to be used directly. Use the subclasses instead.
IRI: REQUIRED

iirds:InformationType

Term Description
URI: http://iirds.tekom.de/iirds#InformationType
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Information type
Subclass Of: iirds:iirdsDomainEntity
Definition: Type of information. Abstract base class of document and topic type.
Description: Not intented to be used directly.
IRI: REQUIRED

iirds:InformationUnit

Term Description
URI: http://iirds.tekom.de/iirds#InformationUnit
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Information unit
Subclass Of: iirds:iirdsDomainEntity
Definition: A unit of information. Abstract base class for specific information units.
Description: Not intended to be used directly. Use the subclasses Package, Document, Topic, and Fragment instead.
IRI: REQUIRED
Properties: 0..1  iirds:dateOfCreation property - http://www.w3.org/2001/XMLSchema#dateTimeStamp
  0..1  iirds:dateOfLastModification property - http://www.w3.org/2001/XMLSchema#dateTimeStamp
  0..⃰  iirds:language properties - http://www.w3.org/2000/01/rdf-schema#Literal
  0..1  iirds:revision property - http://www.w3.org/2000/01/rdf-schema#Literal
  0..⃰  iirds:rights properties - http://www.w3.org/2000/01/rdf-schema#Literal
  0..1  iirds:title property - http://www.w3.org/2000/01/rdf-schema#Literal
  0..⃰  iirds:is-applicable-for-document-type properties - iirds:DocumentType
  0..1  iirds:has-abstract property
  0..⃰  iirds:has-content-lifecycle-status properties - iirds:ContentLifeCycleStatus
  0..⃰  iirds:has-identity properties - iirds:Identity
  0..⃰  iirds:has-information-type properties - iirds:InformationType
  0..⃰  iirds:has-planning-time properties - iirds:PlanningTime
  0..⃰  iirds:has-rendition properties - iirds:Rendition
  0..⃰  iirds:has-subject properties - iirds:InformationSubject
  0..⃰  iirds:has-topic-type properties - iirds:TopicType
  0..⃰  iirds:is-part-of-package properties - iirds:Package
  0..1  iirds:is-replacement-of property - iirds:InformationUnit
  0..1  iirds:is-version-of property - iirds:InformationObject
  0..⃰  iirds:relates-to-component properties - iirds:Component
  0..⃰  iirds:relates-to-event properties - iirds:Event
  0..⃰  iirds:relates-to-functional-metadata properties - iirds:FunctionalMetadata
  0..1  iirds:relates-to-information-unit property - iirds:InformationUnit
  0..1  iirds:relates-to-party property - iirds:Party
  0..⃰  iirds:relates-to-product-feature properties - iirds:ProductFeature
  0..⃰  iirds:relates-to-product-lifecycle-phase properties - iirds:ProductLifeCyclePhase
  0..⃰  iirds:relates-to-product-metadata properties - iirds:ProductMetadata
  0..⃰  iirds:relates-to-product-variant properties - iirds:ProductVariant
  0..⃰  iirds:relates-to-qualification properties - iirds:Qualification
  0..⃰  iirds:relates-to-supply properties - iirds:Supply

iirds:Learning

Term Description
URI: http://iirds.tekom.de/iirds#Learning
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Learning
Subclass Of: iirds:TopicType
Definition: Class of topic types for learning. Learning content MAY comprise learning plans, learning objectives, learning content details, summaries, and assessments.
IRI: REQUIRED

iirds:MaintenanceInterval

Term Description
URI: http://iirds.tekom.de/iirds#MaintenanceInterval
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Maintenance interval
Subclass Of: iirds:PlanningTime
Definition: Type of planning time: Fixed time interval for the scheduled maintenance of a technical system or its parts.
Description: Instances have a maintenance frequency and an OPTIONAL maintenance duration.
IRI: OPTIONAL
Properties: 1  iirds:frequency property - http://www.w3.org/2000/01/rdf-schema#Literal

iirds:nil

Term Description
URI: http://iirds.tekom.de/iirds#nil
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: End of Directory node
Subclass Of: iirds:DirectoryNode
Definition: The end in a chain of directory nodes

iirds:Package

Term Description
URI: http://iirds.tekom.de/iirds#Package
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Package
Subclass Of: iirds:InformationUnit
Definition: A set of information in terms of documents and topics with their metadata.
Description: There is exactly one Package instance within an iiRDS package. It holds general metadata on the overall iiRDS package.
IRI: REQUIRED
Properties: 0..1  iirds:formatRestriction property - http://www.w3.org/2000/01/rdf-schema#Literal
  1  iirds:iiRDSVersion property - http://www.w3.org/2000/01/rdf-schema#Literal

iirds:Party

Term Description
URI: http://iirds.tekom.de/iirds#Party
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Party
Subclass Of: iirds:AdministrativeMetadata
Definition: Party related to an iiRDS domain entity.
Description: Detailed information about a party MAY be specified in a vCard.
IRI: REQUIRED
Properties: 0..1  iirds:has-party-role property - iirds:PartyRole
  0..1  iirds:relates-to-vcard property - http://www.w3.org/2006/vcard/ns#Kind

iirds:PartyRole

Term Description
URI: http://iirds.tekom.de/iirds#PartyRole
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Party role
Subclass Of: iirds:AdministrativeMetadata
Definition: Role of a party related to an iiRDS domain entity.
Description: Examples of party roles: manufacturer, author, inspector.
IRI: REQUIRED

iirds:PlanningTime

Term Description
URI: http://iirds.tekom.de/iirds#PlanningTime
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Planning time
Subclass Of: iirds:FunctionalMetadata
Definition: Parent class for different types of planning time that MAY be referenced in technical documentation. Planning times describe periods of time REQUIRED for or resulting from specific working tasks.
Description: Not intended to be used directly. Use the subclasses instead.
IRI: OPTIONAL
Properties: 1  iirds:duration property - http://www.w3.org/2001/XMLSchema#duration

iirds:Process

Term Description
URI: http://iirds.tekom.de/iirds#Process
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Process
Subclass Of: iirds:InformationSubject
Definition: Information subject for process-related information
IRI: REQUIRED

iirds:ProductFeature

Term Description
URI: http://iirds.tekom.de/iirds#ProductFeature
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Product feature
Subclass Of: iirds:ProductMetadata
Definition: Parent class for characteristics and functions of a product or component.
Description: Not intended to be used directly. Use the subclasses instead.
IRI: REQUIRED

iirds:ProductFunction

Term Description
URI: http://iirds.tekom.de/iirds#ProductFunction
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Product function
Subclass Of: iirds:ProductFeature
Definition: A function that a product or component provides or implements.
Description: Examples: starting a phone call, ending a phone call, ringing.
IRI: REQUIRED

iirds:ProductLifeCyclePhase

Term Description
URI: http://iirds.tekom.de/iirds#ProductLifeCyclePhase
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Phase of product lifecycle
Subclass Of: iirds:ProductMetadata
Definition: Parent class for standardized product lifecycle phases that technical documentation MAY refer to.
Description: Not intended to be used directly. Use the subclasses instead.
IRI: REQUIRED

iirds:ProductMetadata

Term Description
URI: http://iirds.tekom.de/iirds#ProductMetadata
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: ProductMetadata
Subclass Of: iirds:DocumentationMetadata
Definition: Parent class for product-related metadata.
Description: Not intended to be used directly. Use the subclasses instead.
IRI: REQUIRED

iirds:ProductProperty

Term Description
URI: http://iirds.tekom.de/iirds#ProductProperty
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Product property
Subclass Of: iirds:ProductFeature
Definition: A characteristic of a product or component.
Description: Examples: dimensions, voltage, power, weight.
IRI: REQUIRED

iirds:ProductVariant

Term Description
URI: http://iirds.tekom.de/iirds#ProductVariant
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Product variant
Subclass Of: iirds:ProductMetadata
Definition: A variation of a product with some specific characteristics or features.
Description: Examples: a specific model in a series or an individually manufactured good.
IRI: REQUIRED
Properties: 0..⃰  iirds:has-identity properties - iirds:Identity
  0..1  iirds:relates-to-party property - iirds:Party

iirds:PuttingToUse

Term Description
URI: http://iirds.tekom.de/iirds#PuttingToUse
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Putting to use
Subclass Of: iirds:ProductLifeCyclePhase
Definition: Parent class for subclasses that describe product lifecycle phases related to putting a product or technical system to use.
Description: Not intended to be used directly. Use the subclasses instead. For lifecycle phases not covered by the iiRDS standard subclasses, define custom subclasses.
IRI: REQUIRED

iirds:Qualification

Term Description
URI: http://iirds.tekom.de/iirds#Qualification
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Qualification
Subclass Of: iirds:FunctionalMetadata
Definition: Parent class for different types of skills and roles REQUIRED for working tasks described in technical documentation.
Description: Not intended to be used directly. Use the subclasses instead.
IRI: REQUIRED

iirds:RangeSelector

Term Description
URI: http://iirds.tekom.de/iirds#RangeSelector
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Range selector
Subclass Of: iirds:Selector
Definition: Points to a range in a physical resource. Has a start and end point.
IRI: OPTIONAL
Properties: 1  iirds:has-end-selector property - iirds:FragmentSelector
  1  iirds:has-start-selector property - iirds:FragmentSelector

iirds:Reference

Term Description
URI: http://iirds.tekom.de/iirds#Reference
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Reference
Subclass Of: iirds:TopicType
Definition: Class of topic types that contain information that supports users as they perform a task, meaning data that is looked up rather than memorized.
IRI: REQUIRED

iirds:Rendition

Term Description
URI: http://iirds.tekom.de/iirds#Rendition
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Rendition
Subclass Of: iirds:iirdsDomainEntity
Definition: Content of an information unit in a specific format
IRI: OPTIONAL
Properties: 1  iirds:format property - http://www.w3.org/2000/01/rdf-schema#Literal
  1  iirds:source property - http://www.w3.org/2000/01/rdf-schema#Literal
  0..⃰  iirds:has-identity properties - iirds:Identity
  0..1  iirds:has-selector property - iirds:Selector

iirds:Role

Term Description
URI: http://iirds.tekom.de/iirds#Role
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Role
Subclass Of: iirds:Qualification
Definition: Docking point for custom roles for users of the technical system and the associated technical information.
Description: Describes a set of connected behaviors, privileges and obligations associated with users (humans, software processes or devices) of a system.
IRI: REQUIRED

iirds:Safety

Term Description
URI: http://iirds.tekom.de/iirds#Safety
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Safety
Subclass Of: iirds:InformationSubject
Definition: Information subject. Abstract base class for safety subjects.
Description: Not intended to be used directly. Use the subclasses instead.
IRI: REQUIRED

iirds:Selector

Term Description
URI: http://iirds.tekom.de/iirds#Selector
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Selector
Subclass Of: iirds:iirdsDomainEntity
Definition: Pointer to a physical resource.
IRI: OPTIONAL

iirds:SkillLevel

Term Description
URI: http://iirds.tekom.de/iirds#SkillLevel
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Skill level
Subclass Of: iirds:Qualification
Definition: Docking point for custom skill levels that the users of the technical system and the associated technical information require.
Description: Describe the levels of ability REQUIRED to carry out a specific task described in the technical documentation.
IRI: REQUIRED

iirds:Supply

Term Description
URI: http://iirds.tekom.de/iirds#Supply
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Supply
Subclass Of: iirds:FunctionalMetadata
Definition: Parent class for different types of supplies REQUIRED for working tasks described in technical documentation.
Description: Not intended to be used directly. Use the subclasses instead.
IRI: REQUIRED

iirds:Task

Term Description
URI: http://iirds.tekom.de/iirds#Task
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Task
Subclass Of: iirds:TopicType
Definition: Class of topic types that contains procedural information for work activities.
Description: Tasks provide instructions and MAY contain information on other aspects, such as requirements that MUST be fulfilled or safety instructions.
IRI: REQUIRED

iirds:TechnicalData

Term Description
URI: http://iirds.tekom.de/iirds#TechnicalData
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Technical data
Subclass Of: iirds:InformationSubject
Definition: Information subject class. Information that describes the technical characteristics of a product or component in sufficient detail for assembly, integration, operation, and maintenance.
Description: Not intended to be used directly. Use instances of this class instead.
IRI: REQUIRED

iirds:TechnicalOverview

Term Description
URI: http://iirds.tekom.de/iirds#TechnicalOverview
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Technical overview
Subclass Of: iirds:InformationSubject
Definition: Parent class for information subjects describing content related to technical plans, diagrams, or the technical architecture of the product.
Description: Examples are circuit diagrams, flow diagrams, software interface overviews, and pneumatic diagrams.
IRI: REQUIRED

iirds:Topic

Term Description
URI: http://iirds.tekom.de/iirds#Topic
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Topic
Subclass Of: iirds:InformationUnit
Definition: A topic is a unit of information covering a single subject.
Description: The resource of a topic is a file in the iiRDS package.
IRI: REQUIRED

iirds:TopicType

Term Description
URI: http://iirds.tekom.de/iirds#TopicType
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Topic type
Subclass Of: iirds:InformationType
Definition: Defines the information type of an iiRDS topic.
Description: Possible types include task, learning, and concept. Information units that represent topics MAY have one or more has-topic-type properties that define the topic's information type. Topics without a has-topic-type property are generic topics, with no specific type.
IRI: REQUIRED

iirds:Troubleshooting

Term Description
URI: http://iirds.tekom.de/iirds#Troubleshooting
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Troubleshooting
Subclass Of: iirds:TopicType
Definition: Class of topic types. Troubleshooting topics contain corrective action information that helps to fix an error or remove a malfunction.
Description: Typical troubleshooting topics contain sections with a description of the system's behavior or symptom, the cause for the error, and a remedy for the error.
IRI: REQUIRED

iirds:Use

Term Description
URI: http://iirds.tekom.de/iirds#Use
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Use
Subclass Of: iirds:ProductLifeCyclePhase
Definition: Parent class for subclasses that describe product lifecycle phases related to using a product or technical system.
Description: Not intended to be used directly. Use the subclasses instead. For lifecycle phases not covered by the iiRDS standard subclasses, define custom subclasses.
IRI: REQUIRED

iirds:WarningMessage

Term Description
URI: http://iirds.tekom.de/iirds#WarningMessage
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Warning message
Subclass Of: iirds:Safety
Definition: Information subject. Description of situations where a potential hazard can occur.
Description: Warning messages usually consist of a hazard alert symbol, a signal word (such as "Danger", "Warning", "Caution", "Notice"), a description of the potential hazard, and hints how to avoid the hazard.
IRI: REQUIRED

iirds:WorkingTime

Term Description
URI: http://iirds.tekom.de/iirds#WorkingTime
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Working time
Subclass Of: iirds:PlanningTime
Definition: Type of planning time: Period of time that is REQUIRED for a specific working task.
IRI: OPTIONAL

A.1.2 Property Definitions

iirds:dateOfCreation

Term Description
URI: http://iirds.tekom.de/iirds#dateOfCreation
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Date of Creation
Subproperty Of: http://purl.org/dc/terms/created, iirds:iirdsAttribute
Has Domain: iirds:InformationUnit
Has Range: http://www.w3.org/2001/XMLSchema#dateTimeStamp
Definition: Date of creation of the information unit

iirds:dateOfEffect

Term Description
URI: http://iirds.tekom.de/iirds#dateOfEffect
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Effective date
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:ContentLifeCycleStatus
Has Range: http://www.w3.org/2001/XMLSchema#dateTimeStamp
Definition: Date and time on which the given content lifecycle status becomes valid.

iirds:dateOfExpiry

Term Description
URI: http://iirds.tekom.de/iirds#dateOfExpiry
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Expiry date
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:ContentLifeCycleStatus
Has Range: http://www.w3.org/2001/XMLSchema#dateTimeStamp
Definition: Date and time on which the given content lifecycle status becomes invalid.

iirds:dateOfLastModification

Term Description
URI: http://iirds.tekom.de/iirds#dateOfLastModification
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Date of last modification
Subproperty Of: iirds:iirdsAttribute
Has Range: http://www.w3.org/2001/XMLSchema#dateTimeStamp
Definition: Specifies the date and time on which the information unit was last changed.
Has Domain: iirds:InformationUnit

iirds:dateOfStatus

Term Description
URI: http://iirds.tekom.de/iirds#dateOfStatus
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Status date
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:ContentLifeCycleStatus
Has Range: http://www.w3.org/2001/XMLSchema#dateTimeStamp
Definition: Specifies the date and time on which content lifecycle status was changed.

iirds:description

Term Description
URI: http://iirds.tekom.de/iirds#description
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Description
Subproperty Of: http://purl.org/dc/terms/description, iirds:iirdsAttribute
Has Domain: iirds:iirdsDomainEntity
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: An account of the resource.
Description: Typically a free-text acount of the resource

iirds:duration

Term Description
URI: http://iirds.tekom.de/iirds#duration
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Duration
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:PlanningTime
Has Range: http://www.w3.org/2001/XMLSchema#duration
Definition: A span of time.

iirds:format

Term Description
URI: http://iirds.tekom.de/iirds#format
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Format
Subproperty Of: http://purl.org/dc/terms/format, iirds:iirdsAttribute
Has Domain: iirds:Rendition
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Media type (MIME type) of the rendition

iirds:formatRestriction

Term Description
URI: http://iirds.tekom.de/iirds#formatRestriction
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Format Restriction
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:Package
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Restriction to the media formats used in the package.
Description: Value "A" means that the package uses a restricted set of media formats ("iiRDS/A").

iirds:frequency

Term Description
URI: http://iirds.tekom.de/iirds#frequency
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Maintenance frequency
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:MaintenanceInterval
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Maintenance frequency

iirds:identifier

Term Description
URI: http://iirds.tekom.de/iirds#identifier
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Identifier
Subproperty Of: http://purl.org/dc/terms/identifier, iirds:iirdsAttribute
Has Domain: iirds:Identity
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: An unambiguous reference to the resource within a given context.
Description: RECOMMENDED best practice is to identify the resource by means of a string conforming to a formal identification system.

iirds:iirdsAttribute

Term Description
URI: http://iirds.tekom.de/iirds#iirdsAttribute
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: iirdsAttribute
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Property type. Abstract base class of all properties with literal values.
Has Domain: iirds:iirdsDomainEntity
Description: Not intended to be used directly. Use the subclasses instead.

iirds:iiRDSVersion

Term Description
URI: http://iirds.tekom.de/iirds#iiRDSVersion
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: iiRDS version
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:Package
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: iiRDS version to which the iiRDS package complies.
Description: Current version is 1.0.

iirds:language

Term Description
URI: http://iirds.tekom.de/iirds#language
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Language
Subproperty Of: http://purl.org/dc/terms/language, iirds:iirdsAttribute
Has Domain: iirds:InformationUnit
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: A language of the resource.
Description: Controlled vocabulary according to RFC 4646.

iirds:purpose

Term Description
URI: http://iirds.tekom.de/iirds#purpose
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Purpose
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:ContentLifeCycleStatus
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Specifies the reason for changing the content lifecycle status.

iirds:revision

Term Description
URI: http://iirds.tekom.de/iirds#revision
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Revision
Subproperty Of: http://purl.org/dc/terms/title, iirds:iirdsAttribute
Has Domain: iirds:InformationUnit
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Version of the information unit.

iirds:rights

Term Description
URI: http://iirds.tekom.de/iirds#rights
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Rights
Subproperty Of: http://purl.org/dc/elements/1.1/rights, iirds:iirdsAttribute
Has Domain: iirds:InformationUnit
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Information about rights held in and over the resource.

iirds:source

Term Description
URI: http://iirds.tekom.de/iirds#source
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Source
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:Rendition
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Relative path to the file containing the content of a rendition.

iirds:statusComment

Term Description
URI: http://iirds.tekom.de/iirds#statusComment
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Status comment
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:ContentLifeCycleStatus
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: Comment describing the status change.

iirds:synonym

Term Description
URI: http://iirds.tekom.de/iirds#synonym
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Synonym
Subproperty Of: iirds:iirdsAttribute
Has Domain: iirds:iirdsDomainEntity
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: A word or phrase that means exactly or nearly the same as another word or phrase in the same language.

iirds:title

Term Description
URI: http://iirds.tekom.de/iirds#title
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: Title
Subproperty Of: http://purl.org/dc/terms/title, iirds:iirdsAttribute
Has Domain: iirds:InformationUnit
Has Range: http://www.w3.org/2000/01/rdf-schema#Literal
Definition: A name given to the information unit.
Description: Typically, a title will be a name by which the information unit is formally known.

A.1.3 Relations

iirds:has-abstract

Term Description
URI: http://iirds.tekom.de/iirds#has-abstract
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has abstract
Subproperty Of: http://purl.org/dc/terms/abstract, iirds:iirdsRelationConcept
Has Domain: iirds:InformationUnit
Definition: Relates to a literal or information unit that provides an abstract/summary for the information unit.

iirds:has-component

Term Description
URI: http://iirds.tekom.de/iirds#has-component
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has component
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:Component
Has Range: iirds:Component
Definition: Relates to a component that is part of another component.

iirds:has-content-lifecycle-status

Term Description
URI: http://iirds.tekom.de/iirds#has-content-lifecycle-status
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to content lifecycle status
Subproperty Of: iirds:relates-to-administrative-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:ContentLifeCycleStatus
Definition: References the content lifecycle status of the information unit.

iirds:has-content-lifecycle-status-value

Term Description
URI: http://iirds.tekom.de/iirds#has-content-lifecycle-status-value
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has status value
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:ContentLifeCycleStatus
Has Range: iirds:ContentLifeCycleStatusValue
Definition: References the content lifecycle status value.

iirds:has-directory-structure-type

Term Description
URI: http://iirds.tekom.de/iirds#has-directory-structure-type
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has directory structure type
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:DirectoryNode
Has Range: iirds:DirectoryNodeType
Definition: The nature of the directory.

iirds:has-document-type

Term Description
URI: http://iirds.tekom.de/iirds#has-document-type
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has document type
Subproperty Of: iirds:has-information-type
Has Domain: iirds:Document
Has Range: iirds:DocumentType
Definition: The type of a document.
Description: Documents have one or more document types. Documents without document types are unspecific documents.

iirds:has-end-selector

Term Description
URI: http://iirds.tekom.de/iirds#has-end-selector
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has end selector
Subproperty Of: iirds:has-selector
Has Domain: iirds:RangeSelector
Has Range: iirds:FragmentSelector
Definition: References the end of a range in a file.
Description: A range selector MUST reference one start and one end selector.

iirds:has-event-code

Term Description
URI: http://iirds.tekom.de/iirds#has-event-code
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has event code
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:Event
Definition: References the code of the event.

iirds:has-event-type

Term Description
URI: http://iirds.tekom.de/iirds#has-event-type
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has event type
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:Event
Definition: References the type of the event.

iirds:has-first-child

Term Description
URI: http://iirds.tekom.de/iirds#has-first-child
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has first child
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:DirectoryNode
Has Range: iirds:DirectoryNode
Definition: References the first directory node on the next sub level.

iirds:has-identity

Term Description
URI: http://iirds.tekom.de/iirds#has-identity
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has complex identifier
Subproperty Of: iirds:relates-to-administrative-metadata
Has Range: iirds:Identity
Definition: References a complex identifier.
Has Domain: iirds:Component, iirds:InformationObject, iirds:InformationUnit, iirds:ProductVariant, iirds:Rendition

iirds:has-identity-domain

Term Description
URI: http://iirds.tekom.de/iirds#has-identity-domain
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has identifier domain
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:Identity
Has Range: iirds:IdentityDomain
Definition: References the domain that an identifier is valid for.

iirds:has-information-type

Term Description
URI: http://iirds.tekom.de/iirds#has-information-type
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has information type
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:InformationUnit
Has Range: iirds:InformationType
Definition: The nature and subject of an information unit.
Description: Not intended to be used directly. Use the child properties instead, such as has-document-type for documents and has-topic-type for topics.

iirds:has-next-sibling

Term Description
URI: http://iirds.tekom.de/iirds#has-next-sibling
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has next sibling
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:DirectoryNode
Has Range: iirds:DirectoryNode
Definition: References the following directory node at the same hierarchy level in a directory structure.

iirds:has-party-role

Term Description
URI: http://iirds.tekom.de/iirds#has-party-role
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has administrative role
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:Party
Has Range: iirds:PartyRole
Definition: References the role that the party has with respect to an entity referencing the party.

iirds:has-planning-time

Term Description
URI: http://iirds.tekom.de/iirds#has-planning-time
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has time
Subproperty Of: iirds:relates-to-functional-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:PlanningTime
Definition: References the planning time that is related to specific tasks or information described in an information unit.

iirds:has-rendition

Term Description
URI: http://iirds.tekom.de/iirds#has-rendition
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has rendition
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:InformationUnit
Has Range: iirds:Rendition
Definition: Relates to a rendition of an information unit, meaning a physical file with content.

iirds:has-selector

Term Description
URI: http://iirds.tekom.de/iirds#has-selector
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has selector
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:Rendition
Has Range: iirds:Selector
Definition: References the selector that is used to relate the information unit to a physical file with content.

iirds:has-start-selector

Term Description
URI: http://iirds.tekom.de/iirds#has-start-selector
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has start selector
Subproperty Of: iirds:has-selector
Has Domain: iirds:RangeSelector
Has Range: iirds:FragmentSelector
Definition: References the start of a range in a file.
Description: A range selector MUST reference one start and one end selector.

iirds:has-subject

Term Description
URI: http://iirds.tekom.de/iirds#has-subject
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has subject
Subproperty Of: http://purl.org/dc/terms/subject, iirds:has-information-type
Has Domain: iirds:InformationUnit
Has Range: iirds:InformationSubject
Definition: References the subject of an information unit.

iirds:has-topic-type

Term Description
URI: http://iirds.tekom.de/iirds#has-topic-type
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: has topic type
Subproperty Of: iirds:has-information-type
Has Domain: iirds:InformationUnit
Has Range: iirds:TopicType
Definition: The nature of an information unit.
Description: Defines the information type of a topic, e.g. task or learning.

iirds:iirdsRelationConcept

Term Description
URI: http://iirds.tekom.de/iirds#iirdsRelationConcept
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: iirdsRelationConcept
Has Domain: iirds:iirdsDomainEntity
Has Range: iirds:iirdsDomainEntity
Definition: Base class for all relations in iiRDS.
Description: Not indented to be used directly.

iirds:is-applicable-for-document-type

Term Description
URI: http://iirds.tekom.de/iirds#is-applicable-for-document-type
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: applicable for document type
Subproperty Of: iirds:has-information-type
Has Domain: iirds:InformationUnit
Has Range: iirds:DocumentType
Definition: Specifies that the information unit is suitable and can be used for specific types of documents.
Description: Example: topics that are suitable for the installation instructions.

iirds:is-part-of-package

Term Description
URI: http://iirds.tekom.de/iirds#is-part-of-package
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: is part of package
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:InformationUnit
Has Range: iirds:Package
Definition: References the package in which the information unit was delivered.

iirds:is-replacement-of

Term Description
URI: http://iirds.tekom.de/iirds#is-replacement-of
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: replaces
Subproperty Of: http://purl.org/dc/terms/replaces, iirds:iirdsRelationConcept
Has Domain: iirds:InformationUnit
Has Range: iirds:InformationUnit
Definition: References the information unit that is replaced by this information unit.

iirds:is-version-of

Term Description
URI: http://iirds.tekom.de/iirds#is-version-of
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: is version of
Subproperty Of: iirds:iirdsRelationConcept, http://purl.org/dc/terms/isVersionOf
Has Domain: iirds:InformationUnit
Has Range: iirds:InformationObject
Definition: Relates an information unit to an information object.
Description: Specifies that the information unit is a version or language variant of the information object.

iirds:relates-to-administrative-metadata

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-administrative-metadata
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to administrative metadata
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:iirdsDomainEntity
Has Range: iirds:AdministrativeMetadata
Definition: Relates an iiRDS entity to administrative metadata.
Description: Not intended to be used directly. Use the subclasses instead.

iirds:relates-to-component

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-component
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to component
Subproperty Of: iirds:relates-to-product-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:Component
Definition: Relates to a component.
Description: That means that the content of the information unit relates to a specific component of the documented product or component.

iirds:relates-to-event

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-event
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to event
Subproperty Of: iirds:relates-to-functional-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:Event
Definition: Relates to an event.
Description: That means that the content of the information unit refers to a specific event that occured in the product/system, e.g. an error.

iirds:relates-to-functional-metadata

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-functional-metadata
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to functional metadata
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:InformationUnit
Has Range: iirds:FunctionalMetadata
Definition: Relates an iiRDS entity to functional metadata.
Description: No intended to be used directly. Use the subclasses instead.

iirds:relates-to-information-unit

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-information-unit
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: references information unit
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:DirectoryNode
Has Range: iirds:InformationUnit
Definition: References an information unit from a directory node.
Description: The referenced information unit is part of the directory.

iirds:relates-to-party

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-party
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to party
Subproperty Of: iirds:relates-to-administrative-metadata
Has Range: iirds:Party
Definition: Relates to a party, e.g. a company or an organization.
Has Domain: iirds:Component, iirds:IdentityDomain, iirds:InformationUnit, iirds:ContentLifeCycleStatus, iirds:ProductVariant

iirds:relates-to-product-feature

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-product-feature
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to product feature
Subproperty Of: iirds:relates-to-product-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:ProductFeature
Definition: Relates to a product feature.
Description: That means that the content of the information unit refers to or describes a specific product feature.

iirds:relates-to-product-lifecycle-phase

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-product-lifecycle-phase
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to phase of the product lifecycle
Subproperty Of: iirds:relates-to-product-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:ProductLifeCyclePhase
Definition: Relates to a product lifecycle phase.
Description: That means that the content of the information unit describes activities or knowledge related to a specific lifecycle phase. Examples are operation and maintenance.

iirds:relates-to-product-metadata

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-product-metadata
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to product metadata
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:InformationUnit
Has Range: iirds:ProductMetadata
Definition: Relates to product metadata.

iirds:relates-to-product-variant

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-product-variant
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to product variant
Subproperty Of: iirds:relates-to-product-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:ProductVariant
Definition: Relates to product variant.
Description: That means that the content of the information unit refers to or describes a specific variant of the product.

iirds:relates-to-qualification

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-qualification
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to qualification
Subproperty Of: iirds:relates-to-functional-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:Qualification
Definition: Relates to a qualification that is REQUIRED for the tasks or activities described in the information unit.

iirds:relates-to-supply

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-supply
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to supply
Subproperty Of: iirds:relates-to-functional-metadata
Has Domain: iirds:InformationUnit
Has Range: iirds:Supply
Definition: Relates to a supply that is REQUIRED for the tasks or activities described in the information unit.

iirds:relates-to-vcard

Term Description
URI: http://iirds.tekom.de/iirds#relates-to-vcard
Type of Term: http://www.w3.org/1999/02/22-rdf-syntax-ns#Property
Label: relates to vCard
Subproperty Of: iirds:iirdsRelationConcept
Has Domain: iirds:Party
Has Range: http://www.w3.org/2006/vcard/ns#Kind
Definition: Relates to a vCard providing detailed information about the party.

A.1.4 Object Definitions

iirds:Acquisition

Term Description
URI: http://iirds.tekom.de/iirds#Acquisition
Type of Term: iirds:DesignAndRealization
Label: Acquisition
Definition: Lifecycle phase of a product during which services, goods, or works are acquired from an external source.

iirds:AdministratorGuide

Term Description
URI: http://iirds.tekom.de/iirds#AdministratorGuide
Type of Term: iirds:DocumentType
Label: Administrator guide
Definition: Type of document. Contains instructions for the administration of a technical system.

iirds:ApplicableStandards

Term Description
URI: http://iirds.tekom.de/iirds#ApplicableStandards
Type of Term: iirds:Conformity
Label: Applicable standard
Definition: Information subject related to conformity. Describes content related to standards that a product needs to fulfill.
Description: Examples: machinery directive, ATEX directive

iirds:Approved

Term Description
URI: http://iirds.tekom.de/iirds#Approved
Type of Term: iirds:ContentLifeCycleStatusValue
Label: Approved
Definition: Content lifecycle status value; indicates that the content has been approved.

iirds:AssemblyInstructions

Term Description
URI: http://iirds.tekom.de/iirds#AssemblyInstructions
Type of Term: iirds:DocumentType
Label: Assembly instructions
Definition: Type of document. Contains instructions enabling the operator to assemble a physical product so that it fulfills its intended use and does not endanger the health and safety of persons.

iirds:Author

Term Description
URI: http://iirds.tekom.de/iirds#Author
Type of Term: iirds:PartyRole
Label: Author
Definition: Instance of the PartyRole class describing the role of an actor related to an iiRDS domain entity.
Description: An author is the individual or the organization from which the referenced iiRDS domain entity originates.

iirds:BillOfMaterials

Term Description
URI: http://iirds.tekom.de/iirds#BillOfMaterials
Type of Term: iirds:DocumentType
Label: Bill of materials
Definition: List of sub-components, sub-modules and parts of a product. The materials are listed with their identity and characteristics so that they can be identified within the product and procured.
Description: Type of document (VDI 2770). Examples are part list with part number, part description, order number, and references to other documents.

iirds:Caution

Term Description
URI: http://iirds.tekom.de/iirds#Caution
Type of Term: iirds:WarningMessage
Label: Caution
Definition: Describes a hazardous situation which, if not avoided, could result in minor or moderate injury.
Description: See ANSI Z535.5

iirds:CEDeclarationOfConformity

Term Description
URI: http://iirds.tekom.de/iirds#CEDeclarationOfConformity
Type of Term: iirds:DocumentType
Label: CE declaration of conformity
Definition: Type of document. Created as a result of a procedure whereby the manufacture or authorized representative "ensures and declares" that the products concerned satisfy the requirements of the directives that apply to them.

iirds:Certificate

Term Description
URI: http://iirds.tekom.de/iirds#Certificate
Type of Term: iirds:DocumentType
Label: Certificate
Definition: Document of legal nature that contains and certifies product information, quality, and characteristics. Usually acknowledged with a signature.
Description: Type of document (VDI 2770). Examples are ATEX certificates, acceptance reports, and material certificates.

iirds:Configuration

Term Description
URI: http://iirds.tekom.de/iirds#Configuration
Type of Term: iirds:PuttingToUse
Label: Configuration
Definition: Lifecycle phase of a product describing activities related to configuring the settings of a technical system before use.

iirds:ContactInformation

Term Description
URI: http://iirds.tekom.de/iirds#ContactInformation
Type of Term: iirds:Formality
Label: Contact information
Definition: Information subject. Contact information of the supplier.
Description: Contact information such as addresses, phone numbers, URLs.

iirds:ContractualDocument

Term Description
URI: http://iirds.tekom.de/iirds#ContractualDocument
Type of Term: iirds:DocumentType
Label: Contractual document
Definition: Document that is part of or accompanies a contract.
Description: Type of document (VDI 2770). Contractual documents include, among others, contracts, acceptance reports, and service conditions.

iirds:Contributor

Term Description
URI: http://iirds.tekom.de/iirds#Contributor
Type of Term: iirds:PartyRole
Label: Contributor
Definition: Instance of the PartyRole class describing the role of an actor related to an iiRDS domain entity.
Description: A contributor is an individual or an organization that participated in the generation/change of the referenced iiRDS domain entity.

iirds:Creator

Term Description
URI: http://iirds.tekom.de/iirds#Creator
Type of Term: iirds:PartyRole
Label: Creator
Definition: Instance of the PartyRole class describing the role of an actor related to an iiRDS domain entity.
Description: A creator is the individual or the organization that created the referenced iiRDS domain entity.

iirds:Customer

Term Description
URI: http://iirds.tekom.de/iirds#Customer
Type of Term: iirds:PartyRole
Label: Customer
Definition: Instance of the PartyRole class describing the role of an actor related to an iiRDS domain entity.
Description: A customer is an individual or an organization that purchased or consumes the referenced iiRDS domain entity.

iirds:Danger

Term Description
URI: http://iirds.tekom.de/iirds#Danger
Type of Term: iirds:WarningMessage
Label: Danger
Definition: Describes a hazardous situation which, if not avoided, will result in death or serious injury.
Description: See ANSI Z535.5

iirds:DeclarationOfConformity

Term Description
URI: http://iirds.tekom.de/iirds#DeclarationOfConformity
Type of Term: iirds:Conformity
Label: Declaration of conformity
Definition: Information subject. Specifies that the information unit deals with the EU Declaration of Conformity for CE marking.
Description: The Declaration of Conformity states that the product complies with the essential requirements of the relevant standards.

iirds:Decommissioning

Term Description
URI: http://iirds.tekom.de/iirds#Decommissioning
Type of Term: iirds:Use
Label: Decommissioning
Definition: Lifecycle phase of a product describing the shut-down and transfer into a safe state.

iirds:Deleted

Term Description
URI: http://iirds.tekom.de/iirds#Deleted
Type of Term: iirds:ContentLifeCycleStatusValue
Label: Deleted
Definition: Content lifecycle status value; indicates that the content has been removed.

iirds:Design

Term Description
URI: http://iirds.tekom.de/iirds#Design
Type of Term: iirds:DesignAndRealization
Label: Design
Definition: Lifecycle phase of product design.

iirds:Development

Term Description
URI: http://iirds.tekom.de/iirds#Development
Type of Term: iirds:DesignAndRealization
Label: Development
Definition: Lifecycle phase of a product progressing from detailed design to prototyping through pilot release to full product launch.

iirds:Diagnostics

Term Description
URI: http://iirds.tekom.de/iirds#Diagnostics
Type of Term: iirds:Use
Label: Diagnostics
Definition: Lifecycle phase of a product containing procedures for locating errors.

iirds:Disposal

Term Description
URI: http://iirds.tekom.de/iirds#Disposal
Type of Term: iirds:AfterUse
Label: Disposal
Definition: Lifecycle phase of a product describing the elimination of components, mounted parts and lubricant considering the country-specific current law.

iirds:ElectronicIdentificationPlate

Term Description
URI: http://iirds.tekom.de/iirds#ElectronicIdentificationPlate
Type of Term: iirds:DocumentType
Label: Electronic identification plate
Definition: Electronically readable label on a machine or component that provides information on the identity of the manufacturer and the product, as well as on the technical characteristics of the product.
Description: Type of document (VDI 2770)

iirds:EmergencyOperation

Term Description
URI: http://iirds.tekom.de/iirds#EmergencyOperation
Type of Term: iirds:Use
Label: Emergency operation
Definition: Product lifecycle phase of a technical system in which the system's functionality is reduced to a minimum due to an error or emergency situation.

iirds:Fault

Term Description
URI: http://iirds.tekom.de/iirds#Fault
Type of Term: iirds:Use
Label: Fault
Definition: Product lifecycle phase of a technical system in which the intended use and operation of a technical system or software is interrupted due to an error or malfunction.

iirds:ForeseeableMisuse

Term Description
URI: http://iirds.tekom.de/iirds#ForeseeableMisuse
Type of Term: iirds:Safety
Label: Foreseeable misuse
Definition: Information subject. Foreseeable misuse of a product.
Description: Use of a product in a manner not intended by the producer or supplier but which MAY result from foreseeable human behavior. See EN 82079-1

iirds:GenericAfterUse

Term Description
URI: http://iirds.tekom.de/iirds#GenericAfterUse
Type of Term: iirds:AfterUse
Label: After use
Definition: Generic instance of the AfterUse class.
Description: The AfterUse class is a parent class for product lifecycle phases that occur after the active use of the product.

iirds:GenericCollection

Term Description
URI: http://iirds.tekom.de/iirds#GenericCollection
Type of Term: iirds:Collection
Label: Collection
Definition: Information subject. Indicates that the content represents a collection of information assembled from different information units.

iirds:GenericConcept

Term Description
URI: http://iirds.tekom.de/iirds#GenericConcept
Type of Term: iirds:Concept
Label: Concept
Definition: Topic type that provides background that helps readers understand essential information about a product, interface, or task.
Description: Conceptual information helps users to map their existing knowledge to tasks and other essential information about a product or system.

iirds:GenericConformity

Term Description
URI: http://iirds.tekom.de/iirds#GenericConformity
Type of Term: iirds:Conformity
Label: Conformity
Definition: Generic instance of the Conformity class.
Description: The Conformity class is a parent class for information subjects that describe content related to applicable standards or the conformity of the product.

iirds:GenericDesignAndRealization

Term Description
URI: http://iirds.tekom.de/iirds#GenericDesignAndRealization
Type of Term: iirds:DesignAndRealization
Label: Design and realization
Definition: Generic instance of the DesignAndRealization class.
Description: The DesignAndRealization class is a parent class for product lifecycle phases related to the design, construction, and realization of a product.

iirds:GenericDownTime

Term Description
URI: http://iirds.tekom.de/iirds#GenericDownTime
Type of Term: iirds:DownTime
Label: Down time
Definition: Generic instance of the DownTime class.
Description: The DownTime class is a parent class for time periods during which an equipment or machine is not functional or cannot work.

iirds:GenericEvent

Term Description
URI: http://iirds.tekom.de/iirds#GenericEvent
Type of Term: iirds:Event
Label: Event
Definition: Generic instance of the Event class.
Description: The Event class describes events that happen in the technical system. Examples are errors, malfunctions, and warnings.

iirds:GenericForm

Term Description
URI: http://iirds.tekom.de/iirds#GenericForm
Type of Term: iirds:Form
Label: Form
Definition: Generic instance of the Form class.
Description: The Form class describes topics that contain information in pre-defined form fields. Examples of forms are service reports, field reports, and user feedback.

iirds:GenericFormality

Term Description
URI: http://iirds.tekom.de/iirds#GenericFormality
Type of Term: iirds:Formality
Label: Formality
Definition: Generic instance of the Formality class.
Description: The Formality class is the parent class for information subjects that describe content related to official or legal documents.

iirds:GenericFunctionality

Term Description
URI: http://iirds.tekom.de/iirds#GenericFunctionality
Type of Term: iirds:Functionality
Label: Functionality
Definition: Generic instance of the Functionality class.
Description: The Functionality class is the parent class for information subjects that describe content related to specific functionalities of the product.

iirds:GenericLearning

Term Description
URI: http://iirds.tekom.de/iirds#GenericLearning
Type of Term: iirds:Learning
Label: Learning
Definition: Topic type that provides learning content.
Description: Learning content MAY comprise learning plans, learning objectives, learning content details, summaries, and assessments.

iirds:GenericMaintenanceInterval

Term Description
URI: http://iirds.tekom.de/iirds#GenericMaintenanceInterval
Type of Term: iirds:MaintenanceInterval
Label: Maintenance interval
Definition: Generic instance of the MaintenanceInterval class.
Description: The MaintenanceInterval class describes time intervals and durations for the scheduled maintenance of a technical system or its parts.

iirds:GenericPlanningTime

Term Description
URI: http://iirds.tekom.de/iirds#GenericPlanningTime
Type of Term: iirds:PlanningTime
Label: Planning time
Definition: Generic instance of the PlanningTime class.
Description: The PlanningTime class describes different types of planning times that MAY be referenced in technical documentation, for example time REQUIRED for or resulting from specific working tasks.

iirds:GenericProcess

Term Description
URI: http://iirds.tekom.de/iirds#GenericProcess
Type of Term: iirds:Process
Label: Process
Definition: Generic instance of the Process class.
Description: The Process class contains information subject for process-related information.

iirds:GenericProductFeature

Term Description
URI: http://iirds.tekom.de/iirds#GenericProductFeature
Type of Term: iirds:ProductFeature
Label: Product feature
Definition: Generic instance of the ProductFeature class.
Description: The ProductFeature class is a parent class for characteristics and functions of a product or component.

iirds:GenericProductFunction

Term Description
URI: http://iirds.tekom.de/iirds#GenericProductFunction
Type of Term: iirds:ProductFunction
Label: Product function
Definition: Generic instance of the ProductFunction class.
Description: The ProductFunction class describes a function that a product or component provides or implements.

iirds:GenericProductProperty

Term Description
URI: http://iirds.tekom.de/iirds#GenericProductProperty
Type of Term: iirds:ProductProperty
Label: Product property
Definition: Generic instance of the ProductProperty class.
Description: The ProductProperty class describes a characteristic of a product or component.

iirds:GenericPuttingToUse

Term Description
URI: http://iirds.tekom.de/iirds#GenericPuttingToUse
Type of Term: iirds:PuttingToUse
Label: Putting to use
Definition: Generic instance of the GenericPuttingToUse class.
Description: The PuttingToUse class is a parent class for the product lifecycle phases related to putting a product or technical system to use.

iirds:GenericReference

Term Description
URI: http://iirds.tekom.de/iirds#GenericReference
Type of Term: iirds:Reference
Label: Reference
Definition: Generic instance of the Reference class.
Description: The Reference class describes a topic type containing information that supports users as they perform a task, meaning data that is looked up rather than memorized. Examples are parameter lists, tables with technical data, UI control overviews, and parts lists.

iirds:GenericRole

Term Description
URI: http://iirds.tekom.de/iirds#GenericRole
Type of Term: iirds:Role
Label: Role
Definition: Generic instance of the Role class.
Description: The Role class describes roles for users of the technical system and the associated technical information.

iirds:GenericSafety

Term Description
URI: http://iirds.tekom.de/iirds#GenericSafety
Type of Term: iirds:Safety
Label: Safety
Definition: Generic instance of the Safety class.
Description: The Safety class contains information subjects related to safety.

iirds:GenericSkillLevel

Term Description
URI: http://iirds.tekom.de/iirds#GenericSkillLevel
Type of Term: iirds:SkillLevel
Label: Skill level
Definition: Generic instance of the SkillLevel class.
Description: The SkillLevel class describes custom skill levels that the users of the technical system and the associated technical information require.

iirds:GenericSupply

Term Description
URI: http://iirds.tekom.de/iirds#GenericSupply
Type of Term: iirds:Supply
Label: Generic supply
Definition: Generic instance of the Supply class.
Description: The Supply class is a parent class for supplies that are REQUIRED for working tasks described in technical documentation.

iirds:GenericTask

Term Description
URI: http://iirds.tekom.de/iirds#GenericTask
Type of Term: iirds:Task
Label: Task
Definition: Topic type that contains procedural information for work activities.
Description: Tasks provide instructions and MAY contain information on other aspects, such as requirements that MUST be fulfilled or safety instructions.

iirds:GenericTechnicalData

Term Description
URI: http://iirds.tekom.de/iirds#GenericTechnicalData
Type of Term: iirds:TechnicalData
Label: Technical data
Definition: Generic instance of the TechnicalData class.
Description: Information that describes the technical characteristics of a product or component.

iirds:GenericTechnicalOverview

Term Description
URI: http://iirds.tekom.de/iirds#GenericTechnicalOverview
Type of Term: iirds:TechnicalOverview
Label: Technical overview
Definition: Generic instance of the TechnicalOverview class.
Description: The TechnicalOverview class is a parent class for information subjects describing contents related to technical plans, diagrams, or the technical architecture of the product.

iirds:GenericTroubleshooting

Term Description
URI: http://iirds.tekom.de/iirds#GenericTroubleshooting
Type of Term: iirds:Troubleshooting
Label: Troubleshooting
Definition: Topic type that contains corrective action information that helps to fix an error or remove a malfunction.
Description: Troubleshooting information MAY comprise a description of the symptoms, the cause of the error, and a remedy for the error.

iirds:GenericUse

Term Description
URI: http://iirds.tekom.de/iirds#GenericUse
Type of Term: iirds:Use
Label: Use
Definition: Generic instance of the Use class.
Description: The Use class is a parent class for product lifecycle phases related to using a product or technical system.

iirds:GenericWarningMessage

Term Description
URI: http://iirds.tekom.de/iirds#GenericWarningMessage
Type of Term: iirds:WarningMessage
Label: Warning message
Definition: Warning or notice with unknown severity.
Description: If possible, use Danger, Warning, Caution, or Notice instead.

iirds:GenericWorkingTime

Term Description
URI: http://iirds.tekom.de/iirds#GenericWorkingTime
Type of Term: iirds:WorkingTime
Label: Generic working time
Definition: Generic instance of the WorkingTime class.
Description: The WorkingTime class is a parent class for periods of time REQUIRED for a specific working task.

iirds:IdentificationDocument

Term Description
URI: http://iirds.tekom.de/iirds#IdentificationDocument
Type of Term: iirds:DocumentType
Label: Identification document
Definition: Type of document.
Description: Identifies an object and provides descriptive or classifying information.

iirds:Index

Term Description
URI: http://iirds.tekom.de/iirds#Index
Type of Term: iirds:DirectoryNodeType
Label: Index
Definition: Index directory type

iirds:InPreparation

Term Description
URI: http://iirds.tekom.de/iirds#InPreparation
Type of Term: iirds:ContentLifeCycleStatusValue
Label: In preparation
Definition: Content lifecycle status value; indicates that the content is not finished yet and is still being edited.

iirds:InReview

Term Description
URI: http://iirds.tekom.de/iirds#InReview
Type of Term: iirds:ContentLifeCycleStatusValue
Label: In review
Definition: Content lifecycle status value; indicates that the content is being reviewed.

iirds:Inspector

Term Description
URI: http://iirds.tekom.de/iirds#Inspector
Type of Term: iirds:PartyRole
Label: Inspector
Definition: Instance of the PartyRole class describing the role of an actor related to an iiRDS domain entity.
Description: An inspector is an individual or an organization that supervises or checks the referenced iiRDS domain entity and makes reports.

iirds:Installation

Term Description
URI: http://iirds.tekom.de/iirds#Installation
Type of Term: iirds:PuttingToUse
Label: Installation
Definition: Lifecycle phase of a product containing procedures for installing and setting up a software or IT system.

iirds:InstallationInstructions

Term Description
URI: http://iirds.tekom.de/iirds#InstallationInstructions
Type of Term: iirds:DocumentType
Label: Installation instructions
Definition: Type of document. Contains instructions enabling the operator or administrator to assemble or install a physical product or software so that it fulfills its intended use.
Description: For physical products: instructions enabling the operator to assemble and electrically connect a physical product so that it fulfills its intended use and does not endanger the health and safety of persons. For IT products: Instructions enabling the administrator to set up and potentially configure a program or new version on a computer so that does not endanger data security.

iirds:IntendedUse

Term Description
URI: http://iirds.tekom.de/iirds#IntendedUse
Type of Term: iirds:Safety
Label: Intended use
Definition: Information subject: Legal concept outlining the field of application specified in matters of design and construction of the machinery which is described in the operating instructions/technical documentation, including considerations of the reasonable foreseeable use and potential misuse.

iirds:LegalInformation

Term Description
URI: http://iirds.tekom.de/iirds#LegalInformation
Type of Term: iirds:Formality
Label: Legal information
Definition: Information subject for legal information.

iirds:LicenceTerm

Term Description
URI: http://iirds.tekom.de/iirds#LicenceTerm
Type of Term: iirds:Formality
Label: License terms
Definition: Information subject describing licensing conditions.

iirds:ListOfFigures

Term Description
URI: http://iirds.tekom.de/iirds#ListOfFigures
Type of Term: iirds:DirectoryNodeType
Label: List of figures
Synonym: LOF
Definition: List of figures
Description: Type of directory

iirds:ListOfListings

Term Description
URI: http://iirds.tekom.de/iirds#ListOfListings
Type of Term: iirds:DirectoryNodeType
Label: List of listings
Synonym: LOL
Definition: Code listing
Description: Type of directory

iirds:ListOfTables

Term Description
URI: http://iirds.tekom.de/iirds#ListOfTables
Type of Term: iirds:DirectoryNodeType
Label: List of tables
Synonym: LOT
Definition: List of tables
Description: Type of directory

iirds:Maintenance

Term Description
URI: http://iirds.tekom.de/iirds#Maintenance
Type of Term: iirds:Use
Label: Maintenance
Definition: Lifecycle phase of a product that describes activities for moving or conveying the product from one place to another.

iirds:MaintenanceInstructions

Term Description
URI: http://iirds.tekom.de/iirds#MaintenanceInstructions
Type of Term: iirds:DocumentType
Label: Maintenance instructions
Definition: Type of document. Contains instructions for retaining or restoring a piece of equipment, machine, or system to the specified operable condition.

iirds:Manufacturer

Term Description
URI: http://iirds.tekom.de/iirds#Manufacturer
Type of Term: iirds:PartyRole
Label: Manufacturer
Definition: Instance of the PartyRole class describing the role of an actor related to an iiRDS domain entity.
Description: The manufacturer is the individual or the organization that produces the referenced iiRDS domain entity.

iirds:ManufacturerInformation

Term Description
URI: http://iirds.tekom.de/iirds#ManufacturerInformation
Type of Term: iirds:Formality
Label: Manufacturer information
Definition: Information subject. Information about the manufacturer of a product like name and address.

iirds:Notice

Term Description
URI: http://iirds.tekom.de/iirds#Notice
Type of Term: iirds:WarningMessage
Label: Notice
Definition: Information considered important but not related to personal injury.
Description: See ANSI Z535.5

iirds:OperatingElement

Term Description
URI: http://iirds.tekom.de/iirds#OperatingElement
Type of Term: iirds:TechnicalOverview
Label: Control element
Definition: Information subject. Describes a device that a person can use to influence a machine or plant.

iirds:OperatingInstructions

Term Description
URI: http://iirds.tekom.de/iirds#OperatingInstructions
Type of Term: iirds:DocumentType
Label: Operating instructions
Definition: Type of document. Contains instructions for operation and use of a technical system.
Description: The instructions in this document type enable the user to operate a device, machine, or software considering the reference use as well as the safety and health regulations for the product.

iirds:Operation

Term Description
URI: http://iirds.tekom.de/iirds#Operation
Type of Term: iirds:Use
Label: Operation
Definition: Lifecycle phase of a product in which a technical product or system is actively used and operated.

iirds:PartsCatalog

Term Description
URI: http://iirds.tekom.de/iirds#PartsCatalog
Type of Term: iirds:DocumentType
Label: Parts catalog
Definition: Type of document. Contains listings of product names and their part numbers and graphics which are necessary for the aftersales service, but do not include prices or availabilities.

iirds:PerformedBy

Term Description
URI: http://iirds.tekom.de/iirds#PerformedBy
Type of Term: iirds:PartyRole
Label: Performed by
Definition: Instance of the PartyRole class describing the role of an actor related to an iiRDS domain entity.
Description: Describes the actor that is involved in changing the content lifecycle status.

iirds:Plan

Term Description
URI: http://iirds.tekom.de/iirds#Plan
Type of Term: iirds:DocumentType
Label: Plan
Definition: Describes documents containing technical plans for a component or machine.
Description: Type of document (VDI 2770).

iirds:ProductIdentification

Term Description
URI: http://iirds.tekom.de/iirds#ProductIdentification
Type of Term: iirds:Formality
Label: Product identification
Definition: Information subject: Describes a name plate or similar that identifies the product.

iirds:Production

Term Description
URI: http://iirds.tekom.de/iirds#Production
Type of Term: iirds:DesignAndRealization
Label: Production
Definition: Lifecycle phase of a product in which the product is manufactured.

iirds:ProductName

Term Description
URI: http://iirds.tekom.de/iirds#ProductName
Type of Term: iirds:Formality
Label: Product name
Definition: Information subject. Contains the name of the product.

iirds:QuickGuide

Term Description
URI: http://iirds.tekom.de/iirds#QuickGuide
Type of Term: iirds:DocumentType
Label: Quick reference guide
Definition: Type of document. Describes a short document that contains selected instructions for a specific user group or purpose.

iirds:Released

Term Description
URI: http://iirds.tekom.de/iirds#Released
Type of Term: iirds:ContentLifeCycleStatusValue
Label: Released
Definition: Content lifecycle status value; indicates that the content has been released.

iirds:Repair

Term Description
URI: http://iirds.tekom.de/iirds#Repair
Type of Term: iirds:Use
Label: Repair
Definition: Lifecycle phase of a product that describes activities for restoring the product to a working and sound condition after damage or wear and tear.

iirds:RepairInstructions

Term Description
URI: http://iirds.tekom.de/iirds#RepairInstructions
Type of Term: iirds:DocumentType
Label: Repair instructions
Definition: Type of document. Contains instructions for restoring a product to a working condition.
Description: The instructions in this document type enable the user to repair a device, machine, or system considering the reference use as well as the safety and health regulations for the product.

iirds:RequirementsAnalysis

Term Description
URI: http://iirds.tekom.de/iirds#RequirementsAnalysis
Type of Term: iirds:DesignAndRealization
Label: Requirement analysis
Definition: Lifecycle phase of a product belonging to the product design; comprises the analysis and definition of requirements for the future product.

iirds:RestrictionOnUse

Term Description
URI: http://iirds.tekom.de/iirds#RestrictionOnUse
Type of Term: iirds:Safety
Label: Restriction on use
Definition: Information subjects. Specifies that there are restrictions regarding the use of the product.

iirds:Reviewed

Term Description
URI: http://iirds.tekom.de/iirds#Reviewed
Type of Term: iirds:ContentLifeCycleStatusValue
Label: Reviewed
Definition: Content lifecycle status value; indicates that the content has been reviewed.

iirds:RiskAssessment

Term Description
URI: http://iirds.tekom.de/iirds#RiskAssessment
Type of Term: iirds:Conformity
Label: Risk assessment
Definition: Information subject related to conformity. Specifies that the information unit contains information on the risk assessment made within the safety engineering of the product.
Description: A risk assessment determines the risks and hazards to life, environment, or machine functioning including a quantitative and qualitative estimate.

iirds:SafetyInstruction

Term Description
URI: http://iirds.tekom.de/iirds#SafetyInstruction
Type of Term: iirds:Safety
Label: Safety instruction
Definition: Information subject. Safety instructions explain to the user how to handle a product in a safe way.

iirds:SafetyInstructions

Term Description
URI: http://iirds.tekom.de/iirds#SafetyInstructions
Type of Term: iirds:DocumentType
Label: Safety instructions
Definition: Contains general safety-related information provided by the manufacturer that MUST be considered during assembly, operation, maintenance, repair, and disassembly of the product. Safety information related to individual tasks is provided in the tasks.
Description: Type of document (VDI 2770). Examples are documents about the intended use of the product, protection/safety measures, safety equipment, and explosion prevention.

iirds:SalesCatalog

Term Description
URI: http://iirds.tekom.de/iirds#SalesCatalog
Type of Term: iirds:DocumentType
Label: Sales catalog
Definition: Type of document. Contains listings of available products of a producing company with consumers as the target group.

iirds:ScopeOfDelivery

Term Description
URI: http://iirds.tekom.de/iirds#ScopeOfDelivery
Type of Term: iirds:Formality
Label: Scope of delivery
Definition: Information subject. Specifies the scope of the delivery.

iirds:Specification

Term Description
URI: http://iirds.tekom.de/iirds#Specification
Type of Term: iirds:DocumentType
Label: Specification
Definition: Type of document. Contains requirements and/or statements describing properties and qualities of a product to be built or manufactured.

iirds:Supplier

Term Description
URI: http://iirds.tekom.de/iirds#Supplier
Type of Term: iirds:PartyRole
Label: Supplier
Definition: Instance of the PartyRole class describing the role of an actor related to an iiRDS domain entity.
Description: Describes the individual or the organization that provides the referenced iiRDS domain entity, e.g. a component.

iirds:Symbol

Term Description
URI: http://iirds.tekom.de/iirds#Symbol
Type of Term: iirds:TechnicalOverview
Label: Symbol
Definition: Information subject. Contains a list and explanation of symbols used in the documentation.

iirds:TableOfContents

Term Description
URI: http://iirds.tekom.de/iirds#TableOfContents
Type of Term: iirds:DirectoryNodeType
Label: Table of contents
Synonym: TOC
Definition: Table of contents
Description: Directory type

iirds:TechnicalDrawingDiagram

Term Description
URI: http://iirds.tekom.de/iirds#TechnicalDrawingDiagram
Type of Term: iirds:DocumentType
Label: Technical drawing/diagram
Definition: Type of document. Examples are flow diagrams and circuit diagrams.
Description: A technical drawing or diagram.

iirds:TechnicalReport

Term Description
URI: http://iirds.tekom.de/iirds#TechnicalReport
Type of Term: iirds:Conformity
Label: Technical report
Definition: Information subject related to conformity. Specifies that the information unit represents a report regarding the activities or working tasks related to the product.

iirds:TransportInstructions

Term Description
URI: http://iirds.tekom.de/iirds#TransportInstructions
Type of Term: iirds:DocumentType
Label: Transport instructions
Definition: Type of document. Contains instructions for transporting the product or its components from one place to another.

iirds:Warning

Term Description
URI: http://iirds.tekom.de/iirds#Warning
Type of Term: iirds:WarningMessage
Label: Warning
Definition: Describes a hazardous situation which, if not avoided, could result in death or serious injury.
Description: See ANSI Z535.5

iirds:WarrantyConditions

Term Description
URI: http://iirds.tekom.de/iirds#WarrantyConditions
Type of Term: iirds:Formality
Label: Warranty conditions
Definition: Information subject. Contains the warranty conditions.

iirds:Withdrawn

Term Description
URI: http://iirds.tekom.de/iirds#Withdrawn
Type of Term: iirds:ContentLifeCycleStatusValue
Label: Withdrawn
Definition: Content lifecycle status value; indicates that the content has been withdrawn and is no longer valid.

A.2 Machinery Domain

A.2.1 Class Definitions

iirdsMch:ConsumableSupply

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#ConsumableSupply
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Consumable supply
Subclass Of: iirdsMch:iirdsMachineryDomainEntity, iirds:Supply
Definition: Type of supply: Goods or material that is consumed, meaning dissipated or spent, in the lifecycle of a technical system. Examples are batteries, sanding discs, and magnets.
Description: Consumable supplies MAY be referenced in the description of working tasks in technical documentation.
IRI: REQUIRED

iirdsMch:HardwareTool

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#HardwareTool
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Hardware tool
Subclass Of: iirds:Supply
Definition: Type of supply: A device or implement, used to carry out a particular function or a working task.
Description: Hardware tools MAY be referenced in the description of working tasks in technical documentation.
IRI: REQUIRED

iirdsMch:iirdsMachineryDomainEntity

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#iirdsMachineryDomainEntity
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: iirdsMachineryDomainEntity
Subclass Of: iirds:iirdsDomainEntity
Definition: Entity of the machinery domain

iirdsMch:Lubricant

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Lubricant
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Lubricant
Subclass Of: iirdsMch:iirdsMachineryDomainEntity, iirds:Supply
Definition: Type of supply: Lubricant, meaning a substance used for lubricating an engine or component, such as oil or grease.
Description: Lubricants MAY be referenced in the description of working tasks in technical documentation.
IRI: REQUIRED

iirdsMch:OperatingSupply

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#OperatingSupply
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Operating supply
Subclass Of: iirdsMch:iirdsMachineryDomainEntity, iirds:Supply
Definition: Type of supply: Physical items REQUIRED for the running of a manufacturing production or service facility.
Description: Operating supplies MAY be referenced in the description of working tasks in technical documentation.
IRI: REQUIRED

iirdsMch:SetupTime

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#SetupTime
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Setup time
Subclass Of: iirds:PlanningTime, iirdsMch:iirdsMachineryDomainEntity
Definition: Type of planning time: Period of time REQUIRED to prepare a technical system for a specific function or job.
IRI: OPTIONAL

iirdsMch:SparePart

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#SparePart
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: Spare part
Subclass Of: iirdsMch:iirdsMachineryDomainEntity, iirds:Supply
Definition: Type of supply: A spare part is an interchangeable part that is kept in an inventory and used for the repair or replacement of failed units of a technical system.
Description: Spare parts MAY be referenced in the description of working tasks in technical documentation.
IRI: REQUIRED

A.2.2 Property Definitions

n/a

A.2.3 Relations

n/a

A.2.4 Object Definitions

iirdsMch:Assembly

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Assembly
Type of Term: iirds:PuttingToUse
Label: Assembly
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Lifecycle phase of a product in which the product or its components are assembled for use.

iirdsMch:CircuitDiagram

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#CircuitDiagram
Type of Term: iirds:TechnicalOverview
Label: Circuit diagram
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Typical representation of an electrical circuit in (electrical) technology.

iirdsMch:Cleaning

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Cleaning
Type of Term: iirds:Use
Label: Cleaning
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Product lifecycle phase of a technical system in which unwanted substances, such as dirt, are removed from the system.

iirdsMch:CloseDown

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#CloseDown
Type of Term: iirds:AfterUse
Label: Close down
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Lifecycle phase of a product in which a plant, technical system, or facility is shut down permanently.

iirdsMch:Commissioning

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Commissioning
Type of Term: iirds:Use
Label: Commissioning
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Product lifecycle phase containing activities related to transferring a product into active use and instructing personnel on the use. Activities include final inspection tests and handover of documentation, among others (DIN EN 82079-1).

iirdsMch:Construction

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Construction
Type of Term: iirds:DesignAndRealization
Label: Construction
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Product lifecycle phase containing activities for constructing a technical system.
Description: Construction is a design phase which prepares the product for mass manufacturing.

iirdsMch:Disassembly

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Disassembly
Type of Term: iirds:AfterUse
Label: Disassembly
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Product lifecycle phase containing activities related to separating a machine or technical system into its different parts.

iirdsMch:EnvironmentalNote

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#EnvironmentalNote
Type of Term: iirds:Safety
Label: Environmental note
Definition: Information subject. Notes in technical documentation regarding environmental protection.

iirdsMch:EnvironmentalProtectionInstruction

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#EnvironmentalProtectionInstruction
Type of Term: iirds:Safety
Label: Environmental protection instruction
Definition: Information subject. Instructions in technical documentation for working in an environmentally compatible way.

iirdsMch:ExplosionProtection

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#ExplosionProtection
Type of Term: iirds:Safety
Label: Explosion protection
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Information in technical documentation how to avoid explosions when working with the product.

iirdsMch:FirstUse

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#FirstUse
Type of Term: iirds:PuttingToUse
Label: First use
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Product lifecycle phase describing the very first operation of a machine according to its intended use.

iirdsMch:FlowDiagram

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#FlowDiagram
Type of Term: iirds:TechnicalOverview
Label: Flow diagram
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Typical representation of a technical process.

iirdsMch:GenericConsumableSupply

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#GenericConsumableSupply
Type of Term: http://iirds.tekom.de/iirds/domain/machinery#ConsumableSupply
Label: Consumable supply
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Generic instance of the ConsumableSupply class.
Description: Consumable supplies MAY be referenced in the description of working tasks in technical documentation.
Description: The ConsumableSupply class describes goods or material that is consumed, meaning dissipated or spent, in the lifecycle of a technical system. Examples of consumables are batteries, sanding discs, and magnets.

iirdsMch:GenericHardwareTool

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#GenericHardwareTool
Type of Term: http://iirds.tekom.de/iirds/domain/machinery#HardwareTool
Label: Hardware tool
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Generic instance of the HardwareTool class.
Description: The HardwareTool class describes tools for a working task.

iirdsMch:GenericLubricant

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#GenericLubricant
Type of Term: http://iirds.tekom.de/iirds/domain/machinery#Lubricant
Label: Lubricant
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Generic instance of the Lubricant class.
Description: The Lubricant class describes lubricants, meaning a substance used for lubricating an engine or component, such as oil or grease. Lubricants MAY be referenced in the description of working tasks in technical documentation.

iirdsMch:GenericOperatingSupply

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#GenericOperatingSupply
Type of Term: http://iirds.tekom.de/iirds/domain/machinery#OperatingSupply
Label: Operating supply
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Generic instance of the OperatingSupply class.
Description: The OperatingSupply class describes operating supplies, meaning physical items REQUIRED for the running of a manufacturing production or service facility. Operating supplies MAY be referenced in the description of working tasks in technical documentation.

iirdsMch:GenericSetupTime

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#GenericSetupTime
Type of Term: http://iirds.tekom.de/iirds/domain/machinery#SetupTime
Label: Setup time
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Generic instance of the SetupTime class.
Description: The SetupTime class describes time periods REQUIRED to prepare a technical system for a specific function or job.

iirdsMch:GenericSparePart

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#GenericSparePart
Type of Term: http://iirds.tekom.de/iirds/domain/machinery#SparePart
Label: Spare part
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Generic instance of the SparePart class.
Description: The SparePart class describes spare parts, meaning interchangeable parts that are kept in an inventory and are used for the repair or replacement of failed units of a technical system. Spare parts MAY be referenced in the description of working tasks in technical documentation.

iirdsMch:HydraulicDiagram

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#HydraulicDiagram
Type of Term: iirds:TechnicalOverview
Label: Hydraulic diagram
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Graphical representation of flows of liquids for control, regulating, driving and braking devices of vehicles, airplanes or devices, whose forces are generated or transmitted by the pressure of a liquid.

iirdsMch:InstallationError

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#InstallationError
Type of Term: iirds:Safety
Label: Installation error
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Describes installation errors.

iirdsMch:Layout

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Layout
Type of Term: iirds:TechnicalOverview
Label: Layout
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Describes the technical structure of the component/machine.

iirdsMch:ListOfLubricants

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#ListOfLubricants
Type of Term: iirds:Collection
Label: List of lubricants
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Collection of lubricants REQUIRED for working tasks described in specific information units. The information is usually assembled from different information units.

iirdsMch:ListOfOperatingSupplies

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#ListOfOperatingSupplies
Type of Term: iirds:Collection
Label: List of operating supplies
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Collection of operating supplies; the information is usually assembled from different information units.

iirdsMch:ListOfSpareParts

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#ListOfSpareParts
Type of Term: iirds:Collection
Label: List of spare parts
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Collection of spare parts REQUIRED for working tasks described in specific information units. The information is usually assembled from different information units.

iirdsMch:ListOfTools

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#ListOfTools
Type of Term: iirds:Collection
Label: List of tools
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Collection of tools REQUIRED for working tasks described in specific information units. The information is usually assembled from different information units.

iirdsMch:LubricationPlan

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#LubricationPlan
Type of Term: iirds:Collection
Label: Lubrication plan
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. A lubrication plan shows the lubrication points of a machine/component and the REQUIRED lubricants.
Description: MAY be assembled from different information units.

iirdsMch:MaintenancePlan

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#MaintenancePlan
Type of Term: iirds:Collection
Label: Maintenance plan
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Maintenance plan. Collection of information REQUIRED for scheduled maintenance. The information is usually assembled from different information units.

iirdsMch:Modification

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Modification
Type of Term: iirds:Use
Label: Modification
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Lifecycle phase of a product during which it is modified.

iirdsMch:PartsList

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#PartsList
Type of Term: iirds:Collection
Label: List of parts
Definition: Information subject. Collection of parts.

iirdsMch:PneumaticDiagram

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#PneumaticDiagram
Type of Term: iirds:TechnicalOverview
Label: Pneumatic diagram
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Contains a technical diagram of a pneumatic system.

iirdsMch:Reuse

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Reuse
Type of Term: iirds:AfterUse
Label: Recycling
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Lifecycle phase after the active use of a product; contains activities for recycling and reusing machine components and materials.
Description: Refers to reuse of materials, not of information.

iirdsMch:SafetyEquipment

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#SafetyEquipment
Type of Term: iirds:Safety
Label: Safety equipment
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Describes equipment that is used for the protection of life and to avoid injuries or casualties.

iirdsMch:SafetyMeasure

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#SafetyMeasure
Type of Term: iirds:Safety
Label: Safety measure
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Information subject. Describes safety measures for work tasks.

iirdsMch:Storage

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Storage
Type of Term: iirds:AfterUse
Label: Storage
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Lifecycle phase of a product that describes the process of keeping physical products available or in an adequate environment in order to bridge the time gap between arrival and use.

iirdsMch:Transport

Term Description
URI: http://iirds.tekom.de/iirds/domain/machinery#Transport
Type of Term: iirds:PuttingToUse
Label: Transport
Type: iirdsMch:iirdsMachineryDomainEntity
Definition: Lifecycle phase of a product containing activities for transporting a technical system or its components from one location to the other.

A.3 Software Domain

A.3.1 Class Definitions

iirdsSft:iirdsSoftwareDomainEntity

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#iirdsSoftwareDomainEntity
Type of Term: http://www.w3.org/2000/01/rdf-schema#Class
Label: iirdsSoftwareDomainEntity
Subclass Of: iirds:iirdsDomainEntity
Definition: Entity of the software domain.

A.3.2 Property Definitions

n/a

A.3.3 Relations

n/a

A.3.4 Object Definitions

iirdsSft:Administration

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#Administration
Type of Term: iirds:Use
Label: Administration
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Lifecycle phase of a product containing activities related to managing, updating, and configuring software products and IT systems.

iirdsSft:Architecture

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#Architecture
Type of Term: iirds:TechnicalOverview
Label: Architecture
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Technical structure of a software product or component.

iirdsSft:Customization

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#Customization
Type of Term: iirds:Use
Label: Customization
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Lifecycle phase of a product containing activities relating to reworking a standard product to the special requirements of individual customers.

iirdsSft:Deinstallation

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#Deinstallation
Type of Term: iirds:AfterUse
Label: Deinstallation
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Lifecycle phase of a product containing procedures for deinstalling an IT system or removing a software from a system.

iirdsSft:Deployment

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#Deployment
Type of Term: iirds:PuttingToUse
Label: Deployment
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Lifecycle phase of a product describing activities related to making a software system available for use.

iirdsSft:Integration

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#Integration
Type of Term: iirds:PuttingToUse
Label: Integration
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Lifecycle phase of a product containing procedures for integrating a software or IT system with other software products or systems.

iirdsSft:Interface

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#Interface
Type of Term: iirds:TechnicalOverview
Label: Interface
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Information subject. Point of interaction between hardware and software or between software programs.

iirdsSft:SystemRequirement

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#SystemRequirement
Type of Term: iirds:TechnicalData
Label: System requirement
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Information subject. Describes the requirements that need to be fulfilled in order for a software to be installed and operated.
Description: Examples are operating system, storage space, and RAM size.

iirdsSft:Update

Term Description
URI: http://iirds.tekom.de/iirds/domain/software#Update
Type of Term: iirds:Use
Label: Update
Type: iirdsSft:iirdsSoftwareDomainEntity
Definition: Lifecycle phase of a software product containing procedures for installing a new version of a software in an IT system.

A.4 Properties and Relations Overview

Subject Predicate Object type Cardinality
iirds:Component iirds:has-component iirds:Component 0..⃰
iirds:Component iirds:has-identity iirds:Identity 0..⃰
iirds:Component iirds:relates-to-party iirds:Party 0..1
iirds:ContentLifeCycleStatus iirds:dateOfEffect http://www.w3.org/2001/XMLSchema#dateTimeStamp 0..1
iirds:ContentLifeCycleStatus iirds:dateOfExpiry http://www.w3.org/2001/XMLSchema#dateTimeStamp 0..1
iirds:ContentLifeCycleStatus iirds:dateOfStatus http://www.w3.org/2001/XMLSchema#dateTimeStamp 0..1
iirds:ContentLifeCycleStatus iirds:statusComment http://www.w3.org/2000/01/rdf-schema#Literal 0..⃰
iirds:ContentLifeCycleStatus iirds:has-content-lifecycle-status-value iirds:ContentLifeCycleStatusValue 1
iirds:ContentLifeCycleStatus iirds:purpose http://www.w3.org/2000/01/rdf-schema#Literal 0..1
iirds:ContentLifeCycleStatus iirds:relates-to-party iirds:Party 0..1
iirds:DirectoryNode iirds:has-directory-structure-type iirds:DirectoryNodeType 0..1
iirds:DirectoryNode iirds:has-first-child iirds:DirectoryNode 0..1
iirds:DirectoryNode iirds:has-next-sibling iirds:DirectoryNode 0..1
iirds:Document iirds:has-document-type iirds:DocumentType 1..⃰
iirds:Event iirds:has-event-code   0..1
iirds:Event iirds:has-event-type   0..1
iirds:Identity iirds:identifier http://www.w3.org/2000/01/rdf-schema#Literal 1
iirds:Identity iirds:has-identity-domain iirds:IdentityDomain 1
iirds:IdentityDomain iirds:relates-to-party iirds:Party 0..1
iirds:iirdsDomainEntity iirds:description http://www.w3.org/2000/01/rdf-schema#Literal 0..⃰
iirds:iirdsDomainEntity iirds:synonym http://www.w3.org/2000/01/rdf-schema#Literal 0..⃰
iirds:iirdsDomainEntity iirds:iirdsRelationConcept iirds:iirdsDomainEntity 0..⃰
iirds:iirdsDomainEntity iirds:relates-to-administrative-metadata iirds:AdministrativeMetadata 0..⃰
iirds:InformationObject iirds:has-identity iirds:Identity 0..⃰
iirds:InformationUnit iirds:dateOfCreation http://www.w3.org/2001/XMLSchema#dateTimeStamp 0..1
iirds:InformationUnit iirds:dateOfLastModification http://www.w3.org/2001/XMLSchema#dateTimeStamp 0..1
iirds:InformationUnit iirds:language http://www.w3.org/2000/01/rdf-schema#Literal 0..⃰
iirds:InformationUnit iirds:revision http://www.w3.org/2000/01/rdf-schema#Literal 0..1
iirds:InformationUnit iirds:rights http://www.w3.org/2000/01/rdf-schema#Literal 0..⃰
iirds:InformationUnit iirds:title http://www.w3.org/2000/01/rdf-schema#Literal 0..1
iirds:InformationUnit iirds:is-applicable-for-document-type iirds:DocumentType 0..⃰
iirds:InformationUnit iirds:has-abstract   0..1
iirds:InformationUnit iirds:has-content-lifecycle-status iirds:ContentLifeCycleStatus 0..⃰
iirds:InformationUnit iirds:has-identity iirds:Identity 0..⃰
iirds:InformationUnit iirds:has-information-type iirds:InformationType 0..⃰
iirds:InformationUnit iirds:has-planning-time iirds:PlanningTime 0..⃰
iirds:InformationUnit iirds:has-rendition iirds:Rendition 0..⃰
iirds:InformationUnit iirds:has-subject iirds:InformationSubject 0..⃰
iirds:InformationUnit iirds:has-topic-type iirds:TopicType 0..⃰
iirds:InformationUnit iirds:is-part-of-package iirds:Package 0..⃰
iirds:InformationUnit iirds:is-replacement-of iirds:InformationUnit 0..1
iirds:InformationUnit iirds:is-version-of iirds:InformationObject 0..1
iirds:InformationUnit iirds:relates-to-component iirds:Component 0..⃰
iirds:InformationUnit iirds:relates-to-event iirds:Event 0..⃰
iirds:InformationUnit iirds:relates-to-functional-metadata iirds:FunctionalMetadata 0..⃰
iirds:InformationUnit iirds:relates-to-information-unit iirds:InformationUnit 0..1
iirds:InformationUnit iirds:relates-to-party iirds:Party 0..1
iirds:InformationUnit iirds:relates-to-product-feature iirds:ProductFeature 0..⃰
iirds:InformationUnit iirds:relates-to-product-lifecycle-phase iirds:ProductLifeCyclePhase 0..⃰
iirds:InformationUnit iirds:relates-to-product-metadata iirds:ProductMetadata 0..⃰
iirds:InformationUnit iirds:relates-to-product-variant iirds:ProductVariant 0..⃰
iirds:InformationUnit iirds:relates-to-qualification iirds:Qualification 0..⃰
iirds:InformationUnit iirds:relates-to-supply iirds:Supply 0..⃰
iirds:MaintenanceInterval iirds:frequency http://www.w3.org/2000/01/rdf-schema#Literal 1
iirds:Package iirds:formatRestriction http://www.w3.org/2000/01/rdf-schema#Literal 0..1
iirds:Package iirds:iiRDSVersion http://www.w3.org/2000/01/rdf-schema#Literal 1
iirds:Party iirds:has-party-role iirds:PartyRole 0..1
iirds:Party iirds:relates-to-vcard http://www.w3.org/2006/vcard/ns#Kind 0..1
iirds:PlanningTime iirds:duration http://www.w3.org/2001/XMLSchema#duration 1
iirds:ProductVariant iirds:has-identity iirds:Identity 0..⃰
iirds:ProductVariant iirds:relates-to-party iirds:Party 0..1
iirds:RangeSelector iirds:has-end-selector iirds:FragmentSelector 1
iirds:RangeSelector iirds:has-start-selector iirds:FragmentSelector 1
iirds:Rendition iirds:format http://www.w3.org/2000/01/rdf-schema#Literal 1
iirds:Rendition iirds:source http://www.w3.org/2000/01/rdf-schema#Literal 1
iirds:Rendition iirds:has-identity iirds:Identity 0..⃰
iirds:Rendition iirds:has-selector iirds:Selector 0..1

A.5 iiRDS Metadata Class Diagram

iiRDS Metadata Class Diagram

Figure 3 iiRDS Metadata Class Diagram

B. References

B.1 Normative references

[rdf-syntax-grammar]
RDF 1.1 XML Syntax. Dave Beckett. W3C. 25 February 2014. W3C Recommendation. URL: https://www.w3.org/TR/rdf-syntax-grammar/
[UNICODE]
The Unicode Standard. Unicode Consortium. URL: https://www.unicode.org/versions/latest/
[ZIP]
.ZIP File Format Specification. 1 September 2012. Final. URL: https://www.pkware.com/documents/casestudies/APPNOTE.TXT

B.2 Informative references

[DCTERMS]
DCMI Metadata Terms. Dublin Core metadata initiative.14 June 2012. DCMI Recommendation. URL: http://dublincore.org/documents/dcmi-terms/
[HTML5]
HTML5. Ian Hickson; Robin Berjon; Steve Faulkner; Travis Leithead; Erika Doyle Navara; Theresa O'Connor; Silvia Pfeiffer. W3C. 27 March 2018. W3C Recommendation. URL: https://www.w3.org/TR/html5/
[IEC82045-2]
Document management -- Part 2: Metadata elements and information reference model. ISO. URL: https://www.iso.org/standard/34513.html
[rfc2119]
Key words for use in RFCs to Indicate Requirement Levels. S. Bradner. IETF. March 1997. Best Current Practice. URL: https://tools.ietf.org/html/rfc2119
[rfc3987]
Internationalized Resource Identifiers (IRIs). M. Duerst; M. Suignard. IETF. January 2005. Proposed Standard. URL: https://tools.ietf.org/html/rfc3987
[vcard-rdf]
vCard Ontology - for describing People and Organizations. Renato Iannella; James McKinney. W3C. 22 May 2014. W3C Note. URL: https://www.w3.org/TR/vcard-rdf/
[VDI2770]
Richtlinie VDI 2770 Blatt 1 'Digitale Herstellerinformationen [German]'. VDI. URL: https://www.vdi.de/2770