Update home - formatting authored by Daniel Perna's avatar Daniel Perna
...@@ -354,18 +354,18 @@ For reference, the following are the original, temporary, Fluid Model-related cu ...@@ -354,18 +354,18 @@ For reference, the following are the original, temporary, Fluid Model-related cu
### 11. Are all the content schemas equally mature (Feb. 2025, M25)? ### 11. Are all the content schemas equally mature (Feb. 2025, M25)?
No, as of Feb. 2025, not all content schemas are equally mature. Those deemed "high priority" (18x) by multiple companies are classified as **"mature"**. These have undergone maturing which includes: No, as of Feb. 2025, not all content schemas are equally mature. Those deemed "high priority" (18x) by multiple companies are classified as **"Mature"**. These have undergone maturing which includes:
* multi-company review * multi-company review
* addition of detailed attribute descriptions * addition of detailed attribute descriptions
* creation and refinement of "MECE" reference list values with complete and precise attribute descriptions * creation and refinement of "MECE" reference list values with complete and precise attribute descriptions
Remaining content schemas (\~26x) are usable, but have not undergone this same level of review. Nonetheless multiple companies represented in RAFS Data Definitions, along with the PMC, have decided to release these with a status of **"pending-review"** for the following reasons: Remaining content schemas (\~26x) are usable, but have not undergone this same level of review. Nonetheless multiple companies represented in RAFS Data Definitions, along with the PMC, have decided to release these with a status of **"Pending Review"** for the following reasons:
* they can be adopted today, with adopters knowing that in the future data migration to more mature schemas may be necessary * they can be adopted today, with adopters knowing that in the future data migration to more mature schemas may be necessary
* they can be tested today, with SMEs, data engineers, and data managers reviewing them in order to understand any needed enhancements, which will accelerate their move to "mature" via feedback * they can be tested today, with SMEs, data engineers, and data managers reviewing them in order to understand any needed enhancements, which will accelerate their move to "mature" via feedback
**The status of "mature" versus "pending-review" for each schema is communicated in at least two ways:** **The status of "Mature" versus "Pending Review" for each schema is communicated in at least two ways:**
* In the Supported Data Types wiki page * In the Supported Data Types wiki page
* In the schemas themselves under the attribute called `x-osdu-review-status` * In the schemas themselves under the attribute called `x-osdu-review-status`
\ No newline at end of file