S1000D Issue 4.2 vs. Issue 4.1 - Part III

Part 3: The Elements and Attributes of the Business Rules Documents

  1. The following is a brief analysis of the elements and attributes introduced in Issue 4.2 to provide a schema to cover the business rule document. The principal markup elements their attributes and children used to describe the business rule documents will be discussed.
    • Elements are identified in Red bold text.
    • The attributes are highlighted in Yellow.
    • Elements or attributes added in S1000D Issue 4.2 but not specifically related to the Business rule documents are highlighted in Bright Blue.
    • Definitions are provided for the highlighted items.
    • Definitions are not provided for common attributes and elements found in descriptive data modules and reused in the Business rules document data module.
  2. Each element will be presented with its definition, followed by its attributes and children elements.
    • Attribute definitions will be provided when the attribute is first identified.
    • Subsequent occurrences of the elements and attributes will have a reference to the location of the element or attribute definition.
    • Reference to the location of children element definitions is provided.

    3. The following elements are children of several elements. They have been highlighted<brLeveledPara> <brDecision> <brdecisionRef>

    diagram-s1000d-issue-4-2-vs-issue-4-1-part-iii
  3. Markup element: <content> captures all types of information related to business rules documentation
    • Attributes:
      1. id (O)
    • Child elements:
      1. <refs>
      2. <referencedApplicGroup>
      3. <referencedApplicGroupRef>
      4. <brDoc> See para 4
  4. Markup element: <brDoc> has a similar structure to the main content of the descriptive data modules (<warningAndCautionElemGroup>, is not included in the Business rules document data module)
    • Attributes:
      1. defaultBrSeverityLevel (O), the default business rules severity level which indicates the severity level of any rules for which no explicit severity level is specified.
        2. Allowable ValuesS1000D Interpretation
        “brsl01”Most severe
        “brsl02”Medium severity
        “brsl03”Least severe
        “brsl51” - “brsl99”Available for projects
    • Child elements:
      1. <para>
      2. <note>
      3. <brLeveledPara> see para 5
      4. <figure>
      5. <multimedia>
      6. <foldout>
      7. <table>
  5. Markup element: <brLevelledPara> is much like <leveledPara> in the descriptive Data module. There are additional elements and attributes provided in the element <brLevelledPara> for recording business rules information.
    • Attributes:
      1. applicRefId (O)
      2. id (O)
      3. changeType (O)
      4. changeMark (O)
      5. reasonForUpdateRefIds (O)
      6. authorityName (O)
      7. authorityDocument (O)
      8. securityClassification (O)
      9. commercialClassification (O)
      10. caveat (O)
      11. derivativeClassificationRefId (O): The element <derivativeClassification> was introduced in Issue 4.2, it contains all derivative classification actions taken (eg, source material, date of action, action type) to the information in the complete publication.
    • Child elements:
      1. <para>
      2. <note>
      3. <brDecision> see para 6
      4. <brPara> see para 7
      5. <para>
      6. <figure>
      7. <multimedia>
      8. <foldout>
      9. <table>
      10. <brLeveledPara> see para 5
  6. Markup element: <brDecision> contains a single decision applicable to the project or organization. A decision is not limited to authoring or publishing but can contain anything related to the organization or project. These decisions can be included in whole or in part and addressed throughout the lifecycle of the product.
    • The <brDecision>
      1. is a child of <brLeveledPara>
      2. as well as a child of <brPara>
    • Attributes:
      1. applicRefId (O)
      2. id (O)
      3. changeMark (O)
      4. changeType (O)
      5. reasonForUpdateRefIds (O)
      6. brDecisionIdentNumber (M), the unique identifier of the element <brDecision>:
        1. It must be used when at least one element <brDecisionText> and/or element <brDecisionValueGroup> is populated.
        2. The only allowed case for not including the attribute brDecisionIdentNumber is when the mandatory choice element <brDecisionPending> is used.
        3. The coding scheme of the attribute brDecisionIdentNumber is a project/organizational decision. It must be defined in such a way that inter-project, inter-program or inter-organizational referencing is possible by using solely the identifier coded by this attribute. For example, the model identifier, as well as the originator’s CAGE code can be included as a part of thebrDecisionIdentNumber. The project and/or organization must ensure the uniqueness of the identifiers captured by the attribute brDecisionIdentNumber.
      7. brexRuleFlag (O), indicates whether the business rule decision must or must not be captured in a BREX data module.
      8. When used, the textual information captured in the element <brDecisionText> (see para 10) must go into the textual response definitions of the element <objectUse> inside a BREX data module.
      9. These can be identified and automatically imported if needed.
      10. brSeverityLevel (O), the indicator of the severity of not implementing the business rule decision with its definition. the attribute can have one of the following values”
        Allowable for ProjectsS1000D Interpretation
        “brsl01”Most severe
        “brsl02”Medium severity
        “brsl03”Least severe
        “brsl51” - “brsl99”Available for projects
      11. authorityName (O)
      12. authorityDocument (O)
      13. securityClassification (O)
      14. commercialClassification (O)
      15. caveat (O)
      16. derivativeClassificationRefId (O) see Attributes in para 5
    • Child elements:
      1. <title>
      2. <brDecisionRef> see para 8
      3. <brDecisionPending> see para 9
      4. <brDecisionText> see para 10
      5. <brDecisionValueGroup> see para 11
      6. <brDecisionExplanation> see para 13
  7. Markup element: <brPara> is a child of element of<brLeveledPara> (see para 5) in the descriptive structure of a business rules data module. It contains information about:
    • A business rule that includes the definition of a BRDP
    • A business rule decision that has been made
    • An indication of the relationship of the business rule to various concepts and constructs defined by the specification
    • The audit information on the BRDP and/or business rules decisions taken upon it
    • Attributes:
      1. applicRefId (O)
      2. id (O)
      3. changeType (O)
      4. changeMark (O)
      5. reasonForUpdateRefIds (O)
      6. brDecisionPointUniqueIdent (M), the unique identifier of a BRDP
      7. brDecisionPointPriority(O), indicates the priority of the BRDP for a project or organization:
        1. The setting of the BRDP priority can assist the project and/or organization by identifying which business rules should be defined first.
        2. This attribute has five predefined values.
          3. Allowable ValuesS1000D Interpretation
          “brpr01”Highest BR priority
          “brpr02”Next lower level of BR priority
          “brpr03”Next lower level of BR priority
          “brpr04”Next lower level of BR priority
          “brpr05”Lowest level of BR priority
      8. authorityName (O)
      9. authorityDocument (O)
      10. securityClassification (O)
      11. commercialClassification (O)
      12. caveat (O)
      13. derivativeClassificationRefId (O) see Attributes in para 5
    • Child elements:
      1. <brRelatedTo> see para 14
      2. <brDecisionPointContent> see para 15
      3. <brDecision> see para 6
      4. <brAudit> see para 16
  8. Markup element: <brDecisionRef> defines a reference of a business rule decision or another element to a business rule decision. The direct reference from a business rule decision to itself is not allowed.
    • The <brDecisionRef>
      1. is a child of <brDecision> see para 6
      2. as well as a child of <brAudit> see para 16
      3. and a child of <brAction> see para 27
    • Attributes:
      1. id (O)
      2. changeType (O)
      3. changeMark (O)
      4. reasonForUpdateRefIds (O)
      5. brDecisionIdentNumber (O)the unique identifier of the element <brDecision> being referred to. It is used for the purpose of implicit referencing. See Attributes in para 6
      6. authorityName (O)
      7. authorityDocument (O)
      8. securityClassification (O)
      9. commercialClassification (O)
      10. caveat (O)
      11. derivativeClassificationRefId (O) see Attributes in para 5
    • Child elements:
      1. <refs>. Used together with the attribute referredFragment and attribute id on the element <brDecision> (see para 6) for explicit referencing.
  9. Markup element: <brDecisionPending> indicates that a business rule decision has not been determined and is “to be defined”.
    • Attributes:
      1. None
    • Child elements:
      1. None
  10. Markup element: <brDecisionText> defines the exact wording of a business rule decision taken for a BRDP.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
    • Child elements:
      1. <para>
  11. Markup element: <brDecisionValueGroup> contains the allowed value, if any. The allowed values can be defined by the project (eg, CAGE code), or the values can be selected from the defined values in the business rule decision point value group (element <brDecisionPointValueGroup>) (eg, language).
    • Attributes:
      1. None
    • Child elements:
      1. <brDecisionValue> see para 12
  12. Markup element: <brDecisionValue>defines the type and, where required, the content of a business rules decision within the range and definitions of BRDP values as a recorded decision taken for a BRDP.
    • Attributes:
      1. brDecisionValueRegistered (M), the recorded value of a business rules decision.
        1. If a business rules decision is made for a certain BRDP and is not a stand-alone business rules decision, then this value must be within the range and of the type of the corresponding BRDP value.
        2. In case of a stand-alone business rules decision, the business rules decision values are already available in the legacy business rules documentation and (correspondingly) need to be captured in the business rules data module using the attribute brDecisionValueRegistered.
    • Child elements:
      1. <brDecisionValue> see para 12
  13. Markup element: <brDecisionExplanation> provides additional information for a business rules definition which was not defined by the element <brDecisionText>.
    • This can be information taken from the specification or any other information formulated by the project or organization.
    • These could be markup examples, extracts from the specification or data/documents from other projects or organizations.
    • The purpose of this added explanation is to enhance the reader’s understanding of the decision made for a BRDP.
    • Attributes:
      1. changeMark (O)
      2. changeType (O)
      3. reasonForUpdateRefIds (O)
    • Child elements:
      1. <title>
      2. <para>
      3. <example>
      4. <figure>
      5. <multimedia>
      6. <foldout>
      7. <table>
      8. <caption>
  14. Markup element: <brRelatedTo> indicates where in the source document the definition of the BRDP can be found and how the BRDP relates to decisions by the project or organization with respect to:
    • business rules categories
    • Schemas
    • configurable attributes
    • remarks
    • Attributes:
      1. id (O)
      2. changeMark (O)
      3. changeType (O)
      4. reasonForUpdateRefIds (O)
    • Child elements:
      1. <sourceDocRef> see para 17
      2. <brCategoryGroup> see para 18
      3. <s1000dSchemas> see para 21
      4. <configAttributes> see para 22
      5. <remarks>
  15. Markup element: <brDecisionPointContent> provides information for a BRDP. It includes the:
    • BRDP title and definition
    • BRDP values and their meaning, plus
    • explanation of the BRDP
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
    • Child elements:
      1. <title>
      2. <brDecisionPointText> see para 23
      3. <brDecisionPointValueGroup> see para 24
      4. <brDecisionPointExplanation> see para 26
  16. Markup element: <brAudit> captures the audit status on the BRDP and/or business rules decisions defined for it, including possible actions to be accomplished in order to come to a satisfying decision and the status with the required date of completion.
    • If one or more child elements <brDecisionRef> (see para 8) are defined, then the element <brDecibrAuditsionRef>(see para 16) refers both to the BRDP it applies to and to one or more of its business rules decisions.
    • If the <brDecisionRef> (see para 8) is missing, then <brAudit> (see para 16) is attributed only to the BRDP defined under the <brPara> (see para 7).
    • Multiple elements <brAudit> (see para 16) within a <brPara> (see para 7) make it possible to capture status not only per BRDP but also per business rules decision.
    • Recording of one <brAudit> (see para 16) for a group of business rules decisions defined within the same <brPara> (see para 7) is allowed.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
      4. authorityName (O)
      5. authorityDocument (O)
      6. securityClassification (O)
      7. commercialClassification (O)
      8. caveat (O)
      9. derivativeClassificationRefId (O)
    • Child elements:
      1. <brDecisionRef> see para 8
      2. <brAction> see para 27
      3. <brCurrentStatus> see para 28
  17. Markup element: <sourceDocRef> indicates where the information for the BRDP is defined.
    • This reference can point to a place inside the same business rules data module
    • A data module with related business rule information or
    • External documents in a non-S1000D or
    • Non-XML format
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
    • Child elements:
      1. <internalRef>
      2. <dmRef>
      3. <pmRef>
      4. <externalPubRef>
  18. Markup element: <brCategoryGroup> allows the business rules category (from 1 to 10) to which the BRDP is related to be indicated in the child <brCategory> see para 19.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
    • Child elements:
      1. <brCategory> see para 19
  19. Markup element: <brCategory> allows the business rules category (from 1 to 10) to which the BRDP is related to be recorded in the attribute brCategoryNumber
    • Attributes:
      1. id (O)
      2. changeMark (O)
      3. changeType (O)
      4. reasonForUpdateRefIds (O)
      5. brCategoryNumber (O) is the number (1 to 10) which represents the Business rule category to which the business rule is related.
        1. General business rules
        1. Data creation
        1. Product definition
        1. Data exchange
        1. Maintenance philosophy and concepts of operation
        1. Data integrity and management
        1. Security
        1. Legacy data conversion, management, and handling
        1. Business process
        1. Data output
    • Child elements:
      1. <title>
      2. <brCategoryDescription> see para 20
  20. Markup element: <brCategoryDescription> provides a description of the related business rules category. A project or organization can add any information to assist with understanding and relating to the business rules category or categories.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
    • Child elements:
      1. <para>
  21. Markup element: <s1000dSchemas> defines the relationship between a BRDP to one or a number of the S1000D Schemas.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)

        4. NOTE
        For the following attributes representing a schema:
        1. If the attribute is set to “1” then the BRDP relates or is associated with the Schema. (<1000dSchemas brexXsd=“1”>)
        2. If the attribute is set to “0” then the BDDP is not related to or associated with the Schema (<1000dSchemas brexXsd=“0”>)

      4. appliccrossreftableXsd (O)
      5. brDocXsd (O)
      6. brexXsd (O)
      7. checklistXsd (O)
      8. commentXsd (O)
      9. comrepXsd (O)
      10. condcrossreftableXsd (O)
      11. containerXsd (O)
      12. crewXsd (O)
      13. ddnXsd (O)
      14. descriptXsd (O)
      15. dmlXsd (O)
      16. faultXsd (O)
      17. frontmatterXsd (O)
      18. icnMetadataXsd (O)
      19. ipdXsd (O)
      20. learningXsd (O)
      21. pmXsd (O)
      22. prdcrossreftableXsd (O)
      23. procedXsd (O)
      24. processXsd (O)
      25. sbXsd (O)
      26. schedulXsd (O)
      27. scocontentXsd (O)
      28. scormcontentpackageXsd (O)
      29. pdateXsd (O)
      30. wrngdataXsd (O)
      31. wrngfldsXsd (O)
    • Child elements:
      1. None
  22. Markup element: <configAttributes> defines the relationship between a BRDP to one or a number of the S1000D configurable attributes.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)

        NOTE
        1. The configurable attributes indicating a BRDP has a relationship include the text “AttRelation” at the end of each attribute name. This is done to avoid redefinition of the types for configurable attributes defined in various S1000D Schemas.
        2. For the following attributes representing the configurable attributes of S1000D
          • If the attribute is set to “1” then the BRDP relates to or is associated with the configurable attribute. (<configAttributes caveatAttRelation=“1”>)
          • If the attribute is set to “0” then the BDDP is not related to or associated with the configurable attribute (<configAttributes caveatAttRelation=”0”>)

        1. accessPointTypeValueAttRelation (O)
        2. acronymTypeAttRelation (O)
        3. actionIdentTypeAttRelation (O)
        4. barCodeSymbologyAttRelation (O)
        5. brDecisionPointPriorityAttRelation (O)
        6. brSeverityLevelAttRelation (O)
        7. brStatusAttRelation (O)
        8. cancelCaptionAttRelation (O)
        9. caveatAttRelation (O)
        10. checkListCategoryAttRelation (O)
        11. circuitBreakerRefTypeAttRelation (O)
        12. circuitBreakerTypeAttRelation (O)
        13. colorAttRelation (O)
        14. commentPriorityCodeAttRelation (O)
        15. commercialClassificationAttRelation (O)
        16. crewMemberTypeAttRelation (O)
        17. crewStepConditionAttRelation (O)
        18. defaultBrSeverityLevelAttRelation (O)
        19. drillTypeAttRelation (O)
        20. emphasisTypeAttRelation (O)
        21. frontMatterInfoTypeAttRelation (O)
        22. frontMatterTypeAttRelation (O)
        23. functionAttRelation (O)
        24. functionalItemRefTypeAttRelation (O)
        25. functionalItemTypeAttRelation (O)
        26. genericPropertyTypeAttRelation (O)
        27. hazardousClassValueAttRelation (O)
        28. icnInfoItemTypeAttRelation (O)
        29. icnResourceFileTypeAttRelation (O)
        30. icnSourceFileTypeAttRelation (O)
        31. installationLocationTypeAttRelation (O)
        32. internalRefTargetTypeAttRelation (O)
        33. itemCharacteristicAttRelation (O)
        34. itemOriginatorAttRelation (O)
        35. limitUnitTypeAttRelation (O)
        36. listItemPrefixAttRelation (O)
        37. lowestLevelAttRelation (O)
        38. maintLevelCodeAttRelation (O)
        39. materialUsageAttRelation (O)
        40. operationTypeAttRelation (O)
        41. partCharacteristicAttRelation (O)
        42. partStatusAttRelation (O)
        43. partUsageCodeAttRelation (O)
        44. pmEntryTypeAttRelation (O)
        45. pmTypeAttRelation (O)
        46. productCategoryAttRelation (O)
        47. productItemTypeAttRelation (O)
        48. quantityTypeAttRelation (O)
        49. refTypeAttRelation (O)
        50. reqCondCategoryAttRelation (O)
        51. reqTechInfoCategoryAttRelation (O)
        52. resetCaptionAttRelation (O)
        53. responseTypeAttRelation (O)
        54. sbComplianceCategoryAttRelation (O)
        55. sbImpactTypeAttRelation (O)
        56. sbMaterialTypeAttRelation (O)
        57. sbTaskCategoryAttRelation (O)
        58. sbTimeComplianceTypeAttRelation (O)
        59. sbTopicTypeAttRelation (O)
        60. scoEntryTypeAttRelation (O)
        61. securityClassificationAttRelation (O)
        62. significantParaDataTypeAttRelation (O)
        63. skillLevelCodeAttRelation (O)
        64. skillTypeAttRelation (O)
        65. softwareClassificationValueAttRelation (O)
        66. softwareCustomizationStatusValueAttRelation (O)
        67. sourceCriticalityAttRelation (O)
        68. sourceTypeCodeAttRelation (O)
        69. sourcingTypeValueTypeAttRelation (O)
        70. submitCaptionAttRelation (O)
        71. supervisorLevelCodeAttRelation (O)
        72. supplyNumberTypeAttRelation (O)
        73. taskCodeAttRelation (O)
        74. thresholdUnitOfMeasureAttRelation (O)
        75. updateReasonTypeAttRelation (O)
        76. verbatimStyleAttRelation (O)
        77. quantityUnitOfMeasureAttRelation (O)
    • Child elements:
      1. None
  23. Markup element: <brDecisionPointText> defines a BRDP for the business rule.
    • For all business rule decision points that have unique identifiers starting with “BRDP-S1-”, the text captured in<brDecisionPointText> must be the text defined by this specification.
    • The only extension allowed for these BRDP is the reference to the place in the specification where the BRDP is defined.
    • Any explanatory information is to be captured in <brDecisionPointExplanation> (see para 26)
    • The text of a project/organizational specific BRDP must be defined specifically for the needs of the project and/or organization.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
    • Child elements:
      1. textElemGroup and
      2. listElemGroup as used in the element <para> in descriptive data modules
  24. Markup element: <brDecisionPointValueGroup> specifies what the BRDP is about.
    • For example, business rules decision points can be about the choice of available values, or about allowing the use of a concept, an element, or an attribute in a certain context.
    • It can also be used to define new values, etc. S1000D provides BRDP values for BRDP defined in the specification and captured inside the business rules template data module
    • The information mapped in the business rules template data module is based on S1000D text, Schemas and the default BREX
    • Attributes:
      1. brDecisionValueSelection (M), this attribute identifies whether a single or multiple values can be chosen. The allowed values are:
        1. “single”
        2. “multiple”
    • Child elements:
      1. <brDecisionPointValue> see para 25
  25. Markup element: <brDecisionPointValue> provides information on separate values for the BRDP.
    • Attributes:
      1. brDecisionValueAllowed (M), the allowed value for the BRDP. Multiple values can be defined, and this attribute is used to define each value.
    • Child elements:
      1. <para>, defines textual information about the value. For BRDP, the unique business rule prefix “BRDP-S1-”, is provided by the specification inside the business rules template data module.
  26. Markup element: <brDecisionPointExplanation> provides additional information on a BRDP, to that provided in the element <brDecisionPointText> (see para 23).
    • This can be information taken from the specification or any other information required by the project or organization.
    • For example, this could be questions arising when making a decision for a BRDP in a specific context of the project and/or organization.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
    • Child elements:
      1. <title>
      2. <para>
      3. <note>
      4. <figure>
      5. <multimedia>
      6. <foldout>
      7. <table>
      8. <caption>
  27. Markup element: <brAction> defines an action that is to be fulfilled to define a complete set of business rules decisions for the BRDP.
    • The information provided under the element <brAction> identifies the owner of the action and if it is complete or not.
    • If one or more child elements <brDecisionRef> (see para 8) are defined, then the element <brAudit> (see para 16) refers both to the BRDP it applies to and to one or more of its business rules decisions.
    • If the <brDecisionRef> (see para 8) is missing, then <brAction> is attributed only to the BRDP defined under the <brPara> (see para 7).
    • Multiple elements <brAction> within <brPara> (see para 7) make it possible to capture actions not only per BRDP but also per business rules decision.
    • Recording of one <brAction> for a group of business rules decisions defined within the same <brPara> (see para 7) is allowed.
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
      4. brActionOwner (M), the action owner. The text marked up with this attribute can be a person’s name, an organization name, CAGE code or combination of various. This can be decided case by case.
      5. brActionCompleted (O), of “yes” or “no” type, shows whether the action has been completed or not at the required date defined inside <brCurrentStatus> (see para 28). The absence of this attribute indicates the required date for the business rules is not reached yet, or the action has not been reviewed and evaluated since the last review.
      6. authorityName (O)
      7. authorityDocument (O)
      8. securityClassification (O)
      9. commercialClassification (O)
      10. caveat (O)
      11. derivativeClassificationRefId (O)
    • Child elements:
      1. <brDecisionRef> see para 8
      2. <title>
      3. <para>
      4. <note>
      5. <figure>
      6. <multimedia>
      7. <foldout>
      8. <table>
      9. <caption>
  28. Markup element: <brCurrentStatus> gives the status of the BRDP and/or related business rules decisions.
    • The business rules data module Schema defines only one <brCurrentStatus> (see para 28) for each element <brAudit> (see para 16).
    • Therefore, if the <brAudit> (see para 16) does not contain a reference to business rules decisions, then the business rules status also refers to the BRDP as a whole.
    • If there is an element <brAudit> (see para 16) for each business rules decision (or separate group of business rules decisions), then the status also describes a separate business rules decision (or a separate group of business rules decisions).
    • Attributes:
      1. changeType (O)
      2. changeMark (O)
      3. reasonForUpdateRefIds (O)
      4. brStatus (M), indicates the quality assurance status of the BRDP and/or business rules decisions to which the audit status applies.
        Allowable ValuesS1000D Interpretation
        “brst01”Unverified
        “brst02”First verified
        “brst03”Second verified
        “brst51” - “brst99”Available for projects
    • Child elements:
      1. <brDecisionRef> see para 8
      2. <responsiblePartnerCompany>
      3. <originator>
      4. <brRequiredDate> see para 29
      5. <brStatusDate> see para 30
  29. Markup element: <brRequiredDate> indicates the date when the business rules decision must be taken and/or the date that the BRDP must be addressed.
    • The business rules data module Schema defines only one <brCurrentStatus> (see para 28) for each element <brAudit> (see para 16)
    • Therefore, if the element <brAudit> (see para 16) does not contain any reference to business rules decisions, then the required date also refers to the BRDP as a whole.
    • If there is an element <brAudit> (see para 16) for each business rules decision (or separate group of business rules decisions), then the required date also applies to a separate business rules decision (or a separate group of business rules decisions).
    • Attributes:
      1. year (M)
      2. month (M)
      3. day (M)
    • Child elements:
      1. None
  30. Markup element: <brStatusDate> indicates the date when the business rules status was recorded.
    • The business rules data module Schema defines only one <brCurrentStatus> (see para 28) for each element <brAudit> (see para 16)
    • Therefore, if the element <brAudit> (see para 16) does not contain any reference to business rules decisions, then the required date also refers to the BRDP as a whole.
    • If there is an element <brAudit> (see para 16) for each business rules decision (or separate group of business rules decisions), then the required date also applies to a separate business rules decision (or a separate group of business rules decisions).
    • Attributes:
      1. year (M)
      2. month (M)
      3. day (M)
    • Child elements:
      1. None