Published

specification

vr.tr.specification · thing-q2101564

Let an agent explain specifications, relay kinds, structure and relationship to standards from standards bodies and engineering sources, describe the named specification types, and distinguish specifications from standards, requirements documents, contracts and sampling plans.

Thing Registry Information and virtual systems INF.MED

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

4 bundles · 8 layers · 8 findings · 16 questions

Understand What a specification is.

Definition

Definition.

Definition

Definition.

What is a specification, and how does it differ from standards, requirements documents, contracts and sampling plans? definition
Is the question about software, engineering, procurement or standards? boundary

Types

Named types.

Types

Types.

What are JSRs, technical specifications, open specifications, record layouts and PAS documents, and why is a sampling plan different? definition
Which entry fits the specific type? action

Writing Writing specifications.

Language

Requirement language.

Language

Language.

How do keywords such as MUST and SHOULD make requirements testable? provenance
Which references are standard? provenance

Structure

Structure.

Structure

Structure.

What sections do specifications typically contain? provenance
Which sources are cited? provenance

Standards Standards processes.

ISO

ISO document types.

ISO

ISO.

How do ISO technical specifications differ from International Standards? provenance
Which entry fits International Organization for Standardization? action

Open

Open specifications.

Open

Open.

What makes a specification open, and how are community processes like the JCP run? provenance
Which entry fits open standard? action

Context Uses.

Procurement

Procurement.

Procurement

Procurement.

How are specifications used in public procurement? provenance
Which entry fits public procurement? action

Data

Data layouts.

Data

Data.

How do record layouts describe fixed-width data files? provenance
Which entry fits file format? action

Classifiers Filled

Family: Thing Registry
Category: Information and virtual systems
Entry kind: thing
Plane: INF
Domain: INF.MED
Other names and narrower kinds: Java Specification Request, technical specification, open specification, sampling plan, record layout, Publicly Available Specification, product specification, functional specification, design specification, software requirements specification, system requirements, open license

What it is Filled

A document that precisely states requirements, design, behaviour or characteristics that a product, material, process, service or data format must meet, used in engineering, software, procurement and standardisation, in forms such as technical specifications, open specifications freely available for implementation, Publicly Available Specifications published by BSI, Java Specification Requests in the Java Community Process and record layouts describing data file structures; the registry alias sampling plan is a quality control scheme that may be part of a specification but is a different document type.

Why it exists Filled

Distinguishing features Filled

Precise requirements
Verifiable
Many domains
May be open or proprietary

What robots and AI may and may not do Filled

Must not

Claim that something meets a specification without testing it.
Change a shared specification without its owner's approval.
Present a private specification as an official standard.
Copy or circulate a confidential specification beyond its audience.

Only with a human decision

Accepting deviations from a specification in safety-relevant work.

May

Check a design, product or dataset against a specification and report any gaps.
Cite a specification by its title, version and issuer.

Moral aspects Filled

Ambiguous specifications shift risk onto the people who build and use the product.
Specifications can be written to favour one supplier in public procurement.

Who is affected

Users of the product
Suppliers and bidders
Engineers

Owners Filled

Steward

The author or issuing organization of the specification.

Links to other meta-models Filled

parent

Q49848 - registry parent class

document - in registry terms
technical standard
Java Specification Request
acceptance sampling - misfiled alias sampling plan

What else AI and robots need to interact with it Filled

Sources Filled

Wikidata item Q2101564: specification - identity and sense of the item
Wikipedia: Specification (technical standard) - general description of the item

Open questions

Should PAS and JSR be separate entries?
How should standards bodies be linked?
The registry alias sampling plan should be moved to acceptance sampling

Machine files

Card as JSON Specification Card backlog vercy.card/1

Provenance

thing registry research (pass 2) · unreviewed

Built from: models/things/publications/thing-q2101564/spec.json

specification

Bundle → Layer → Finding → Questions Filled

Definition

Types

Language

Structure

ISO

Open

Procurement

Data

Classifiers Filled

What it is Filled

Why it exists Filled

Distinguishing features Filled

What robots and AI may and may not do Filled

Must not

Only with a human decision

May

Moral aspects Filled

Who is affected

Owners Filled

Steward

Links to other meta-models Filled

parent

related

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

Direct properties not applicable Not applicable

Recognition optional Filled

Capabilities and actions required Filled

Hazards and failure modes required Filled

Standards and interfaces required Filled

Context of use required Filled

Sources Filled

Open questions

Machine files

Provenance