product-components.schema.json¶

This schema defines the product-information blocks shared by lenses, teleconverters, and pinhole products. It is a collection of definitions referenced by product-full, not a schema that validates a standalone JSON file.

Definition groups¶

For smaller definitions such as IDs, numbers, measurement conditions, and optical construction, see Shared definitions.

Examples of common blocks¶

The following examples use the NIKKOR Z 24-70mm f/2.8 S II to show where these blocks appear in a canonical record. Each code block contains actual data limited to the blocks identified below.

{
  "identity": {
    "manufacturerId": "nikon",
    "brandId": "nikkor",
    "productName": "NIKKOR Z 24-70mm f/2.8 S II",
    "modelNumberOptions": null,
    "alternateNames": null,
    "variants": null
  },
  "lifecycle": {
    "announcementDate": "2025-08-22",
    "officialDesignations": []
  }
}

{
  "systemId": "nikon-z",
  "replaceability": "fixed",
  "mountOwnerRelationship": "mount-owner",
  "electronicContacts": {
    "present": true,
    "metadataTransmission": {
      "present": true,
      "standards": [
        "exif"
      ]
    }
  }
}

Identity¶

All six fields directly under identity are required. Even when model numbers, alternate names, or variants cannot be confirmed from accepted published evidence, do not omit the fields. Record null instead. See the shared definition of modelNumberOptions for which identifiers are treated as model numbers.

Product release information¶

announcementDate and officialDesignations are required. Do not use a development-announcement date for announcementDate.

officialDesignations: [] does not mean that the product is currently sold, in stock, or available.

Official product pages¶

Every element of officialProductPages[] contains five fields directly under it: url, pageFamilies, region, language, and publisher.

Both publisher.type and publisher.name are required within publisher.

Connection to the Nikon Z mount¶

systemId, replaceability, mountOwnerRelationship, and electronicContacts are required directly under mount. adapter is present only for a product supplied with a Nikon Z-mount adapter or used with an adapter dedicated to that product or an officially identified product series.

Electronic-contact conditions¶

Mount-adapter conditions¶

All five fields directly under mount.adapter are required. When relationship is optional, dedicatedToProduct must be true.

For detailed inclusion criteria and examples, see the Lens and related optical product field reference.

Physical form and attachment interfaces¶

dimensionMeasurements, weightMeasurements, officialEnvironmentalProtectionClaims, filterInterfaces, and tripodSupport are required directly under physical. Other fields are present only for products to which they structurally apply.

Dimensions and weight¶

Every dimension entry requires a positive number in at least one of maximumDiameterMm and lengthMm. Both fields are required, so record null for the unpublished value. conditions for dimensions and conditions.attachedComponents for weight are also required.

The following values are available for attachedComponents:

• Tripod mounting hardware: tripod-collar-assembly, tripod-foot, tripod-mount-cover
• Lens accessories: lens-hood, front-cap, rear-cap
• Filter: drop-in-filter
• Other: other

Environmental protection claims¶

Do not use scope.component when scope.kind is product. When it is component, scope.component is required.

Filter attachment methods¶

For physical.filterInterfaces, use [] after checking the attachment methods and finding that none apply, or null when accepted published evidence is unavailable. The dimension field in each entry depends on type.

Tripod mounting hardware and external shape changes¶

When tripodSupport.present is false, the object contains only present. When it is true, components is also required; use null when support is present but its component breakdown is not established.

Controls¶

Every element of controls[] contains type and quantity. officialName may be added to any control when a stable name appears on the product or in an official specification. Omit a generic name such as Focus ring when it merely repeats type. Use the manufacturer's official English designation when an equivalent English page exists, but do not invent a translation.

The values of type treated as rings are aperture-ring, control-ring, function-ring, focus-ring, and zoom-ring. Only these controls may use clickBehavior, rotationDegrees, geared, and response.

The other type values are grouped below.

• Zoom controls: power-zoom-control, zoom-lever, zoom-lock
• Buttons: function-button, memory-set-button
• Focus controls: focus-mode-switch, focus-limiter
• Aperture and control rings: aperture-ring-click-switch, control-ring-click-switch, aperture-ring-lock
• Displays: information-display, focus-distance-scale, depth-of-field-scale
• Other: other

Accessories¶

accessories is an object or null. When it is an object, it contains all six fields directly under it, and every field contains an array or null.

Related pages¶

• Shared definitions: definitions for IDs, numbers, measurement conditions, electronic services, tripod support, and attachment hosts
• product-full: combination of common and product-type blocks
• Lens and related optical product field reference: explanations of each block using actual data

JSON Schema file