← Back to catalogue
Generated draft

Microsoft SQL Server

vr.tr.microsoft-sql-server · PHY.OBJ
Thing Registry Physical world and living 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 Microsoft SQL Server, record what state it is in, and decide what may be done with it.

A physical thing registered under PHY.OBJ. The registry names it; this draft has not been given a definition yet.

It can be observed and measured.

Distinguishing features

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

Physical character

Made of: matter you can touch.

Mobility varies between examples.

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

Recognised by form and material. The registry holds no appearance data, so what a Microsoft SQL Server looks like has to come from research.

Described in 46 Wikipedia languages, which measures how widely it is written about rather than how important or how common it is.

Where this came from

wikidata · CC0 1.0

Source repository Registry entry point

Drafted structure

Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 13 layers · 15 findings · 45 questions.

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

Classification and granularity

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

Distinguishing features

What separates a Microsoft SQL Server from the things most often confused with it.

  1. What identifies and describes what distinguishes a Microsoft SQL Server, and in what units or vocabulary? definition
  2. Who or what asserted this about what distinguishes a Microsoft SQL Server, by which method, and when was it true? provenance
  3. What may an agent decide or do once what distinguishes a Microsoft SQL Server is known, and what must it refuse? action
Form, composition and condition What a Microsoft SQL Server is made of, what shape and size it takes, and what state it is in.

A physical thing can be measured, and a model that cannot record its measurements cannot support any decision that depends on them.

Form and dimensions

Shape, size, mass and the ranges these take across examples.

Measurable dimensions and their units

The quantities worth recording and the units they are recorded in.

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

Material and composition

Materials, parts and how they are put together.

Parts and materials

What a Microsoft SQL Server is built from and which parts are replaceable.

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

Condition and integrity

Wear, damage, health and the difference between working and broken.

Condition, damage and health

How the condition of a Microsoft SQL Server is judged and by whom.

  1. What identifies and describes the condition of a Microsoft SQL Server, and in what units or vocabulary? definition
  2. Who or what asserted this about the condition of a Microsoft SQL Server, by which method, and when was it true? provenance
  3. What may an agent decide or do once the condition of a Microsoft SQL Server is known, and what must it refuse? action
Place and movement Where a Microsoft SQL Server is, how it got there and where it may go (varies).

A thing that can move needs its position recorded with a time, or every later claim about it is about a place it has left.

Location and placement

Position, containment and the reference frame the position is given in.

Position, container and reference frame

Where a Microsoft SQL Server is, and what that position is measured against.

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

Movement and transfer

How a Microsoft SQL Server is carried, installed or relocated.

Movement events and constraints

What counts as a movement, what records it and what limits it.

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

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

Observations and current status

What is observed about a Microsoft SQL Server, how often and by whom.

Observation record

How an observation of a Microsoft SQL Server is recorded so that it can be superseded rather than overwritten.

  1. What identifies and describes an observation of a Microsoft SQL Server, and in what units or vocabulary? definition
  2. Who or what asserted this about an observation of a Microsoft SQL Server, by which method, and when was it true? provenance
  3. What may an agent decide or do once an observation of a Microsoft SQL Server is known, and what must it refuse? action
Use and operation What can be done with a Microsoft SQL Server and what it takes to do it.

An agent that can recognise a thing but not act on it has only half a model.

Intended use and function

What a Microsoft SQL Server is for, and what it is used for anyway.

Function, purpose and misuse

The function a Microsoft SQL Server performs and the uses that fall outside it.

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

Handling and procedure

The steps, skills and tools involved in using a Microsoft SQL Server.

Procedures, skills and required tools

What an agent needs before it can act on a Microsoft SQL Server at all.

  1. What identifies and describes handling a Microsoft SQL Server, and in what units or vocabulary? definition
  2. Who or what asserted this about handling a Microsoft SQL Server, by which method, and when was it true? provenance
  3. What may an agent decide or do once handling a Microsoft SQL Server is known, and what must it refuse? action
Provenance, evidence and time Where every claim about a Microsoft SQL Server 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 Microsoft SQL Server and how confident it is.

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

  1. What identifies and describes the validity of a claim about a Microsoft SQL Server, and in what units or vocabulary? definition
  2. Who or what asserted this about the validity of a claim about a Microsoft SQL Server, 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 Microsoft SQL Server 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 Microsoft SQL Server, and on what evidence are they told apart?
Draft as JSON