Although use of dITContentRules definitions is normally better suited for custom design to suit the needs of the directory, the rootArc STRUCTURAL class is rigid enough that a general-use rule MAY be worth adding to the I-D series.
Here is an example that has been tested. If this definition is incorporated, it is slated for placement within Section 2.6.1 of the RASCHEMA I-D.
## The rootContentRule governs the contents of any 'rootArc'
## instance (1.3.6.1.4.1.56521.101.2.5.2). Specifically, this
## rule enforces that the minimum (sensible) requirements are
## satisfied, and that no forbidden attribute types are used.
## For example, 'rootArc' entries cannot be frozen.
dITContentRules: ( 1.3.6.1.4.1.56521.101.2.5.2
NAME 'rootContentRule'
AUX ( spatialContext
$ registrationSupplement
$ x660Context
$ x680Context
$ x690Context )
MUST ( iRI
$ unicodeValue
$ aSN1Notation
$ identifier )
NOT ( topArc
$ supArc
$ c-topArc
$ c-supArc
$ isFrozen
$ isLeafNode
$ dotEncoding
$ dotNotation
$ registrationRange ) )
Although use of
dITContentRulesdefinitions is normally better suited for custom design to suit the needs of the directory, therootArcSTRUCTURAL class is rigid enough that a general-use rule MAY be worth adding to the I-D series.Here is an example that has been tested. If this definition is incorporated, it is slated for placement within Section 2.6.1 of the RASCHEMA I-D.