[Feature] Add typed parties, relationships, and effective-dated contact points #13

New Issue

2026-07-31T11:39:39+02:00

zemion commented

2026-07-31 11:39:39 +02:00

Context

The historical AdreMa assessment in docs/ADREMA_CAPABILITY_ASSESSMENT.md shows that recipient selection depends on more than a display name and a primary address: person/organization kind, formal salutation, organizational/function context, address purpose, and effective dates determine the usable target.

This issue extends the current vCard-compatible contact baseline without turning Addresses into a second IDM or Organizations master.

Scope

Add local party kinds for person, organization, household, group, and location.
Add formal/display name components, locale, titles, and salutation/addressing metadata.
Add purpose, preference, validity interval, source revision, and provenance to contact points.
Extend postal addresses with care-of/addressee lines, PO box, country code, internal-mail route, and delivery instructions.
Add typed, effective-dated relationships with provenance.
Allow optional stable links to identity, organization, unit, and function provider references through capabilities.
Migrate existing contacts losslessly, treating the current shape as a compatible person/contact baseline.
Surface the new fields through the API and standard address editor UI.

Acceptance Criteria

Addresses remains fully usable when IDM and Organizations are absent.
Optional provider links enrich local parties without copying provider-owned records.
Existing vCard/CardDAV data round-trips without regression; supported KIND/RELATED semantics are preserved where applicable.
Every relationship and contact point can explain its validity and provenance.
Existing contacts and recipient-source consumers have an explicit compatibility path with regression tests.
Field visibility and write decisions remain scope- and policy-aware.

Parent: #1. Related: #10.

## Context The historical AdreMa assessment in `docs/ADREMA_CAPABILITY_ASSESSMENT.md` shows that recipient selection depends on more than a display name and a primary address: person/organization kind, formal salutation, organizational/function context, address purpose, and effective dates determine the usable target. This issue extends the current vCard-compatible contact baseline without turning Addresses into a second IDM or Organizations master. ## Scope - Add local party kinds for person, organization, household, group, and location. - Add formal/display name components, locale, titles, and salutation/addressing metadata. - Add purpose, preference, validity interval, source revision, and provenance to contact points. - Extend postal addresses with care-of/addressee lines, PO box, country code, internal-mail route, and delivery instructions. - Add typed, effective-dated relationships with provenance. - Allow optional stable links to identity, organization, unit, and function provider references through capabilities. - Migrate existing contacts losslessly, treating the current shape as a compatible person/contact baseline. - Surface the new fields through the API and standard address editor UI. ## Acceptance Criteria - Addresses remains fully usable when IDM and Organizations are absent. - Optional provider links enrich local parties without copying provider-owned records. - Existing vCard/CardDAV data round-trips without regression; supported KIND/RELATED semantics are preserved where applicable. - Every relationship and contact point can explain its validity and provenance. - Existing contacts and recipient-source consumers have an explicit compatibility path with regression tests. - Field visibility and write decisions remain scope- and policy-aware. Parent: #1. Related: #10.

zemion added this to the Module And Integration Roadmap milestone 2026-07-31 11:39:39 +02:00

zemion added the module/addresses module/organizations area/api module/idm area/webui codex/ready area/governance area/db

labels 2026-07-31 11:39:39 +02:00

~~zemion referenced this issue 2026-07-31 11:40:57 +02:00~~

[Feature] Complete the Addresses provider for AdreMa distribution lists #1

zemion referenced this issue

2026-07-31 11:40:58 +02:00

[Feature] Add deduplication, merge, address quality, provenance, and audit history #10

zemion commented

2026-07-31 14:49:03 +02:00

Architecture correction: this work does not belong in Addresses.

Organizations already owns unit/function definitions.
IDM already owns effective-dated identity-to-function assignments in #5.
Typed groups and effective-dated identity/group relationships are now tracked in GovOPlaN/govoplan-idm#7.
Addresses retains contact points, postal addressing semantics, vCard round-trip compatibility, and stable links to provider subjects.

Closing as superseded/moved; no Addresses implementation is required for the party/relationship model described here.

Architecture correction: this work does not belong in Addresses. - Organizations already owns unit/function definitions. - IDM already owns effective-dated identity-to-function assignments in #5. - Typed groups and effective-dated identity/group relationships are now tracked in GovOPlaN/govoplan-idm#7. - Addresses retains contact points, postal addressing semantics, vCard round-trip compatibility, and stable links to provider subjects. Closing as superseded/moved; no Addresses implementation is required for the party/relationship model described here.

zemion closed this issue

2026-07-31 14:49:03 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-addresses#13