@@ -61,7 +61,11 @@ For more on the relationship between the RAFS DDMS and the forum Data Definition
### Forum Approval for the RAFS DDMS
-[DDMS Architectural Decision Record (ADR) #2](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/home/-/issues/2)
-[DDMS Architectural Decision Record (ADR) ](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/home/-/issues/2)#492
### Other Architectural ADRs
*[Proposal to Enhance to Medallion Architecture](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/rock-and-fluid-sample/rafs-ddms-services/-/issues/604)(604)
### RAFS DDMS Data Model - Content Schemas
...
...
@@ -192,7 +196,7 @@ For more technical and architectural documentation, please follow relevant links
In order to progress this solution, ExxonMobil, with EPAM, have:
- Set up a PMC project
- Submitted prototype code and architectural documentation for review and approval by the PMC and EA, as appropriate (including [DDMS ADR #2](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/home/-/issues/2), now approved)
- Submitted prototype code and architectural documentation for review and approval by the PMC and EA, as appropriate (including [DDMS ADR ](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/home/-/issues/2)#2, now approved)
- Collaborated with the appropriate Data Concepts/Definitions teams to align on which data modeling activity is solved by which OSDU solution and/or workstream, and to get SMEs aware of these efforts
Subsequent to this, as with any forum initiative, multiple companies and developers can contribute, coordinated though the appropriate OSDU PMC team. As of Aug. 2023, there are **recurring forum calls for this PMC Project** ([Thursdays, bi-weekly](https://www.opengroup.org/og_sduaggregatedcalendar)).
...
...
@@ -416,6 +420,6 @@ On ingest and data preparation, data loading applications can check the referenc
For some Sample Analysis Types (e.g. lab tests), part of the lab process is to perform the test at varying temperatures and pressures. In this case, a temperature is captured at each test step in the content schema. This is true, for example, for `PVT.MultiStageSeparatorTest`. In this scenario, there would be a single SamplesAnalysis WPC to catalog this dataset, which contains varying temperatures.
By contrast, for `PVT.ConstantCompositionExpansion` (CCE), the test process does not require varying temperatures. There is a single temperature value for the entire test; This is reflected in the content schema.
By contrast, for `PVT.ConstantCompositionExpansion` (CCE), the test process does not require varying temperatures. There is a single temperature value for the entire test; This is reflected in the content schema.
In cases in which additional partial CCE tests were run and partial datasets were produced in order to determine the appropriate saturation pressure for the main test, the temperature on those partial tests may indeed vary compared to the main test. In this scenario, each of those tests - the partial and the main tests - would be cataloged by their own instance of a SamplesAnalysis WPC. In order to associate these partial and main tests together if desired, best practice would be to use a form of [OSDU data lineage](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Guides/Chapters/05-Provenance.md#53-lineage-assertion), such as Lineage Assertions (the simpler choice) or Activity (a more detailed choice).
