← Back to catalogue
Generated draft

file manager

vr.tr.file-manager · INF.MED
Thing Registry Information and virtual systems

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.

Written from the archetype playbook - what this kind of thing needs beyond identity and provenance - and from the structure that recurred across 6,333 models already researched by two engines. Applied to this entry by rule. No source was read for this thing and no claim here is researched. This entry carries no facets of its own, so they were inferred from its domain - a guess about a whole domain applied to one thing.

Generator: vr.draft.v3

Purpose and description

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

An informational thing registered under INF.MED. The registry names it; this draft has not been given a definition yet.

It can be read and interpreted; observed and measured.

Distinguishing features

Names folded into this entry, which a task may need to split apart again: spatial file manager.

1 finer distinctions are held as aliases rather than separate entries, because telling them apart needs a task that asks for it.

Described in 38 Wikipedia languages, which is a measure of how widely the thing is known, not of how important it is.

Physical character

Made of: content that has to be carried by something else.

Does nothing on its own; everything it does, something else did to it.

These come from the domain this entry sits in rather than from the entry itself, so treat them as a first guess about the whole domain applied to one thing.

How it is recognised

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

Related models

covers - Finer kinds folded into this entry because telling them apart needs a task that asks for it. Each is a model waiting to be split out when one does.

spatial file manager

Described in 38 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is. 1 finer distinctions are held inside this entry as names rather than as separate models.

Also called

spatial file manager

Where this came from

wikidata · CC0 1.0

Drafted structure

Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 12 layers · 14 findings · 38 questions.

Identity, naming and classification How an agent tells one file manager from another, and a file manager 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 file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about the name of a file manager, by which method, and when was it true? provenance
  3. What may an agent decide or do once the name of a file manager 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 file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about an identifier for a file manager, by which method, and when was it true? provenance
  3. What may an agent decide or do once an identifier for a file manager is known, and what must it refuse? action

Classification and granularity

Where a file manager 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 file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about the kind of a file manager, by which method, and when was it true? provenance
  3. What may an agent decide or do once the kind of a file manager is known, and what must it refuse? action

Distinguishing features

What separates a file manager from the things most often confused with it.

  1. What identifies and describes what distinguishes a file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about what distinguishes a file manager, by which method, and when was it true? provenance
  3. What may an agent decide or do once what distinguishes a file manager is known, and what must it refuse? action
State and lifecycle The states a file manager 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 file manager between them.

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

Observations and current status

What is observed about a file manager, how often and by whom.

Observation record

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

  1. What identifies and describes an observation of a file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about an observation of a file manager, by which method, and when was it true? provenance
  3. What may an agent decide or do once an observation of a file manager is known, and what must it refuse? action
Content, encoding and access What a file manager 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 file manager contains and in what form it is held.

  1. What identifies and describes the content of a file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about the content of a file manager, by which method, and when was it true? provenance
  3. What may an agent decide or do once the content of a file manager 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 file manager and the period it survives.

  1. What identifies and describes access to a file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about access to a file manager, by which method, and when was it true? provenance
  3. What may an agent decide or do once access to a file manager is known, and what must it refuse? action
Work, version and copy Which level of file manager 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 file manager, 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 file manager 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 file manager 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 file manager, 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 file manager, 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 file manager 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 file manager and how confident it is.

  1. What identifies and describes a claim about a file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about a claim about a file manager, by which method, and when was it true? provenance
  3. What may an agent decide or do once a claim about a file manager 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 file manager is retired without being erased.

  1. What identifies and describes the validity of a claim about a file manager, and in what units or vocabulary? definition
  2. Who or what asserted this about the validity of a claim about a file manager, 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 file manager is known, and what must it refuse? action

What the second pass must settle

  • 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 file manager, and on what evidence are they told apart?