Interpret structured editorial and licensing metadata

  Add normalized record kinds and roles for structured IPTC and PLUS
  metadata, including contacts, people, organizations, products, artwork,
  rights expressions, licenses, constraints, and releases.

  Expose independent policy-sensitivity classification through C++,
  transfer diagnostics, and Python bindings. Extend exact query semantics,
  conflict handling, tests, and public documentation.

  Increase version to 0.4.79.

Author: ssh4net

CHANGES.md

@@ -1,5 +1,35 @@
 # OpenMeta Changes
 
+## 0.4.79 - 2026-07-17
+
+Changes compared with `0.4.78`.
+
+### Added
+
+- Added structured descriptive record kinds and normalized roles for creator
+  contacts, events, people, organizations, products, artwork/objects, encoded
+  rights expressions, rights holders, licensors, licensees, licenses, and
+  model/property releases.
+- Added exact query semantics for contact, event, person, organization,
+  product, artwork, encoded-rights-expression, and release fields.
+- Added an independent sensitivity classification for personal contact,
+  person identity, location, and legal-rights metadata. C++ candidates,
+  transfer diagnostics, and thin Python dictionaries expose the same values.
+- Added interpretation for PLUS license dates, constraints, transaction and
+  project identifiers, terms, conditions, and release status/identifiers.
+
+### Changed
+
+- Structured descriptive conflicts and preference are isolated by record kind,
+  record scope, and language where applicable, so equal roles in different
+  people, products, artwork, license, or release records remain independent.
+- Technical transfer safety and policy sensitivity are reported separately;
+  privacy-sensitive metadata can remain technically portable without being
+  treated as automatically appropriate for publication.
+- Creator-contact, structured editorial, rights-expression, and PLUS fields
+  now participate in exact descriptive query results without consuming new
+  bits from the full legacy `MetadataQueryMatchTerm` mask.
+
 ## 0.4.78 - 2026-07-15
 
 Changes compared with `0.4.77`.

VERSION

@@ -1 +1 @@
-0.4.78
+0.4.79

docs/api_stability.md

@@ -17,8 +17,8 @@ model should stay compact:
 | Area | Purpose | Readiness |
 | --- | --- | --- |
 | Decoding | Find metadata carriers and decode EXIF, XMP, IPTC, ICC, Photoshop IRB, JUMBF/C2PA, EXR, and related blocks into `MetaStore` entries. | High, about 98-100% for the current target scope. |
-| Interpretation | Normalize names and values, group entries by meaning, and classify source-bound data such as RAW crop, exposure adjustment, color/profile/source-color-transform evidence, RAW curves/linearity metadata with descriptor-backed compressed-storage applicability, lens-correction, sensor, BMFF brand/item-property associations and rollups including `avio` AVIF brands, item groups, item semantic counts, whole-scene policy hints, graph-component summaries with per-component roles, member item IDs, semantic composition, typed relation counts, bounded `grid`/`iovl`/`iden` construction semantics with recursive item-offset descriptors and graph-cycle/source validation, bounded complete `tili` configuration/reference/offset-table interpretation, `container_graph` concepts, primary item properties, primary metadata-carrier flags, primary sidecar and scene summaries, and display-transform summaries, JUMBF labels, Photoshop IRB embedded carriers plus fixed-layout, XML/text, working-path and numbered clipping-path records, byte-count, descriptor-header, scalar/class/alias/enum/reference, and bounded nested list/object summaries, EXIF 3.1 correction/noise labels, version/firmware-style value formatting for selected EXIF/Nikon/Olympus/native RAF contexts, selected Sony ILCE-7RM6 correction-offset routing, Fujifilm flash white-balance naming, Apple/FLIR/JVC/GE/Reconyx/Microsoft/Nintendo/Sanyo scalar MakerNote labels, current Canon RF/Nikon Z lens labels, an ambiguous Pentax Sigma/Samsung/Tokina lens-family label, EXIF/XMP GPS timestamp composites, EXIF `OffsetTime*`/`SubSecTime*` date composition with normalized-instant conflict checks, separate camera/destination/shown/created GPS roles with scope-aware structured-location conflicts, language-aware descriptive scalar roles and additive creator/keyword/location-identifier/rights-holder/licensor collections with structured owner/licensor scopes, computational, thermal, stitch/panorama capture state, and vendor-private fields. | High, about 97-98%. |
-| Query | Find entries by name, fuzzy term, or semantic group, then expose normalized query candidates, structured interpretation records, bounded cross-family concept resolutions, transfer hints, and conflict flags for crop/border/active-area, exposure/gain, color/WB/profile/source-color-transform, orientation, date/time, GPS, descriptive fields including rights/license/credit/source, lens-correction, computational/thermal/stitch, RAW/source-processing fields, and BMFF derived-image construction and tiled-image configuration evidence across standard and vendor metadata. | Medium-high, about 92-95%. |
+| Interpretation | Normalize names and values, group entries by meaning, and classify source-bound data such as RAW crop, exposure adjustment, color/profile/source-color-transform evidence, RAW curves/linearity metadata with descriptor-backed compressed-storage applicability, lens-correction, sensor, BMFF brand/item-property associations and rollups including `avio` AVIF brands, item groups, item semantic counts, whole-scene policy hints, graph-component summaries with per-component roles, member item IDs, semantic composition, typed relation counts, bounded `grid`/`iovl`/`iden` construction semantics with recursive item-offset descriptors and graph-cycle/source validation, bounded complete `tili` configuration/reference/offset-table interpretation, `container_graph` concepts, primary item properties, primary metadata-carrier flags, primary sidecar and scene summaries, and display-transform summaries, JUMBF labels, Photoshop IRB embedded carriers plus fixed-layout, XML/text, working-path and numbered clipping-path records, byte-count, descriptor-header, scalar/class/alias/enum/reference, and bounded nested list/object summaries, EXIF 3.1 correction/noise labels, version/firmware-style value formatting for selected EXIF/Nikon/Olympus/native RAF contexts, selected Sony ILCE-7RM6 correction-offset routing, Fujifilm flash white-balance naming, Apple/FLIR/JVC/GE/Reconyx/Microsoft/Nintendo/Sanyo scalar MakerNote labels, current Canon RF/Nikon Z lens labels, an ambiguous Pentax Sigma/Samsung/Tokina lens-family label, EXIF/XMP GPS timestamp composites, EXIF `OffsetTime*`/`SubSecTime*` date composition with normalized-instant conflict checks, separate camera/destination/shown/created GPS roles with scope-aware structured-location conflicts, language-aware descriptive roles, structured creator-contact/event/person/organization/product/artwork/rights/license/release records, independent privacy/policy sensitivity, computational, thermal, stitch/panorama capture state, and vendor-private fields. | High, about 98-99%. |
+| Query | Find entries by name, fuzzy term, or semantic group, then expose normalized query candidates, structured interpretation records, bounded cross-family concept resolutions, transfer hints, sensitivity, and conflict flags for crop/border/active-area, exposure/gain, color/WB/profile/source-color-transform, orientation, date/time, GPS, descriptive fields including contact/event/person/organization/product/artwork/rights/license/release semantics, lens-correction, computational/thermal/stitch, RAW/source-processing fields, and BMFF derived-image construction and tiled-image configuration evidence across standard and vendor metadata. | High, about 96-98%. |
 | Creation | Build fresh metadata entries from host-provided values. | Medium, about 55-65%. |
 | Editing | Modify existing logical metadata entries while preserving valid surrounding structure. | Medium, about 60-70%. |
 | Transfer | Move metadata between files using explicit compatible-file or rendered-image safety policies. | Medium-high, about 80-85%. |
@@ -99,8 +99,9 @@ candidate source entries, source families, preferred entries, normalized
 compare keys, parsed date/time fields, date/time precision, timezone kind, GPS
 altitude-reference state, distinct destination/shown/created coordinate roles,
 structured-location scope, normalized descriptive language, additive
-collection preference, generic structured-record scope for rights/licensor
-records, canonical geometry origin/size/rect/margins,
+collection preference, structured record kinds and scopes for editorial,
+rights, license, and release records, independent policy sensitivity,
+canonical geometry origin/size/rect/margins,
 normalized exposure values, full normalized value vectors for grouped
 matrix/vector/table records, transfer hints, compatible and rendered safety
 booleans, and same-role conflict flags. This is deliberately an

docs/development.md

@@ -84,12 +84,13 @@ resolved independently within each scope. Use
 Descriptive concepts reconcile standard EXIF, IPTC IIM, Dublin Core,
 XMP Rights, Photoshop, IPTC Core/Extension, and PLUS title/headline,
 description, creator, keyword/subject, location, copyright, rights/license,
-credit, and source fields. Scalar conflicts are isolated by normalized
-language and structured location scope; creator, keyword, location-identifier,
-rights-holder, and licensor values are additive collections whose duplicate
-values select one preferred source. Structured owner/licensor members also
-carry a `record_scope`, such as `Licensor[1]`, so hosts can keep associated
-names and identifiers together.
+credit, source, creator-contact, event, person, organization, product,
+artwork/object, encoded-rights-expression, license-constraint, and release
+fields. Scalar conflicts are isolated by normalized language and structured
+location scope; additive collections retain distinct values. Structured
+members carry both a `record_kind` and `record_scope`, such as `person` plus
+`Person[1]`, so hosts can keep associated names, identifiers, descriptions,
+contacts, constraints, and release records together.
 Treat this as an inspection and policy input rather than an automatic metadata
 rewrite decision; source-bound color, lens, and RAW-processing values still need
 rendered-transfer safety filtering. Each candidate also carries a transfer
@@ -106,6 +107,13 @@ diagnostics distinguish stored RAW samples from rendered pixels before
 choosing keep/drop actions. Rendered-transfer drop messages distinguish source
 color transforms, white balance, lens correction, source RAW curves/linearity
 metadata, source-bound RAW processing, and target-owned image properties.
+
+`sensitivity` is a separate policy signal with `none`, `personal_contact`,
+`person_identity`, `location`, and `legal_rights` values. A candidate marked
+`safe` can still be privacy- or policy-sensitive. Hosts that publish or share
+images should review or remove sensitive metadata according to their own user
+consent, privacy, and rights policies; OpenMeta does not drop it automatically
+merely because it is sensitive.
 Hosts can localize or replace the wording, but they do not need to invent the
 basic safe/drop/rewrite reasons.