OMG Issue

SBVR15 — SBVR should use the latest MOF rather than sticking with MOF 2.0.

Key: SBVR15-38
OMG Task Force: SBVR 1.5 RTF

Key: SBVR15-38
Legacy Issue Number: 19674
Status: closed
Source: Adaptive ( Mr. Pete Rivett)
Summary:
SBVR should use the latest MOF rather than sticking with MOF 2.0.
Reported: SBVR 1.1 — Mon, 8 Dec 2014 05:00 GMT
Disposition: Resolved — SBVR 1.5
Disposition Summary:
State even more directly that SBVR uses MOF as a Syntax for SBVR Semantics + use MOF 2.4.2 and XM 2.4.2

see attached documents
Updated: Tue, 8 Oct 2019 17:48 GMT
Attachments:
- SBVR Clause 23 Edit Instructions for SBVR Issue 15-38 -- (Baseline text is AFTER Changes that are Part of SBVR Issue 15-08 Resolution).docx 165 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)
- SBVR Clause 25 Edit Instructions for SBVR Issue 15-38 -- (Baseline text is SBVR v1.4 Specification -- formal-17-05-05 (4).docx 18 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)
- SBVR Clauses 1-6 Edit Instructions for SBVR Issue 15-38 -- (Baseline text is AFTER Changes that are Part of SBVR Issue 15-08 Resolution.docx 74 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)
- SBVR-Issue-15-38 SBVR should use the latest MOF rather than sticking with MOF 2.0.docx 38 kB (application/vnd.openxmlformats-officedocument.wordprocessingml.document)