OASIS-OP-Admin
commented
3 days ago Hi @sparrell,
I sent your question to Jamie and here was his response:
-
If OSIM (or any standard) says, normatively, for function X, go use UBL (or another standard), then each one is implemented according to its own license terms. An implementer will ask themselves, can I use RF on Limited Terms licensing for conformant UBL stuff? (Probably, yes.) Can I use Nonassertion licensing for conformant OSIM stuff? (Again, probably, yes.) The two licenses do not 'merge' or affect each other just by reason of differing adjacent modules both being implemented, so long as each of the uses stays within its own applicable conformance clauses.
-
Just as an implementer of STIX also is using JSON (under IETF RFC licensing), and other standards from other places as well. But the STIX spec does not re-define JSON, it just says, use JSON notation, see RFC 8259, ECMA-262, etc.
-
If, on the other hand, OSIM actually tried to re-state and embed elements of UBL, it would need to go get them re-contributed and re-licensed under OSIM's license. OASIS TC projects do not have the automatic right to "borrow" pieces from each other -- each piece is licensed by ITS contributors for use in ITS TC. So incorporation by reference is a better strategy, most of the time.
Does this answer your question?
UBL is an OASIS Standard specifying "a generic XML interchange format for business documents", some (many) of which are relevant to supply chain. UBL specifies the (normative) XML and has an non-normative associated data model.
OSIM intends to create information models.
UBL operates under the RF on Limited Terms mode of the OASIS IPR Policy.
OSIM operates in the Non-Assertion Mode, as described in the OASIS IPR Policy.
What does this mean wrt OSIM making use of UBL information (eg what if we wanted to use some of their definitions from their spec? What if we made an info model based in part on their non-normative data model?).