tgf — archive

[David Webber]

John, I would note that the OASIS BCM is an existing OASIS Member approved standard and precedence for TGF. OASIS realized at that time that standards did NOT have to include XML schema documents and be machine testable for conformance. I would point to further work - such as the NIEM approach for enterprise information exchanges using XML that is being widely adopted. The Naming and Design Rules are derived from ISO 11179 and ebXML CCTS - and contain several semantic guidelines for which you cannot write code based checks - human inspection and acceptance of linguistic and industry domain common practice is needed (e.g. is something a tariff, a surcharge, or a weight). NIEM too avoids conformance - because it simply cannot be fully asserted or tested. The best you can say is something is aligned with and is consistent with NIEM. Providing guidance to organizations so they can set their own expectations and requirements and methods for testing alignment. Therefore I would strongly concur with John here, OASIS needs tools beyond middleware XML that inform and empower organizations to build better processes for developing solutions. The marketplace is looking to standards organizations to provide this guidance. Thanks, David Webber