@@ -224,7 +224,7 @@ Subject matter experts in the OSDU Forum, including petrophysicists and geochemi
### 2. Why are Rock and Fluid Samples not incorporated into the Wellbore DDMS?
1.[In OSDU](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-(C)/Reference-Architecture/Functional-Architecture/Data), DMS (aka CSS) (shape of data) is different from DDMS (optimized to a specific business domain)
1.[In OSDU](https://community.opengroup.org/osdu/documentation/-/wikis/OSDU-\(C\)/Reference-Architecture/Functional-Architecture/Data), DMS (aka CSS) (shape of data) is different from DDMS (optimized to a specific business domain)
2. Even if the "shape of data" (e.g. array data, at least partially solved by Parquet) is similar to well logs and even re-usable, a separate DDMS is needed for a separate business domain
3. Rock and Fluid Sample Data have been identified as a separate domain from Wellbore by both the SMEs in the Samples Data Definitions teams (an [output of a January workshop, slide 6](https://opensdu.slack.com/archives/C028RLMJVJP/p1676385721498969)), and by the Domain Driven Design team ([spreadsheet](https://gitlab.opengroup.org/osdu/subcommittees/data-def/docs/-/blob/master/Design%20Documents/WIP/DomainDefinitions/Domains-and-datatypes-Registry.xls)). Reasons include: Not all rock or fluid samples come from wellbores, and the Rock and Fluid Domain deals mostly with multi-faceted analysis on physical specimens rather than measurements along a wellbore
4. It is broadly recognized that Domains have inter-dependencies. OSDU must develop a methodology for domain-and-DDMS interactions rather than merging domains into a single DDMS when inter-dependencies are observed.
...
...
@@ -375,6 +375,6 @@ Remaining content schemas (\~26x) are usable, but have not undergone this same l
As of the M25 (March 2025) release, the Meta block of the content schemas is used to identify and define the unit of measure for each relevant attribute in the schema. This is similar to its use in the catalog schemas.
However, this Meta block in the DDMS content schemas does not contribute to the "normalization" of any units of measure in the RAFS DDMS. The RAFS DDMS does not today do unit of measure normalization. It is possible that in the future, the RAFS DDMS will do unit of measure normalization like the Core Services do with catalog schemas; That question is under discussion at this time.
However, this Meta block in the DDMS content schemas does not contribute to the "normalization" of any units of measure in the RAFS DDMS. The RAFS DDMS does not today do unit of measure normalization. (If normalization is needed today, it can be done by the consuming application.) It is possible that in the future, the RAFS DDMS will do unit of measure normalization like the Core Services do with catalog schemas; That question is under discussion at this time.
You can read more about how the catalog schemas using this "meta" block and how it relates to normalization in the OSDU Core Services [here in the OSDU Schema Usage Guide](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Guides/Chapters/04-FrameOfReference.md)(Frame of Reference section).
