-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Use Case
As we move beyond always rendering the ADAPT Standard as a consolidated dataset, the "root" terminology is inappropriate and potentially confusing.
Current Processes
Most anything smaller than an ADAPT root (dataset) is not being exchanged in ADAPT but rather as custom schemas.
Touchpoints
The goal is to use BIEs from Connect Center to render purpose-built schemas leveraging ADAPT components as true core components.
Proposed Change
Rename adapt-root-schema to adapt-dataset-schema
Change these lines:
"$id": "https://adaptstandard.org/root/2.0.2", (root becomes dataset)
(OLD) "description": "When ADAPT data is consolidated into a single dataset (usually as physical files), the Root component acts as the top level entity that contains all available data. It is serialized as "adapt.json." Note that it is also possible to use json representations of individual ADAPT components in a distributed service architecture without the container entities (Root, Catalog, Documents, etc.)",
(NEW) "description": "ADAPT data when consolidated into a normalized container for use as a bulk export. It is serialized as "adapt-dataset.json."",
Metadata
Metadata
Assignees
Labels
Type
Projects
Status