← Back to catalogue
Generated draft

coding system

vr.tr.coding-system · thing-coding-system

Give an agent a durable, checkable way to recognise a coding system, record what state it is in, and decide what may be done with it.

Thing Registry Information and virtual systems INF.MED

Generated draft, first pass

This model was drafted by rule from what the registry knows about the thing. It proposes which bundles a real model will need and which questions research must answer. It is not researched and no sentence in it is sourced.

Generator: vr.draft.v3

Bundle → Layer → Finding → Questions Derived, awaiting review

6 bundles · 12 layers · 14 findings · 38 questions

Identity, naming and classification How an agent tells one coding system from another, and a coding system from things that resemble it.

Recognition comes before every other claim. Without stable identity nothing else in the model can be trusted to be about the same thing twice.

Names and identifiers

The names this thing goes by and the identifiers that survive translation and time.

Preferred name, aliases and local names

Which name to use, which names mean the same thing, and which merely sound similar.

  1. What identifies and describes the name of a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about the name of a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once the name of a coding system is known, and what must it refuse? action

Stable identifiers and external keys

Identifiers that keep pointing at this kind of thing across systems and languages.

  1. What identifies and describes an identifier for a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about an identifier for a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once an identifier for a coding system is known, and what must it refuse? action

Classification and granularity

Where a coding system sits among kinds, and how finely a task needs to cut it.

Kind, parents and neighbouring kinds

The classes this thing belongs to and the ones it is next to.

  1. What identifies and describes the kind of a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about the kind of a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once the kind of a coding system is known, and what must it refuse? action

Distinguishing features

What separates a coding system from the things most often confused with it.

  1. What identifies and describes what distinguishes a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about what distinguishes a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once what distinguishes a coding system is known, and what must it refuse? action
State and lifecycle The states a coding system passes through and the events that move it between them.

Most decisions about a thing depend on what state it is in now, which is a claim with a time on it, not a property.

Lifecycle stages

From coming into existence to ceasing to be one of these.

Stages and transitions

The stages worth naming and what moves a coding system between them.

  1. What identifies and describes the lifecycle of a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about the lifecycle of a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once the lifecycle of a coding system is known, and what must it refuse? action

Observations and current status

What is observed about a coding system, how often and by whom.

Observation record

How an observation of a coding system is recorded so that it can be superseded rather than overwritten.

  1. What identifies and describes an observation of a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about an observation of a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once an observation of a coding system is known, and what must it refuse? action
Content, encoding and access What a coding system says, how it is encoded and who may read it.

An informational thing carries content that can be copied, versioned and withheld, none of which its physical carrier explains.

Content and encoding

The content itself, its format and its language.

Content, format and language

What a coding system contains and in what form it is held.

  1. What identifies and describes the content of a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about the content of a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once the content of a coding system is known, and what must it refuse? action

Access, rights and retention

Who may read, copy or change it, and for how long it is kept.

Access rules and retention

The permissions attached to a coding system and the period it survives.

  1. What identifies and describes access to a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about access to a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once access to a coding system is known, and what must it refuse? action
Work, version and copy Which level of coding system a statement is about.

The work, the edition, the file and the copy in hand are four things; rights and content attach to different ones.

Levels of the thing

Work, expression, manifestation and item, in plain terms.

What belongs at each level

Which facts hold for the work and which only for one copy.

  1. For coding system, which facts belong to the work itself, which to a version, and which to a single copy? boundary
  2. What identifier exists at each level, and which one is being cited? definition

Versions, editions and variants

How versions differ and which is canonical to whom.

Versions and canonicity

Differences that matter and who calls one authoritative.

  1. Which versions or editions of coding system exist, and how do they differ substantively? definition
  2. Who treats which version as authoritative, and for what purpose? provenance
Authorship, rights and permitted use Who made coding system and what may be done with it.

Rights are jurisdictional, time-limited and attached to a level, and an agent that ignores that will copy what it may not.

Authorship and contribution

Who contributed what, and in what capacity.

Contributors and roles

The people and bodies behind it, with their roles.

  1. Who authored or contributed to coding system, in what roles, and how is that attested? provenance
  2. Where authorship is disputed or anonymous, what is recorded instead? boundary

Rights and permissions

Which rights subsist, where, until when, and what they permit.

Rights, term and permitted acts

The regime in force and what it allows.

  1. What rights subsist in coding system, in which jurisdictions, and until when? definition
  2. Which acts are permitted without further permission, and which must an agent refuse? action
Provenance, evidence and time Where every claim about a coding system came from and when it held.

A claim without a source and a time cannot be superseded, only overwritten, and an agent that overwrites loses the ability to explain itself.

Source and authority

Who said it, on what evidence, and how strongly.

Claim provenance and confidence

The authority behind each claim about a coding system and how confident it is.

  1. What identifies and describes a claim about a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about a claim about a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once a claim about a coding system is known, and what must it refuse? action

Time, versions and supersession

When a claim was true, when it was learnt, and what replaced it.

Validity period and supersession

How an old claim about a coding system is retired without being erased.

  1. What identifies and describes the validity of a claim about a coding system, and in what units or vocabulary? definition
  2. Who or what asserted this about the validity of a claim about a coding system, by which method, and when was it true? provenance
  3. What may an agent decide or do once the validity of a claim about a coding system is known, and what must it refuse? action

Classifiers Filled

Family
Thing Registry
Category
Information and virtual systems
Entry kind
work, medium or creative form
Plane
INF
Domain
INF.MED
Facets: substance
information
Facets: origin
conceptual
Facets: agency
inert
Facets: mobility
not-applicable
Facets: scale
not-applicable
Facets: affordances
readable

What it is Filled

a system of signals used to represent letters or numbers in transmitting messages

Why it exists Derived, awaiting review

Give an agent a durable, checkable way to recognise a coding system, record what state it is in, and decide what may be done with it.

Distinguishing features Missing, in the backlog

Not described yet. This gap is in the card backlog.

What robots and AI may and may not do Derived, awaiting review

May

  • read it and act on what it says

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Missing, in the backlog

Not described yet. This gap is in the card backlog.

Links to other meta-models Missing, in the backlog

Not described yet. This gap is in the card backlog.

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Direct properties not applicable Not applicable

  • Made of: content that has to be carried by something else
  • Does nothing on its own; everything it does, something else did to it.

Recognition optional Derived, awaiting review

  • What is seen is a copy or a performance, not the work. Recognising the work means recognising the content through whatever is carrying it.

Capabilities and actions required Derived, awaiting review

  • read and interpreted

Hazards and failure modes required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Context of use required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Sources Missing, in the backlog

Not described yet. This gap is in the card backlog.

Open questions

  • Which of the bundles below does a real task actually need, and which are ceremony?
  • What does this thing have that the facets do not capture at all?
  • Which neighbouring kind is most often confused with a coding system, and on what evidence are they told apart?
  • What may an agent decide or do once the name of a coding system is known, and what must it refuse?
  • What may an agent decide or do once an identifier for a coding system is known, and what must it refuse?
  • What may an agent decide or do once the kind of a coding system is known, and what must it refuse?

Machine files

Provenance

thing registry, generated draft (pass 1) · not researched

Built from: models/draft_model.php, oewn:2024

Generated by rule from registry facets. No source was read; every derived section awaits the research pass.