This initiative emerged from the recommendations provided by STAR members during the March 2017 STAR General Session Meeting.
High Level STAR XML BOD Architecture Refactoring Proposal
• Full refactoring and clean-up of STAR XML BODs based on OAGIS 10, branching off into STAR 6.
• For an extended transitional period, in parallel maintain the current STAR 5 branch with extensions and updates
(similar to the transition to STAR 5 in 2006).
• Aim is to secure future relevance of STAR as an industry B2B standard by
• Ensuring alignment with the latest major OAGIS release:
• Improved support for future Mobile/Cloud/REST API/JSON expansions of STAR.
• Compliance with updated UN/CEFACT 3.0 definitions (incl. low level components, type definitions and code lists)
• Cleaning up and harmonizing BODs for more consistent data modeling to make STAR faster to implement and easier to use:
• Consistency in naming and design rules (eg.OAGIS verb usage and language handling)
• Increased reusability of components between BODs, eg.
• naming of nouns (eg.prices in order, shipment and invoice)
• consistent usage of proprietary elements vs. more general structures (name value pairs)
• Removal of ambiguous and/or deprecated content, based on current members usage of existing BODs
• Incentivizing former and new members to engage with STAR.
This presentation describes the background and details of the proposed project.
Questions and Answers
Q: Why do we need to migrate to OAGIS 10, can we just refactor and clean-up the existing global components and BODs?
A: Currently STAR 5 implements OAGIS 9. In order for STAR to align with the latest B2B global standards, the recommendation is to adopt OAGIS 10.
Q: Can you provide examples of latest ISO standards that the current STAR XML architecture does not support?