TLA Toolbox now has an alpha linked data workspace for Sharable Competency Definitions. It sits beside the ordinary competency list. The list is still where you edit competencies and rubrics. Linked data is where a framework becomes a publishable, traceable set of concepts that other systems can cite.
Each framework gets a stable scheme address of the form https://w3id.org/tla/scd/fw-{framework-id}. Each competency gets a concept address under that scheme. Renaming the framework does not change those addresses. Existing IEEE SCD fields, imported IRIs, and rubric level identifiers stay as they are. Exports keep their original @id values and add a canonical schema:url. New publication documents add SKOS, PROV-O, Dublin Core, and schema.org. This is not a separate triple store and not a SPARQL endpoint. Validation is the application's own rules.
Open Linked data in the sidebar, pick a framework, and open its workspace. You can set preferred, alternative, and hidden labels, including other languages, plus definitions, notation, attribution, source or derivation, and a license. Broader and related links stay inside the same framework. Narrower links and the reverse of related are filled in for you. Saving checks language tags, URIs, duplicate labels, hierarchy cycles, and cross-scheme mistakes. A draft can be saved without a license or a source. Publish cannot.
Publication asks for an open license URI and a source or derivation URI on the framework and on every concept. The license is the address of the license, such as https://creativecommons.org/licenses/by/4.0/, not a pasted legal paragraph. Creative Commons hosts the text. Choosing it here is your declaration that these definitions are offered under that license. NonCommercial and NoDerivatives licenses are flagged for review rather than treated as open. After a valid publish, the framework is public and its definitions lock. People can read the scheme and each concept as HTML, JSON-LD, or Turtle, including through the w3id addresses, which redirect to tlatoolbox.com. A private framework returns not found to anyone who is not signed in.
Mappings between frameworks are proposals until a manager of the source framework accepts them. Proposed and rejected mappings are not treated as equivalence. Exact matches can be followed through. A close match is optional and only one step. Broad, narrow, and related matches do not stand in for the concept. Authority profiles let a consumer set a preferred framework order. If two candidates are equally preferred, the result is ambiguous instead of a silent winner.
Rubric Assertion Profiles (aka RAP Sheets) can be migrated so recognized local references become the canonical w3id URI while the old id is kept as legacyId. That migration touches only the current user's recognized references. It does not rewrite historic xAPI statements.
The workspace also offers fictional private sample data, so you can try labels, mappings, and resolution without writing into a real framework. Sample data is opt-in. Signing in does not create it.
TLA Toolbox remains public, with no fee planned. The linked data workspace is an alpha on top of IEEE 1484.20.3 SCD, meant for people who need competency definitions that can be shared, versioned, and resolved across frameworks without losing the rubric and the identifiers they already have.
Each framework gets a stable scheme address of the form https://w3id.org/tla/scd/fw-{framework-id}. Each competency gets a concept address under that scheme. Renaming the framework does not change those addresses. Existing IEEE SCD fields, imported IRIs, and rubric level identifiers stay as they are. Exports keep their original @id values and add a canonical schema:url. New publication documents add SKOS, PROV-O, Dublin Core, and schema.org. This is not a separate triple store and not a SPARQL endpoint. Validation is the application's own rules.
Open Linked data in the sidebar, pick a framework, and open its workspace. You can set preferred, alternative, and hidden labels, including other languages, plus definitions, notation, attribution, source or derivation, and a license. Broader and related links stay inside the same framework. Narrower links and the reverse of related are filled in for you. Saving checks language tags, URIs, duplicate labels, hierarchy cycles, and cross-scheme mistakes. A draft can be saved without a license or a source. Publish cannot.
Publication asks for an open license URI and a source or derivation URI on the framework and on every concept. The license is the address of the license, such as https://creativecommons.org/licenses/by/4.0/, not a pasted legal paragraph. Creative Commons hosts the text. Choosing it here is your declaration that these definitions are offered under that license. NonCommercial and NoDerivatives licenses are flagged for review rather than treated as open. After a valid publish, the framework is public and its definitions lock. People can read the scheme and each concept as HTML, JSON-LD, or Turtle, including through the w3id addresses, which redirect to tlatoolbox.com. A private framework returns not found to anyone who is not signed in.
Mappings between frameworks are proposals until a manager of the source framework accepts them. Proposed and rejected mappings are not treated as equivalence. Exact matches can be followed through. A close match is optional and only one step. Broad, narrow, and related matches do not stand in for the concept. Authority profiles let a consumer set a preferred framework order. If two candidates are equally preferred, the result is ambiguous instead of a silent winner.
Rubric Assertion Profiles (aka RAP Sheets) can be migrated so recognized local references become the canonical w3id URI while the old id is kept as legacyId. That migration touches only the current user's recognized references. It does not rewrite historic xAPI statements.
The workspace also offers fictional private sample data, so you can try labels, mappings, and resolution without writing into a real framework. Sample data is opt-in. Signing in does not create it.
TLA Toolbox remains public, with no fee planned. The linked data workspace is an alpha on top of IEEE 1484.20.3 SCD, meant for people who need competency definitions that can be shared, versioned, and resolved across frameworks without losing the rubric and the identifiers they already have.