3. Main Goal of Version 5: Internationalization
Most companies work not only within the EU,
thus a SDScom must support other regions
(Steering Committee, 17. October 2018)
To stay educative, some parts of the XML structure
need to be reworked to add other regions
Since common data is represented only once, a
„Datasheet“ is no longer one SDS, but a product
dataset.
4. National Extensions for Version 5
●
EU plus DE
●
CH
●
NO
●
JP (incomplete)
●
TR (incomplete)
●
US (not yet)
●
CA (not yet)
Release of Version 5.0: October 2019
6. Rework: InformationFromExportingSystem
●
InformationFromExportingSystem is moved to a
separate node, once per DatasheetFeed.
●
Good for SystemUsedInPreparation,
DateGeneratedExport etc. - but what about Language?
– One language per file
– One language per SDS
– Multiple languages per (multi-region) SDS
Language != Country!
9. Classification and Ingredient List
●
Composition is region specific: Due to differing cut-off
limits on CMR classification, legal classification lists,
SCLs in Europe etc., not only the product classification,
but also the list of ingredients may differ (and thus
needs to be repeated for every region).
10. Move Ingredient-specific Information
●
While information on chemical inventories is usually
printed in section 15, it is relevant per ingredient, and
thus belongs in the composition list in section 3.
●
This is true for most other data assigned to
ingredients, e.g. limit values!
11. Transport
●
Transport info needs to be structured by carriers: Just
like in the good old days of pre-REACH EU SDSs!
●
Since region-specific transport info exists, it makes
most sense to apply this to IMDG and IATA-DGR as well.
●
It is only Europe that deviates from this structure in
printout. Compliant SDS template is still possible with
version 5!