S1000D DIG General Business rules S1000D Defense Interest Group S1000D Defense Interest Group All //dmCode[@systemDiffCode[contains(.,"I") or contains(.,"O")] or @systemCode[contains(.,"I") or contains(.,"O")] or @subSystemCode[contains(.,"I") or contains(.,"O")] or @subSubSystemCode[contains(.,"I") or contains(.,"O")] or @assyCode[contains(.,"I") or contains(.,"O")] or @disassyCode[contains(.,"I") or contains(.,"O")] or @disassyCodeVariant[contains(.,"I") or contains(.,"O")] or @infoCode[contains(.,"I") or contains(.,"O")] or @infoCodeVariant[contains(.,"I") or contains(.,"O")] or @learnCode[contains(.,"I") or contains(.,"O")]] Specific alpha character values Chap 1.3 Para 6.2.4 BRDP-S1-00001 Use of "I" and "O" Decide whether and when to use the alpha characters "I" and "O". The alpha characters "I" and "O" can only be used for the Model Identification code in the Data Module Code (DMC). For the rest of the DMC "I" and "O" shall not be used in data module coding. //title[descendant::internalRef or descendant::dmRef or descendant::pmRef or descendant::externalPubRef] Use of cross-references from titles Chap 3.9.5.2.1.5 Para 2 BRDP-S1-00119 Use of cross- references from titles Decide whether to allow cross-referencing from titles. Cross-referencing from titles shall not be allowed. //title[count(ancestor::levelledPara) > 8] Use of titles for the elements levelledPara and proceduralStep Chap 3.9.5.2.1.5 Para 2 BRDP-S1-00120 Use of titles for the elements levelledPara and proceduralStep from sublevel six thru eight for legacy data Decide whether titles can be included for the elements levelledPara and proceduralStep from sublevel six thru eight when converting legacy data to S1000D. Titles for levels six thru eight in the elements levelledPara, levelledParaAlt, proceduralStep or proceduralStepAlt can be used. //title[count(ancestor::levelledParaAlt) > 8] Use of titles for the elements levelledPara and proceduralStep Chap 3.9.5.2.1.5 Para 2 BRDP-S1-00120 Use of titles for the elements levelledPara and proceduralStep from sublevel six thru eight for legacy data Decide whether titles can be included for the elements levelledPara and proceduralStep from sublevel six thru eight when converting legacy data to S1000D. Titles for levels six thru eight in the elements levelledPara, levelledParaAlt, proceduralStep or proceduralStepAlt can be used. //title[count(ancestor::proceduralStep) > 8] Use of titles for the elements levelledPara and proceduralStep Chap 3.9.5.2.1.5 Para 2 BRDP-S1-00120 Use of titles for the elements levelledPara and proceduralStep from sublevel six thru eight for legacy data Decide whether titles can be included for the elements levelledPara and proceduralStep from sublevel six thru eight when converting legacy data to S1000D. Titles for levels six thru eight in the elements levelledPara, levelledParaAlt, proceduralStep or proceduralStepAlt can be used. //title[count(ancestor::proceduralStepAlt) > 8] Use of titles for the elements levelledPara and proceduralStep Chap 3.9.5.2.1.5 Para 2 BRDP-S1-00120 Use of titles for the elements levelledPara and proceduralStep from sublevel six thru eight for legacy data Decide whether titles can be included for the elements levelledPara and proceduralStep from sublevel six thru eight when converting legacy data to S1000D. Titles for levels six thru eight in the elements levelledPara, levelledParaAlt, proceduralStep or proceduralStepAlt can be used. //graphic[parent::table] Use of tables as graphics Chap 3.9.5.2.1.6 Para 2.4 BRDP-S1-00122 Use of tables as graphics Decide if tables represented as graphics are allowed, and if they are, in what situations they can be used. Tables represented as graphics shall be allowed. //supportEquipDescr[(not(attribute::id = //internalRef/@internalRefId))][ancestor::preliminaryRqmts] Use of the attribute id on the element supportEquipDescr Chap 3.9.5.2.1.9 Para 2.5.1 BRDP-S1-00150 Use of the attribute id on the element supportEquipDescr in the element preliminaryRqmts Decide whether to use the attribute id to create cross- references from the procedure to the support equipment listed in Preliminary requirements. The attribute id on element supportEquipDescr is used to establish the link between the two and will guarantee consistent use of identification throughout the procedure. The use of cross-references is encouraged. The attribute id shall always be used for cross-referencing purposes. //supplyDescr[(not(attribute::id = //internalRef/@internalRefId))][ancestor::preliminaryRqmts] Use of the attribute id on the element supplyDescr Chap 3.9.5.2.1.9 Para 2.6.1 BRDP-S1-00155 Use of the attribute id on the element supplyDescr in the element preliminaryRqmts Decide whether to use the attribute id to create cross- references from the procedure to the supplies listed in Preliminary requirements. The attribute id on element supplyDescr is used to establish the link between the two and will guarantee consistent use of identification throughout the procedure. The use of cross-references is encouraged. The attribute id shall be used for cross-referencing from a procedure to the supplies listed in the Preliminary requirements. //spareDescr[(not(attribute::id = //internalRef/@internalRefId))][ancestor::preliminaryRqmts] Use of the attribute id on the element spareDescr Chap 3.9.5.2.1.9 Para 2.7.1 BRDP-S1-00156 Use of the attribute id on element spareDescr in the element preliminaryRqmts Decide whether to use the attribute id to create cross- references from the procedure to the spares listed in Preliminary requirements. The attribute id on element spareDescr is used to establish the link between the two and will guarantee consistent use identification throughout the procedure. The use of cross-references is encouraged. The attribute id shall be used for cross-referencing from a procedure to the spares listed in the Preliminary requirements. //levelledPara[child::levelledPara or child::levelledParaAlts] | //levelledParaAlts[child::levelledPara] Level of depth of descriptive data modules (levelledPara and levelledParaAlts) Chap 3.9.5.2.2 Para 2.4 BRDP-S1-00180 Level of depth of descriptive data modules Decide whether to exceed 5 levels of depth for new data. For new projects, the granularity of the descriptive data modules shall not exceed 5 levels. For legacy data this may be increased as required. //levelledPara[parent::description][not(child::levelledPara or child::levelledParaAlts)] | //levelledParaAlts[parent::description][not(child::levelledPara)] Minimum para occurrences (levelledPara and levelledParaAlts) Chap 3.9.5.2.2 Para 2.4 BRDP-S1-00181 Minimum para occurrences Decide whether to impose a minimum of two occurrences of child elements. For new projects, the minimum of two occurrences shall be imposed. //proceduralStep/proceduralStep/proceduralStep/proceduralStep/proceduralStep/proceduralStep Decide on the maximum number of step levels allowed in a procedure Chap 3.9.5.2.3 Para 2.4.1 BRDP-S1-00186 Decide on the maximum number of step levels in a procedure Decide on the maximum number of step levels allowed in a procedure. Exceeding five levels of depth is strongly discouraged in development of new data. It is recommended that additional levels are only used in a conversion effort where the existing data is authored to this depth (maximum eight levels) and restructuring of data is not feasible. For new projects, the maximum number of step levels shall be five. For legacy data this may be increased as required. //natoStockNumber[not(@natoCodificationBureau and @natoItemIdentNumberCore and @natoSupplyClass)] Use of the element natoStockNumber (NATO stock number) Chap 3.9.5.2.7 Para 2.2.1.2 BRDP-S1-00216 Use of the element natoStockNumber (NATO stock number) Decide whether and how to use the NATO Stock Number, split it into its three fields using the attributes natoSupplyClass, natoCodificationBureau and natoItemIdentNumberCore or to fill it as a whole in the child element fullNatoStockNumber. When NATO Stock Numbers (NSNs) are used in the project, the NSN shall be specified using the three attributes. //@assyCode Number of characters in assembly code Chap 4.3.3 Para 2.2.4 BRDP-S1-00338 Number of characters in assembly code Decide whether to use two or four characters for unit or assembly. Four characters shall be used. [0-9A-Z]{4} //@infoCode[normalize-space(string(.)) = "951"] Identification of a process data module Chap 4.11 Para 2.3 BRDP-S1-00372 Use of the generic IC 951 for identification of process data modules Decide whether to use IC 951 for identification of process data modules. IC 951 shall not be used. The appropriate information codes relating to the content of the process data module shall be used. //brexDmRef Use of a project- specific BREX data module Chap 4.10 Para 2.1 BRDP-S1-00366 Use of a project- specific BREX data module Decide whether to develop and use a project-specific BREX data module. The project should refer to the most appropriate BREX within the layers. If required a project-specific BREX data module shall be developed. //brexDmRef Use of layered BREX data modules Chap 4.10 Para 2.2 BRDP-S1-00367 Use of layered BREX data modules Decide whether to apply a layered BREX data module structure. This decision is related to, but not entirely dependent on, whether a layered business rules structure applies. A layered BREX data module structure shall be applied. //tocEntry/tocEntry/tocEntry/tocEntry/tocEntry/tocEntry Use of hierarchical Table of contents Chap 3.9.5.2.16 Para 2.3.2.3 BRDP-S1-00304 Use of hierarchical Table of contents Decide whether to use a hierarchical Table of contents and on the number of levels. When the project applies a hierarchical Table of Contents (TOC) up to five levels shall be used. //tocEntry[descendant::issueInfo or descendant::externalPubIssueInfo or descendant::issueDate or descendant::externalPubIssueDate] Use of issue number and/or issue date in the Table of contents Chap 3.9.5.2.16 Para 2.3.2.3.2 BRDP-S1-00306 Use of issue number and/or issue date in the Table of contents Decide whether to use and present the issue number (issueInfo/externalPubIssueInfo) and/or the issue date (issueDate/externalPubIssueDate) for the entries in the Table of contents The issue number and issue date shall not be used in the Table of Contents (TOC). //dmodule/identAndStatusSection/dmAddress/dmIdent/dmCode/@disassyCodeVariant Identification of container data module Chap 4.13.4 Para 2.3.2 BRDP-S1-00385 Identification of container data module Decide which identification method to use for container data modules. The chosen method must be used systematically. The following value shall be assigned to the disassembly code variant: "Z, ZZ or ZZZ" in accordance with the project data module coding rules. [A-Z]{1,3} //container Use of applicability within container data module content s Chap 4.13.4 Para 2.5 BRDP-S1-00386 Use of applicability within container data module content Decide whether applicability annotations are duplicated from the referenced data modules to the container data module. Applicability annotations shall be duplicated from the referenced data modules to the container data module. //@internalRefTargetType[normalize-space(string(.)) = "irtt11"] Use of hotspots in IPD data module Chap 3.9.5.2.7 Para 2.4.3 BRDP-S1-00217 Use of hotspots in IPD data modules Decide whether to use the generic hotspot mechanism in IPD data modules. The generic hotspot mechanism shall be used in IPD data modules. //genericPartData Use of hotspots in IPD data module Chap 3.9.5.2.7 Para 2.5.12 BRDP-S1-00237 Use of the BREX to define the non-S2000M elements Decide whether to use the BREX for the definition of the non- S2000M elements. The BREX shall always be used to define any genericPartData element names. //checkListStep/checkListStep/checkListStep/checkListStep/checkListStep/checkListStep Define maximum number of step levels (element checkListStep) in checkListProcedure Chap 3.9.5.2.14 Para 2.3.1.3.5 BRDP-S1-00279 Define maximum number of step levels in checkListProcedure Projects must decide the maximum number of step levels allowed. The maximum number of step levels in checkListProcedure shall be five. For legacy data this may be increased as required. //dml Use of data management requirement list Chap 4.5 Para 2.1 BRDP-S1-00350 Use of data management requirement list Decide whether to use the data management requirement list for specification and exchange of CSDB planning information. The data management requirement list shall always be used in a format specified by the project/organization. //notationRuleList Include restrictions in using various illustration, multimedia object or other data information formats Chap 4.10.2.2 Para 2.2 BRDP-S1-00370 Include restrictions in using various illustration, multimedia object or other data information formats Decide whether to use the BREX data module to impose any restrictions in the use of various formats for illustrations, multimedia objects or other data. The BREX data module shall be used to impose restrictions in the use of various formats for illustrations, multimedia objects or other data. Use of applicability Chap 4.14 Para 2.1.2 BRDP-S1-00387 Use of applicability Decide if the project will use applicability. Applicability shall be included at the data module (DM) level and shall be optional within the content.