Hi Implementers,
I have a question regarding the use of v0 archetypes in production systems. The Ocean OPT validator implements the archetype ID scheme where v0 is not a valid archetype ID. I think this was changed recently, in ADL2.0 I think? We deliberately did this to ensure we were not using draft archetypes in production systems. We are now looking at using some of the latest draft archetypes in a couple of projects and need to make a decision on how to proceed.
Do others allow v0 archetypes in their operational systems?
Rather than making changes to support v0 archetypes, we are thinking of changing these v0 archetypes to v1, perhaps using some pseudo namespacing scheme considering we are still using ADL 1.4, which unlike ADL 2.0 doesn’t have namespacing? I don’t want to simply change to v1 as this will cause conflicts when these v0 archetypes finally get published as v1.
Does anyone already use a pseudo namespacing scheme when using ADL 1.4 archetypes?
Regards
Heath
Heath Frankel
Enterprise Platform Architect
Ocean Informatics Pty Ltd
E: heath.frankel@oceaninformatics.com
M: +61 (0) 412 030 741