17 July 2016 — ISO/TC 154 was a major participant and contributor to the ISO/IEC/ITU/UNECE MoU/MG PoC on Semantic Interoperability (PoC-SI) project. As the creators of the original ISO/TS 16668:2000 – Basic Semantics Register (BSR), ISO/TC 154 members offered their past experience which resulted in the successful completion of the PoC-SI project.
Because ISO/TC 154 members do not want to see the rules and guideline, they helped develop during the PoC-SI project, being forgotten, they initiated a new work item within ISO/TC 154 to ensure that instead their work will be persevered so that any BST system, based on SKOS, that may be built in the future does not have to start from a blank sheet.
ISO/NP TS 21887 – “The Business Semantic Thesaurus (BST)” will provide the background, guidelines and rules for the development of the various SKOS artifacts. It is not a system in itself that is created and maintained by ISO/TC 154. Anyone who wants to build such a system can use the proposed rules and guidelines, the same way “ISO/TS 16668 BSR” was used by an external party to build a repository 15+ years ago.
To eliminate any confusion between the UN/CEFACT Core Component work, ISO/TC 154 included the following Q&A in the new work item proposal:
Is the BST in competition with UN/CEFACT’s Core Component Library (CCL)?
No! The CCL is a library of reusable data components addressing data harmonization. The BST compliments the CCL, and similar libraries such as the UBL component library, by allowing links between the libraries and thesaurus to provide multilingual definitions that are in “every day” language, not specific to one domain nor use technical jargon.
Is the BST replacing “ISO/TS 16668:2000 – Basic Semantic Register (BSR)” which was withdrawn by ISO/TC 154?
No! The BSR was withdrawn because of the emerging work on the ebXML Core Component Technical Specification (CCTS) which became ISO/TS 15000-5 and its associated UN/CEFACT Core Component Library (CCL). The BSR’s purpose was to align and harmonize data among and between existing directories by providing the pivotal data for the cross-referencing of equivalent data in various directories which are maintained by different agencies. This function has been replaced by the CCL which is a library of reusable data components addressing data harmonization
Does ISO/TC 154 have any plans to create its own implementation of the BST?
No! ISO/TC 154 has no plans or mandate to do so. ISO/TC 154 reason for creating the BST technical specification is to preserve the work done by the ISO/IEC/ITU/UNECE/MoU/MG “Proof-of-concept on Semantic Interchangeability” project. By doing so, should the user community decide to create a BST, it does not have to start from a blank sheet, but instead has the benefits to use this technical specification.