On Monday the 6th of February 2017, the S1000D Working Group released v4.2 of the ASD S1000D Specification. Below is a summary of the key changes that have been implemented into Issue 4.2.
Business Rules and BREX
The most obvious thing to me was the focus around Business Rules (BRs), BR Decision Points (BRDPs), the automatic generation of a BREX DM, and new Information Code (IC) for business rules (024), so that you don’t have to use the BREX (022) info code (IC) any more.
Specific items worth a mention:
- Business Rules Decision Points –
- 23 new BRDPs
- 136 BRDPs deleted
- 128 BRDPs reworded
- Business Rules Mark up for BRDPs allow for the automatic generation of the BREX DM.
- Chapter 2.5.3 – Business Rules Index
- Chapter 188.8.131.52 – BREX data module – Coding a BREX DM
- Chapter 184.108.40.206 – Introduction to brDoc DM schema
- Chapter 8.4.1 – new Information Code 024 – Business Rules document
Other changes and updates of interest that were noted:
- New section for ICN metadata files (chapter 220.127.116.11) – the ICN metadata file contains the hotspot calls outs for the graphic.
- Techname (in IDstatus block DMTitle) now has an attribute securityClassification
- Chapter 18.104.22.168.16.1 – Front matter markup examples!
- Chapter 8.2.5 – new subsystem 70 to system 34 and system 85
- New Information Code IC 0A4 for Warnings CIR (Common Information Repository) and
IC 0A5 for Cautions CIR
- IPD – Operations restriction information – the element <restrictedOperationNote> has been expanded to support a new attribute of operationType (O) and can have the values of op01 to op99
- Learning – runtime. The notations.xml has been expanded to support declarations for CSS, FLA, JS and ZIP
- Schedule schema now supports preliminary requirements
- Reason for Update – this element now supports references to Data Modules, Publication Modules and External Pub References
To download the latest version of the specification and sample data, visit the S1000D.ORG site.
If you have any questions for the ADG Consulting Team regarding the new version of the specification, please email firstname.lastname@example.org