Documentation Center

New features and enhancements in Contenta S1000D 5.7

This section lists features and enhancements that were introduced in Contenta S1000D 5.7.

S1000D BREX support enhancements

The following enhancements were made to the S1000D Validate tool.
  • Support of XPath 2.0 to validate S1000D Issue 4.0 and later data modules (DMs)

    Contenta S1000D 5.7 supports XPath 2.0 to validate S1000D Issue 4.0 and later DMs against their BREX rules. This version of XPath includes an XPath 1.0 compatibility mode, which is used to validate S1000D Issue 3.0 DMs against their BREX rules.

  • Checking for context-sensitive BREX rules

    The Validate BREX tool now checks for context-sensitive BREX rules, that is, rules that apply only to DMs that use the specified schema. For example, rules that apply only to Issue 4.2 procedural DMs will not be evaluated when validating DMs of other types or issues. This enhancement helps the tool run more efficiently and to report only those results that apply to DMs using the specified schema.

  • Improved detection of duplicate XPath expressions in BREX rules

    BREX results should no longer contain the same BREX rule reported more than once.

Issue 4.2 Derivative Classification support

Enhancements were made to support the optional derivativeClassification markup introduced in Issue 4.2 of the S1000D specification, which provides a way to keep track of the history of classification actions taken on an entire module (DM, PM, SCPM) or on part of a module. S1000D Issue 4.2 Derivative Classification includes the following new pieces of XML markup, each of which is optional.
  • A <derivativeClassification> tag in the <identAndStatusSection>, which may contain one or more <classificationActionGroup> tags, each of which contains the history of a single classification action taken on a chunk of data (an entire module or part of a module).
  • A derivativeClassificationRefId attribute that refers to an id attribute on a <classificationActionGroup> tag, using XML's ID/IDREF construct.
The following enhancements were made to support Derivative Classification markup.
  • The Contenta S1000D upgrade program adds a new property sheet field, Security DerivativeClass RefId, to the DModule, PModule, and SCORMContentPackage objects.
  • S1000D Upload and Arbortext (or other editor) Check In functionality has been modified so that if the optional derivativeClassificationRefId attribute is present in the <security> tag of the <identAndStatusSection> in an Issue 4.2 module, its value is extracted into the new property sheet field.
  • When running PM Builder on an Issue 4.2 PM, a new field, security derivativeClassificationRefId, is displayed in the PM Properties form.
  • The following changes were made to PM Builder.
    • When the user fills in the new security derivativeClassificationRefId field, PM Builder checks whether the entry is a valid XML IDREF (NCName). If the entry is a valid IDREF, the derivativeClassificationRefId attribute on the <security> tag of the <identAndStatusSection> is added or updated, and the IDREF is also stored in the PM's Security DerivativeClass RefId property sheet field.
    • When run on an existing Issue 4.2 PM, PM Builder checks for the optional derivativeClassificationRefId attribute on the <security> tag of the PM's <identAndStatusSection> and populates the security derivativeClassificationRefId field accordingly. PM Builder also checks for the optional <derivativeClassification> tag and preserves the tag and its contents along with other optional markup in the PM's <identAndStatusSection>, which is also preserved.
    • When run on an existing Issue 4.2 PM, PM Builder checks for unsupported markup in the PM's <content> section, including the derivativeClassificationRefId attribute (and the other security/classification attributes) on any tag except the optional <security> tag under <pmRef> tags.

Support for S1000D ACT Catalog data modules

This version of Contenta S1000D includes support for the ACT Catalog DM added in S1000D Issue 4.1. An ACT Catalog DM facilitates the use of multiple ACT/PCT/CCT DMs within a project or organization by defining how product attributes in two or more ACT DMs (and by inference, products in PCT DMs) relate to one another. This functionality enables the coordination of product attributes or conditions from multiple sources, defined as an integrator and one or more suppliers. The relationship between the integrator and supplier(s) is hierarchical, with the integrator at the higher level, and thus responsible for creating and maintaining an ACT Catalog DM.

An ACT Catalog DM is a top-level DM and is thus not directly referenced by any other module. It supports the following types of relationships between multiple ACTs or between multiple CCTs.
  • Use of supplier product attributes or conditions in integrator DM applicability annotations. For example, the aircraft data provider (integrator) can express the applicability of some procedures depending on the engine model (where the engine model data is coming from a supplier).
  • The ability to filter both integrator and supplier DMs by an integrator product attribute.
To enable this enhancement, the S1000D Publish tool has been modified as follows.
  • If the CSDB contains an ACT Catalog DM with the same modelIdentCode as the PM's ACT DM, that ACT Catalog DM and additional referenced applicability DMs are exported along with other modules and graphics in the publication.
  • When the user sets applicability for Publish, ACT Catalog information is displayed in the ACT/CCT tables and applied during applicability filtering.

See the Publishing S1000D content topic in the Using Contenta S1000D section of this documentation for more information about the changes to the S1000D Publish tool.

Also, the S1000D DDN Export tool may be optionally configured to include an ACT Catalog DM and additional referenced applicability DMs. See the Exporting a DDN topic in the Using Contenta S1000D section of this documentation for more information about using the DDN Export tool with an ACT Catalog DM.

Support for SVGZ graphics

Contenta S1000D databases and tools have been enhanced to support SVGZ (compressed SVG) graphic files. To enable search of SVGZ graphics, add SVGZ to the hyphen-delimited list of object types available for Advanced Search in the cw_searchObjectTypes AppData setting under the {Global} > content@web > Settings path.

S1000D Publish to LiveContent S1000D enhancements

S1000D Publish now supports additional LiveContent S1000D features. If a user optionally selects any of these new options via S1000D Publish, those selections are passed to LiveContent S1000D.

The following enhancements were made to the LiveContent Settings section of the Contenta S1000D Publish user interface to support new features introduced in SDL LiveContent S1000D.
  • A new drop down menu allows you to specify how titles are displayed in the IETM table of contents. You can select from the following options.
    • TechName and InfoName (the default)
    • InfoName Only
    • TechName Only
  • A new drop down menu allows you to specify whether API results in an IETM will be returned in UTF-8 (the default) or ISO-8859-1 character encoding.
  • A new check box allows you to specify whether graphics and multimedia objects will be encrypted.
  • The CGM Viewer UI option was removed from the standard LiveContent settings in the S1000D Publish user interface. By default, LiveContent S1000D uses the PTC IsoView viewer to display CGMs. However, you can still customize LiveContent S1000D to use a different CGM viewer if needed.

In addition, you can now specify a port other than the default of 2245 for LiveContent S1000D.

To enable these enhancements, a number of changes to the Contenta S1000D PublishConfiguration.xml and PublishConfiguration_Unix.xml configuration files were made, including the addition of a new LiveContentPort property, which is set to 2245 by default.

Security enhancements

Many of our third-party libraries were updated to recent versions to keep current and reduce security risks. In addition, as part of our Java security enhancements, our Java-based installers no longer leave a JRE on the file system. When running the uninstall program for some our products, you must have a JRE on the system path that meets Contenta S1000D 5.7 minimum requirements (refer to our Platform Requirements). This requirement applies to Contenta S1000D and Contenta S1000D Editor Extensions.

Upload tool changes

A new tool, S1000D Upload Codes, has been added for uploading DMRL/CSV files (that is, codes). This tool interface contains links to the Define and Manage tools. The existing S1000D Upload tool has been modified to upload only files, and not codes (CSVs), and to remove links to the Define and Manage tools.

S1000D Upload and Check In enhancement

When uploading Issue 4.1 and later PMs and SCPMs, the S1000D Upload and XML editor Check In tools now extract <brexDmRef> tag contents into the new Business Rules Reference property sheet field, as they do for DMs.

Added Issue 4.2 support to SDL S1000D Foundation Suite

The SDL S1000D Foundation Suite has been updated to generate Issue 4.2 modules. The S1000D Foundation Suite is a separate product from Contenta S1000D that generates initial data modules (DMs) that can be uploaded into a Contenta S1000D CSDB. It simplifies the process of beginning a new Issue 4.0.1, 4.0.2, 4.1, or 4.2 S1000D project by creating all the starting-point data modules required for a new S1000D project, effectively defining the structure of the project.

For further information about this enhancement, refer to Using the SDL S1000D Foundation Suite in the Contenta S1000D documentation.

Contenta S1000D new database changes

The default language for new Contenta S1000D databases has been changed to United States English (EN-US). Previously, the default was United States Simplified Technical English (SX-US). The Contenta S1000D database .dmp files and default AppData settings reflect this change. In addition, new database templates for S1000D Issues 4.0 and later are delivered with the default language set to EN-US.

New customers must use dbimport to import the appropriate s1000d.dmp file, which is located at:
  • Contenta_home/S1000D_samples/databases/Contenta57_MSSQLServer_database
  • Contenta_home/S1000D_samples/databases/Contenta57_Oracle12c_database

Contenta S1000D database upgrade changes

This section lists the changes made to your existing Contenta S1000D databases when you upgrade them to Contenta S1000D 5.7. If you are upgrading from a release earlier than 5.5, contact SDL Professional Services at mailto:ProServRequest@sdl.com to discuss upgrade services for your implementation.
  • A new object type, SVGZ (based on the Graphic object type) is created.
  • The MIME Type property sheet field for SVGZ objects has been set to image/svg+xml.
  • A New SVGZ creation tool has been added to the Container, Group, Model, SystemDifferenceCode, System, Subsystem, Subsubsystem, Project, ContentRoutingProject, and Dispatcher objects.
  • The mimetypeMappings AppData setting has been updated to add a Name/Value pair with Name set to image/svgz+xml and Value set to .svgz.
  • A new property sheet field has been added to DModule, PModule, and SCORMContentPackage objects. Field name: Security DerivativeClass RefId.
  • A new property sheet field has been added to PModule and SCORMContentPackage objects. Field name: Business Rules Reference.

For customers upgrading from Contenta S1000D version 5.6, there is no Contenta core database upgrade program; customers upgrading from previous versions must run the Contenta upgrade_56 database program before running the Contenta S1000D upgrade_S1000D_57.pl database program to upgrade their Contenta S1000D databases.