-
Key: SYSMOAS_-11
-
Status: closed
-
Source: International Business Machines ( Mr. Eran Gery)
-
Summary:
it is unclear if queryConformace implies derivedProperties conformance. In other words, does the query service provider need to support derived properties or not.
-
Reported: SystemsModelingAPI 1.0a1 — Mon, 28 Aug 2023 13:57 GMT
-
Disposition: Resolved — SystemsModelingAPI 1.0b3
-
Disposition Summary:
Add clarification on QueryConformance and DerivedPropertyConformance
Section 2 (Conformance) already states the following for DerivedPropertyConformance.
In order to demonstrate Derived Property Conformance, a service provider must do the following when ProjectDataVersioningService.createCommit operation is invoked.
1. Compute or verify all derived properties for Element data that is created or updated in the commit
2. Include the derived properties in the response, i.e. DataVersion.payload should include derived properties for Element data.Section 2 (Conformance) already states the following for QueryConformance.
A Service Provider must implement all the operations in the Query Service, and demonstrate that the implementation successfully passes all the QueryService Conformance Test Cases (see Section A.4) and Cross-Cutting Conformance Test Cases
This proposal adds a supporting text under QueryConformance in section 2. This supporting text is available in the Revised Text field of this proposal.
-
Updated: Sat, 19 Jul 2025 19:07 GMT
SYSMOAS_ — Query conformance and derived properties
- Key: SYSMOAS_-11
- OMG Task Force: Systems Modeling API and Services (SystemsModelingAPI) 1.0 FTF 2