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 →

Classes 2

term	definition
vs:SourceVersion	One retrieval of one locator from one source at one moment — the warrant every membership, edge and fact cites (D-093).
vs:Pathway	A reified IS_PATHWAY_TO edge: training.gov.au publishes an occupation as an outcome of a code (D-070), with its envelope and facts.

Properties 38

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 (D-085).
vs:codeMembership	A credential lineage's dated membership of a register code (D-084); 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 (D-094); absent on an anchor.
vs:partEntity	ABS: this entity corresponds only in part to the code (D-094); absent on an anchor.
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.
vs:pathwayFrom	On an occupation: the Pathway edges reaching it, each carrying the code membership it starts from.
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.
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.
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 (D-111).
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.
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 (D-118).
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 (D-077).

States 15

Registry codes, verbatim. Epistemic states are read from registry.epistemic_state on each request; review states, permitted uses and value states are described here because the register does not expose those tables to this page.

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 — TGA's register status of a code, verbatim (D-086).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 — entity lifecycle (D-086).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 (paper §10).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.registry.review_state
vs:approved	Admitted by a named reviewer.registry.review_state
vs:rejected	Assessed and not admitted; a rejection reason is mandatory. Never emitted in the payload.registry.review_state
vs:navigation	May be followed to reach related records and shown on a page.registry.permitted_use
vs:aggregation	May be used to attribute or roll up measures. Partial correspondences never carry this (D-085).registry.permitted_use
vs:citation	May be cited as evidence in an answer's evidence envelope. The gate for this payload (Call 2 rule 1).registry.permitted_use
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