Vocabulary

The vs: terms in every page's JSON-LD — https://vocascope.com.au/vocab/. Used where a schema.org property would claim more than the register does. How to read a fact →

Against the register, on this request

Every code in registry.epistemic_state, registry.review_state, registry.permitted_use and registry.relationship_type has a term here, every term that reads a register row found it, and every row carries a description.

Classes 2

Where a term corresponds to a registry.predicate or registry.relationship_type code, the register's description follows the definition, read on each request.

term	definition
vs:SourceVersion	One retrieval of one locator from one source at one moment — the warrant every membership, edge and fact cites.
vs:Pathway	A reified IS_PATHWAY_TO edge: training.gov.au publishes an occupation as an outcome of a code, with its envelope and facts. the register's words, registry.relationship_type IS_PATHWAY_TO: The subject training-product code is published by TGA as having the object occupation as an occupational outcome. Not evidence of labour-market outcome. Reaches the occupation entity through a reviewed crosswalk from TGA's occupation to an ANZSCO code, then ABS's ANZSCO–OSCA correspondence; the sequence followed is stated in the relationship's method.

term

definition

vs:SourceVersion

One retrieval of one locator from one source at one moment — the warrant every membership, edge and fact cites.

vs:Pathway

A reified IS_PATHWAY_TO edge: training.gov.au publishes an occupation as an outcome of a code, with its envelope and facts.

the register's words, registry.relationship_type IS_PATHWAY_TO: The subject training-product code is published by TGA as having the object occupation as an occupational outcome. Not evidence of labour-market outcome. Reaches the occupation entity through a reviewed crosswalk from TGA's occupation to an ANZSCO code, then ABS's ANZSCO–OSCA correspondence; the sequence followed is stated in the relationship's method.

Properties 38

Where a term corresponds to a registry.predicate or registry.relationship_type code, the register's description follows the definition, read on each request.

term	definition
vs:evidenceAsAt	The most recent retrieval among every source version the page cites; moves on a retrieval that changes nothing, so never dateModified.
vs:genesisWarrant	The source version an entity was created from.
vs:fact	The assertions on this node, each a blank node with predicate, value state, value when present, method, warrant and epistemic state.
vs:sourceVersionCount	On a list: the number of distinct source versions warranting the rows shown.
vs:edgeCount	On a root: one entry per relationship type and for classification memberships, counting rows recorded and rows citable — a count names, links and warrants nothing (Call 2 rule 4).
vs:relationshipType	The registry relationship type an edgeCount entry counts (IS_PATHWAY_TO, IS_SUCCESSOR_TO).
vs:membershipType	The membership kind an edgeCount entry counts (classificationMembership).
vs:recordedCount	Rows of this kind the register holds for the page, whatever their state.
vs:citableCount	Rows of this kind the payload emits — those whose permitted uses include citation.
vs:classificationMembership	An occupation entity's dated membership of a classification code, as a CategoryCode with its scheme, part flags, validity and envelope.
vs:codeMembership	A credential lineage's dated membership of a register code; on a Pathway, the membership the edge starts from.
vs:scheme	The registry scheme code the membership belongs to (osca_2024, anzsco_2022, tga).
vs:code	The code value a membership or succession node names — a literal, never an identity.
vs:isAnchor	True on the classification membership an occupation entity was anchored on at creation (OSCA 2024).
vs:partCode	ABS: the classification code corresponds only in part to this entity, read from the flag assertion. Absent on an anchor, and wherever that assertion is missing, withheld or retrieved-absent — a retrieved absence is stated by its own fact node, never by this property. the register's words, registry.predicate part_code: ABS part flag, code direction: the classification code corresponds only in part to this entity. Asserted from the retrieved correspondence. The membership column of the same name is an earlier reading inherited from a prior load; the assertion is the one to rely on.
vs:partEntity	ABS: this entity corresponds only in part to the code, read from the flag assertion. Absent on an anchor, and wherever that assertion is missing, withheld or retrieved-absent — a retrieved absence is stated by its own fact node, never by this property. the register's words, registry.predicate part_entity: ABS part flag, entity direction: this entity corresponds only in part to the classification code. Asserted from the retrieved correspondence.
vs:validFrom	First date a classification membership holds.
vs:validTo	Last date a classification membership holds; absent while open.
vs:admittedAt	When a register code was admitted to a credential lineage.
vs:credential	The credential entity a code membership belongs to, by canonical URI.
vs:occupation	The occupation entity a Pathway reaches, by canonical URI.
vs:isPathwayTo	On a code membership: the Pathway edges from this code to occupations. the register's words, registry.relationship_type IS_PATHWAY_TO: The subject training-product code is published by TGA as having the object occupation as an occupational outcome. Not evidence of labour-market outcome. Reaches the occupation entity through a reviewed crosswalk from TGA's occupation to an ANZSCO code, then ABS's ANZSCO–OSCA correspondence; the sequence followed is stated in the relationship's method.
vs:pathwayFrom	On an occupation: the Pathway edges reaching it, each carrying the code membership it starts from. the register's words, registry.relationship_type IS_PATHWAY_TO: The subject training-product code is published by TGA as having the object occupation as an occupational outcome. Not evidence of labour-market outcome. Reaches the occupation entity through a reviewed crosswalk from TGA's occupation to an ANZSCO code, then ABS's ANZSCO–OSCA correspondence; the sequence followed is stated in the relationship's method.
vs:isSuccessorTo	On a code membership: the code this one supersedes, as a node naming that code with the edge's envelope and TGA's equivalence as facts. the register's words, registry.relationship_type IS_SUCCESSOR_TO: The subject code supersedes the object code, as training.gov.au records it. TGA's statement of whether the two are equivalent is a separate fact on this relationship (is_equivalent); whether the codes share a credential lineage follows that fact.
vs:hasSuccessor	On a code membership: the code that supersedes this one, as a node naming that code with the edge's envelope and TGA's equivalence as facts. the register's words, registry.relationship_type IS_SUCCESSOR_TO: The subject code supersedes the object code, as training.gov.au records it. TGA's statement of whether the two are equivalent is a separate fact on this relationship (is_equivalent); whether the codes share a credential lineage follows that fact.
vs:warrant	The SourceVersion a membership, edge or fact rests on.
vs:sourceSystem	The registry source system code of a warrant (tga_rest, abs_osca_2024, vocascope).
vs:retrievedAt	When the warrant's retrieval happened, ISO 8601.
vs:httpStatus	The HTTP status the retrieval returned, when recorded — for a retrieved-closed fact the refusal is the evidence.
vs:locator	A warrant's locator when it is not a URL — a method or review batch name for vocascope source versions.
vs:epistemicState	What kind of statement a row is, as one of the epistemic state terms below. Carried where the register records one — on edges and on facts; a membership carries none.
vs:reviewState	Where a row stands in human review, as one of the review state terms below.
vs:reviewedBy	Who signed the review; vocascope:carry when carried from a prior review cited by a fact.
vs:reviewedAt	When the review was signed, ISO 8601.
vs:permittedUse	The analytical uses the register permits for a row, as permitted use terms below; citation is what admits a row to this payload (Call 2).
vs:method	The stated method behind a derived fact or an edge.
vs:predicate	The registry predicate code a fact asserts.
vs:valueState	Whether the retrieval found a value (present) or found none (absent); a predicate never retrieved has no node at all.

States 15

Registry codes, verbatim. Epistemic states, review states and permitted uses are described in the register's own words, read from registry.epistemic_state, registry.review_state and registry.permitted_use on each request. Value states have no table — they are a CHECK constraint on registry.assertion — so their wording is this vocabulary's.

term	definition
vs:AUTHORITATIVE_SOURCE	Direct assertion from the governing source for that concept — a TGA title, an OSCA title.registry.epistemic_state · read live
vs:SOURCE_OBSERVED	Direct observation from an approved source that is not the governing authority for the concept — for example, TGA's register status of a code, recorded verbatim.registry.epistemic_state · read live
vs:OFFICIAL_RELATIONSHIP	Publisher-provided correspondence, hierarchy or succession — ABS ANZSCO↔OSCA correspondence, TGA supersession, TGA taxonomy occupations.registry.epistemic_state · read live
vs:DERIVED_DETERMINISTIC	Reproducible transformation of governed inputs by a stated method — for example, an entity's lifecycle state, derived from its code memberships.registry.epistemic_state · read live
vs:HUMAN_ASSERTED	Reviewed judgement or curator decision — an approved crosswalk row, an admitted pathway.registry.epistemic_state · read live
vs:REJECTED	Candidate assessed and not admitted. Retained as negative knowledge — a record that it was considered and refused.registry.epistemic_state · read live
vs:SUPERSEDED	Historically valid, no longer current. Retained; points at what replaced it.registry.epistemic_state · read live
vs:pending	Awaiting human review. Neither admitted nor refused.registry.review_state · read live
vs:approved	Admitted by a named reviewer.registry.review_state · read live
vs:rejected	Assessed and not admitted; a reason is always recorded.registry.review_state · read live
vs:navigation	May be followed to reach related records and shown on a page.registry.permitted_use · read live
vs:aggregation	May be used to attribute or roll up measures. A partial correspondence never carries this.registry.permitted_use · read live
vs:citation	May be cited as evidence in an answer's evidence envelope.registry.permitted_use · read live
vs:present	The retrieval found a value; the node carries it.registry.assertion.value_state
vs:absent	The retrieval found no value; the node carries its warrant and no value — never null, false or empty (Call 2 rule 3).registry.assertion.value_state

Predicates 19

These are the literal codes a fact's vs:predicate carries; they are register vocabulary, not vs: terms, and have no IRI. Read from registry.predicate on each request. Where a code also has a vs: term, the row links to it.

code	subject kind	object type	single valued	the register's description
classification_title	classification_membership	text	yes	The title the classification publisher gives the code — ABS's OSCA or ANZSCO title.
code_title	code_membership	text	yes	The title TGA gives this code. Two codes in one lineage may carry the same title.
currency_from	code_membership	date	yes	The start of the currency period TGA records for the code.
currency_to	code_membership	date	yes	The end of the currency period TGA records for the code. Where TGA's response carries no end date, that is recorded as retrieved and absent — never assumed to mean open-ended.
is_equivalent	relationship	boolean	yes	TGA's statement of whether a superseding code is equivalent to the one it replaces, on an IS_SUCCESSOR_TO relationship. Where it is absent or not retrieved, the two lineages stay separate. Never defaulted.
lifecycle	entity	text	yes	The entity's lifecycle state, derived deterministically from the TGA status of its code memberships by a fixed rule. The value is one of the register's lifecycle states, each defined by its rule.
mapping_date	relationship	date	yes	TGA mappingInformation.date on an IS_SUCCESSOR_TO edge — the date the register records the supersession. SOURCE_OBSERVED.
mapping_note	relationship	text	yes	TGA mappingInformation.notes, verbatim, on an IS_SUCCESSOR_TO edge — e.g. "Supersedes and is not equivalent to CPC32413 …". Shown in the evidence envelope.
nrt_status	code_membership	text	yes	TGA's status of the code, verbatim: Current, Superseded, Deleted. SOURCE_OBSERVED.
nrt_type	entity	text	yes	Qualification or Skill set, as TGA states it. An attribute, not identity.
occupational_outcomes_applicable	code_membership	boolean	yes	Whether TGA's taxonomy-occupations endpoint applies to this code. A false is retrieved, not assumed: TGA answers HTTP 400 "Taxonomy occupations only applies to qualifications", and that response is the fact's warrant. A false here is retrieved-closed, not not-retrieved.
part_code	classification_membership	boolean	yes	ABS part flag, code direction: the classification code corresponds only in part to this entity. Asserted from the retrieved correspondence. The membership column of the same name is an earlier reading inherited from a prior load; the assertion is the one to rely on. term: vs:partCode
part_entity	classification_membership	boolean	yes	ABS part flag, entity direction: this entity corresponds only in part to the classification code. Asserted from the retrieved correspondence. term: vs:partEntity
release_number	code_membership	text	yes	The TGA release the detail was read from; permits citation pinned to a release.
rests_on_crosswalk_row	relationship	numeric	yes	The reviewed crosswalk row an IS_PATHWAY_TO relationship followed — the link from TGA's occupation to an ANZSCO code. Recorded when the pathway is derived, so the pathway's evidence is shown with the row it rests on. The value is a VocaScope row id, never a classification code.
review_carried_from	relationship	text	no	This relationship's review state, permitted uses and rejection reason were carried from a human-reviewed relationship asserting the identical claim (same type, subject, object and equivalence). The value names the human-reviewed relationship or relationships cited. A derived act, never a fresh human decision.
tga_record_id	code_membership	text	yes	TGA's own GUID for the record (payload `id`). A retrieval handle and the key `mapsToId` points at; never an identity.
title	entity	text	yes	The name VocaScope presents for the entity. Warranted by the anchor source at genesis; later assertions supersede.
usage_recommendation	code_membership	text	yes	TGA's UsageRecommendation, verbatim.