Public Libraries

SDCStudio ships nineteen public projects: libraries of published components and models that any project can use without copying and without charge. Each library is built on an open standard, by reference, so a record made from its components carries that standard's meaning. Your own projects are private by default; only what you mark public leaves them.

The nineteen libraries

The Project name column is the exact name the catalog API and a Markdown template use; it is the name, not an identifier, and it is case-sensitive.

Library Project name What it covers
Default Default The domain-agnostic components every other library composes from: names, addresses, identifiers, dates, amounts, consent
ProvGov ProvGov Provenance and governance: the components that make a record governable, on W3C PROV
NIEM NIEM The National Information Exchange Model: justice, public safety, emergency management, immigration
FHIR FHIR HL7 FHIR clinical resources
NIH CDE NIH_CDE NIH Common Data Elements for clinical research
NIH PhenX NIH_PhenX A PhenX Toolkit instrument (180701) as a record
SINAN SINAN Brazil's notifiable-disease surveillance forms, in Portuguese
Imaging Imaging Imaging metadata records from the MIDRC data dictionary: study, series, annotation and radiology report, with DICOM's multi-valued attributes as list types (not pixel data)
Business Documents Business Documents OASIS UBL business documents as header and line records, Request for Quotation through Remittance Advice
Peppol Peppol Peppol BIS profiles as models over the business documents
UN/EDIFACT UN-EDIFACT The interchange record and the D.24A qualifier codes
Transport Documents Transport Documents UBL transport documents, eCMR, the DCSA electronic bill of lading, the FIATA eFBL
Traceability Traceability GS1 EPCIS 2.0 events for supply-chain traceability
ISO 20022 ISO 20022 Payment and financial messages as records
CRM CRM Customer relationships: account, contact, lead, opportunity, activity, case, campaign, consent on the W3C Data Privacy Vocabulary; vocabularies at semanticdatacharter.com/vocabularies/crm
ERP ERP Master data: customer, supplier, item, price list, location, inventory balance, employee, on the Open Applications Group's nouns; vocabularies at semanticdatacharter.com/vocabularies/erp
Ledger Ledger The chart of accounts, the journal entry and its lines, on XBRL Global Ledger
Human Resources Human Resources Organizational unit, job, position, work assignment, pay, absence, time, performance, requisition, candidate, application, benefits, learning, competency, on HR Open Standards 4.5 by reference; vocabularies at semanticdatacharter.com/vocabularies/hr
FOCUS FOCUS Cloud, SaaS and AI cost, usage and billing on the FinOps Open Cost and Usage Specification 1.4: charge, tags, contract applications, billing period, contract commitment, invoice detail, and the delivery that asserted them; a correction is a new record, so the charge history is never overwritten; vocabularies at semanticdatacharter.com/vocabularies/focus

The component counts change as libraries grow; the public catalog API gives today's count for any library, and the pilot pages on semanticdatacharter.com show how pilots compose from them.

curl -s "https://sdcstudio.axius-sdc.com/api/v1/catalog/components/?project=Human%20Resources&page_size=1"

Three ways to use a library component

Reference it. A published public component can be a member of your cluster as it is, from any library, with no copy and no charge. The Cluster Wizard's Add Components step lists every published public component beside your own; the Model Wizard's Data Cluster picker lists published public clusters. In a Markdown template, name the component with **ReuseComponent**: @Project name:Component label, for example @NIEM:StateUSPostalServiceCode, or by identifier with **Reuse**: <ct_id>; see Template Format. A referenced component keeps its identity: a record made from your model carries the library's definition, and anyone receiving the record resolves it to the same schema.

Copy it. When a library component is close but not right, Copy on its detail page puts an unpublished copy into your project, prefixed COPY --, derived from the original and carrying its semantic links. Rename it, change it, publish it. A copy is a new component: it costs nothing to make, and a record made from it carries your definition, not the library's. See Copy and Retire.

Create your own. The Component Wizard, with the library open in another tab for the labels and the links worth matching. A new component is 100 credits at creation; see Wallet and Billing.

Mixing libraries in one model is normal: a clinical record can take its patient from FHIR, its consent from Default and its provenance from ProvGov.

Choosing a starting point

  • Justice, public safety, emergency management: NIEM, with Default for the generic parts.
  • Clinical care: FHIR; clinical research: NIH CDE, NIH PhenX; public-health surveillance in Brazil: SINAN; imaging: Imaging.
  • Trade and logistics: Business Documents for the documents themselves, Peppol where a BIS profile is required, UN/EDIFACT for interchanges, Transport Documents for carriage, Traceability for EPCIS events, ISO 20022 for payments.
  • The business itself: CRM for customers, ERP for master data, Ledger for the books, Human Resources for people, FOCUS for cloud, SaaS and AI spend.
  • Anything else: Default, which every other library is composed from, and ProvGov for the governance of any record.

What is public and what is private

A project is private unless it is a library. A component has a Public flag, off by default; a public published component appears in the catalog and in every other user's pickers, and its definition can be referenced by anyone. A model's visibility follows its project. Publishing is not the same as making public: a published private component is usable by your project and your team only.

To share your own work, set Public on a published component, or add people to your project's team; see Teams. Anyone who can view a published component can copy it into a project they can build in; nobody can change it.

Next steps