Glossary · Extensions

iiRDS Handover Documentation Domain

Also known as: Handover Documentation Domain, iiRDS handover domain, iirdsHov

In iiRDS (intelligent information Request and Delivery Standard), the Handover Documentation Domain is the standardized domain extension in the namespace http://iirds.tekom.de/iirds/domain/handover that provides the vocabulary for the restricted iiRDS/H variant: the class iirdsHov:DocumentCategory, the relation iirdsHov:has-document-category and twelve document categories that correspond to the categories of VDI 2770.

iiRDS term
Ontology
Information architecture

In one sentence

The iiRDS Handover Documentation Domain adds twelve document categories for iiRDS/H, from Identification to Contract documents, matching VDI 2770.

Example

An operating manual in an iiRDS/H package has the document type iirds:OperatingInstructions and the document category iirdsHov:Operation.

How it applies

Class: iirdsHov:DocumentCategory is defined as a type of information arranged in a document, defined with respect to its main content. It is a subclass of iirds:InformationType and of iirdsHov:iirdsHandoverDomainEntity, the root of the domain.
Relation: iirdsHov:has-document-category is a subproperty of iirds:has-information-type; its domain is iirds:Document and its range iirdsHov:DocumentCategory. The schema allows at most one category per document, and the metadata requirements of iiRDS/H make exactly one mandatory, next to at least one document type.
Instances: The domain defines twelve document categories.

iiRDS instance	Label in the specification	Corresponding VDI 2770 category
`iirdsHov:Identification`	Identification	01-01 Identification
`iirdsHov:TechnicalSpecification`	Technical specification	02-01 Technical specification
`iirdsHov:DrawingsPlans`	Drawings, Plans	02-02 Drawings, plans
`iirdsHov:Components`	Components	02-03 Components
`iirdsHov:Certificates`	Certificates	02-04 Certificates
`iirdsHov:AssemblyDisassembly`	Assembly, Disassembly	03-01 Assembly, disassembly
`iirdsHov:Operation`	Operation	03-02 Operation
`iirdsHov:GeneralSafety`	General Safety	03-03 General safety
`iirdsHov:InspectionMaintenanceControl`	Inspection, Maintenance, Control	03-04 Inspection, maintenance
`iirdsHov:Repair`	Repair	03-05 Repair
`iirdsHov:SpareParts`	Spare parts	03-06 Spare parts
`iirdsHov:ContractDocuments`	Contract documents	04-01 Contract documents

Correspondence: The labels follow the categories of VDI 2770 Blatt 1; the specification does not list VDI 2770 identifiers for them. To record the identifier itself, add an external classification with the classification type iirds:VDI2770.
Use outside iiRDS/H: The domain is part of the iiRDS standard, like the Machinery and Software Domains, so unrestricted packages can use the same categories, for example to let a portal group whole documents the way an operator files them.
Limits: A document category says what a document is mainly about. It does not say whether the document fulfills any legal requirement for that kind of information.

Document category vs. document type

A document in iiRDS/H needs both. The document type, from the iiRDS core (iirds:OperatingInstructions, iirds:DeclarationOfConformity and others), says what kind of document it is. The document category says in which of the twelve handover groups it is filed. Several document types can share one category.

In RDF

Shown in Turtle for readability; iiRDS/H packages must also provide their metadata in JSON-LD.

@prefix iirds: <http://iirds.tekom.de/iirds#> .
@prefix iirdsHov: <http://iirds.tekom.de/iirds/domain/handover#> .

<https://example.com/iirds/d1_en> a iirds:Document ;
    iirds:title "BM01 – Operating instructions"@en ;
    iirds:language "en" ;
    iirds:has-document-type iirds:OperatingInstructions ;
    iirdsHov:has-document-category iirdsHov:Operation .

In one sentence

Example

How it applies

Document category vs. document type

In RDF

External references