shared-definitions.schema.json¶

This JSON Schema collects definitions referenced by multiple JSON Schemas under $defs. In addition to IDs and numbers, it defines focal lengths, measurement conditions, optical construction, electronic data, tripod support, movements, and related values.

It does not validate a standalone JSON file. Each JSON Schema uses $ref to reference the definitions it needs.

Example using shared definitions¶

The NIKKOR Z 24-70mm f/2.8 S II example below shows how shared definitions represent actual values.

Source: data/records/lenses/nikkor/nikkor-z-24-to-70mm-f2p8-s-ii.json

{
  "kind": "zoom",
  "rangeMm": {
    "minimum": 24,
    "maximum": 70
  }
}

{
  "format": "full-frame",
  "orientation": "diagonal",
  "degrees": 84,
  "conditions": {
    "focalLength": {
      "kind": "point",
      "millimeters": 24
    }
  }
}

{
  "value": 2.8,
  "conditions": {}
}

focalLength represents the product's nominal focal length. The conditions.focalLength of a measurement indicates where on the focal-length range that value applies. An empty conditions object means that there are no additional focal-length, focus-distance, or other conditions.

Basic values¶

Do not record JAN, EAN, or UPC codes, barcodes, SKUs, product numbers, catalog numbers, article numbers, or similar identifiers in modelNumberOptions unless the manufacturer or brand explicitly identifies them as model numbers.

Focal lengths and conditions¶

focalLengthCondition¶

Represents a point or range on the focal-length scale to which a measurement applies. It is not the focal-length specification of the lens itself.

point requires kind and millimeters; range requires kind, minimumMm, and maximumMm. The two shapes are mutually exclusive, so fields from the unselected shape are not permitted.

focalLength¶

Record the following fields according to kind.

prime requires kind and millimeters; zoom requires kind and rangeMm; interchangeable requires kind and configurations. The three shapes are mutually exclusive, so fields from the unselected shapes are not permitted. configurations must contain at least two distinct entries, each with magnification and millimeters.

Condition objects¶

The conditions that can be attached to a measurement depend on the type of value. Each key is optional, and an empty object {} means that there are no additional conditions.

Condition objects combine the following keys.

Optical values¶

F-number and T-stop measurements¶

angleOfView¶

opticalConstruction¶

At least one of the group and element counts must be numeric. If only one is officially published, record null for the other. When both are numeric, hatch run validate checks that the group count does not exceed the element count.

specialElement¶

coating¶

types provides cross-brand grouping, while officialName preserves the manufacturer's published terminology. Retain a stable technical designation in officialName even when both fields express the same general property. Interpret officialName within its brand and field; identical wording does not establish that technologies from different brands are the same. Differences limited to sentence capitalization, spacing, hyphenation, grammatical number, or generic suffixes do not create separate names. Prefer an official glossary, technology page, specification label, heading, badge, or marking on the product. Use an official English designation when an equivalent official English page exists; otherwise preserve the published designation rather than inventing a translation. Omit ® and ™, but preserve a symbol that is part of the designation itself, such as the asterisk in T*.

Environmental-protection claims¶

environmentalClaim records dust-, drip-, weather-, and similar protection wording explicitly published by the manufacturer or brand, together with the scope to which it applies.

When scope.kind is product, record only kind in scope. When it is component, component is also required. This definition structures official wording; it does not infer compliance with a test standard or complete waterproofing.

Electronic data¶

metadataTransmission¶

metadataTransmission records whether shooting metadata is transmitted and which published standards are used.

Use { "present": false } when the absence of transmission is confirmed. When transmission is present, both present: true and standards are required. Use null when accepted published evidence does not establish whether transmission is present.

electronicServices¶

electronicServices records published product firmware-update status and connection methods used for updates, configuration, or control.

Use electronicServices: null when electronic services as a whole are not established.

Tripod support¶

tripodSupport records whether tripod support is present and the components that have been established. Lenses and mount adapters use the same definition.

Use threadDesignation: null for a mounting-thread whose thread specification is not established. Use { "present": false } when the absence of support is confirmed, and null when its presence is not established.

Movements¶

movements records tilt, shift, and the range through which a movable assembly can rotate around the optical axis. The same definition is used for lenses and mount adapters.

movements contains at least one of tiltMeasurements, shiftMeasurements, and rotationMeasurements. Measurement arrays cannot contain duplicate entries. Every measurement requires either a numeric maximum from neutral or a numeric total range; use null for the other when it is not established. directionality and conditions are also required; use conditions: {} when there are no additional conditions. When the applicable movement mechanism is confirmed but its nominal amount is not, the corresponding value may be null.

Focus distances and reproduction ratios¶

Each minimumFocusDistance and workingDistance entry requires both distanceM and conditions. A reproductionMagnification uses value for maximum or fixed, minimum and maximum for range, or values for discrete; every shape also requires kind and conditions. These shapes are mutually exclusive, and values must contain at least one value with no duplicates.

Host¶

host indicates whether a filter or similar interface is attached to the product itself or to an external accessory.

When kind is product, record only kind. When it is accessory, category and modelNumberOptions are also required.

Repository validation¶

hatch run validate also checks that the lower bound of a range does not exceed its upper bound. This applies to minimum and maximum values for focal lengths, reproduction ratios, and similar ranges. For optical construction, it also checks that groups does not exceed elements.

Related pages¶

• JSON Schema reference: Overall JSON Schema structure and how to read the reference
• How to interpret values: When to use null, an empty array, or false
• Field reference for lenses and related optical products: How these definitions appear in canonical records
• Mount adapter field reference: Mount adapter fields that use shared definitions
• JSON Schema file