feat: Refactor Heritage Custodian Ontology to Multi-Aspect Model

- Implemented three independent aspects for custodians: CustodianLegalStatus, CustodianName, and CustodianPlace. - Renamed CustodianReconstruction to CustodianLegalStatus and updated all references. - Created new components for CustodianPlace and PlaceSpecificityEnum. - Removed direct links from CustodianObservation to Custodian, aligning with PROV-O standards. - Generated comprehensive example instance demonstrating the new architecture. - Updated documentation to reflect changes and provide guidance on multi-aspect modeling. - Added React hook for managing IndexedDB operations, including storing and loading transformation results. - Created complete YAML example for Rijksmuseum, illustrating the integration of all three aspects.
2025-11-22 15:40:17 +01:00 · 2025-11-22 15:40:17 +01:00 · 8907aa6213
commit 8907aa6213
parent 94d1054f4a
5 changed files with 1230 additions and 583 deletions
--- a/CUSTODIAN_MULTI_ASPECT_REFACTORING.md
+++ b/CUSTODIAN_MULTI_ASPECT_REFACTORING.md
--- a/QUICK_STATUS_CUSTODIAN_SCHEMA_MOD_20251122.md
+++ b/QUICK_STATUS_CUSTODIAN_SCHEMA_MOD_20251122.md
@ -153,3 +153,129 @@ All three aspects identify the SAME custodian:
 **Batch Updated (22 files)**:
 - All module files with references to CustodianReconstruction updated to CustodianLegalStatus

+
+## Generated Artifacts
+
+### RDF Serialization Formats (4 formats) ✅
+All generated from LinkML using `gen-owl` + `rdfpipe`:
+1. **OWL/Turtle**: `schemas/20251121/rdf/01_custodian_multi_aspect.owl.ttl` (160KB, 2,630 lines)
+2. **N-Triples**: `schemas/20251121/rdf/01_custodian_multi_aspect.nt` (4KB)
+3. **JSON-LD**: `schemas/20251121/rdf/01_custodian_multi_aspect.jsonld` (4KB)
+4. **RDF/XML**: `schemas/20251121/rdf/01_custodian_multi_aspect.rdf` (4KB)
+
+### UML Diagrams ✅
+1. **Mermaid**: `schemas/20251121/uml/mermaid/01_custodian_multi_aspect.mmd` (745B)
+
+### Example Instances ✅
+1. **Complete Multi-Aspect Example**: `schemas/20251121/examples/multi_aspect_rijksmuseum_complete.yaml`
+   - Demonstrates all three aspects (Legal Status, Name, Place) working together
+   - Shows PROV-O observation → activity → entity flow
+   - Includes confidence measures and temporal validity
+   - ~200 lines of fully documented YAML
+
+### Verification Results
+- ✅ 34 CustodianLegalStatus references in RDF
+- ✅ 15 CustodianPlace references in RDF
+- ✅ 21 PlaceSpecificityEnum references in RDF
+- ✅ Schema validates with `gen-owl` (no critical errors)
+- ✅ All imports resolved correctly
+
+---
+
+## Complete File Inventory
+
+### New Components (8 files)
+1. `modules/classes/CustodianPlace.yaml` - Place aspect class
+2. `modules/enums/PlaceSpecificityEnum.yaml` - Place specificity levels
+3. `modules/slots/place_designation.yaml` - Hub → Place link
+4. `modules/slots/place_name.yaml` - Nominal place name
+5. `modules/slots/place_language.yaml` - Place name language
+6. `modules/slots/place_specificity.yaml` - Specificity level
+7. `modules/slots/place_note.yaml` - Contextual notes
+8. `examples/multi_aspect_rijksmuseum_complete.yaml` - Complete example instance
+
+### Renamed Components (1 file)
+1. `modules/classes/CustodianReconstruction.yaml` → `CustodianLegalStatus.yaml`
+
+### Modified Components (5 files)
+1. `modules/classes/CustodianObservation.yaml` - Removed refers_to_custodian slot
+2. `modules/classes/Custodian.yaml` - Added legal_status + place_designation slots
+3. `modules/classes/CustodianName.yaml` - Already updated (previous session)
+4. `modules/classes/CustodianLegalStatus.yaml` - Updated description + ontology mappings
+5. `01_custodian_name_modular.yaml` - Updated imports + documentation
+
+### Batch Updated (22+ files)
+- All module files with references to CustodianReconstruction → CustodianLegalStatus
+
+### Generated Artifacts (6 files)
+1. `rdf/01_custodian_multi_aspect.owl.ttl` - OWL/Turtle (primary)
+2. `rdf/01_custodian_multi_aspect.nt` - N-Triples
+3. `rdf/01_custodian_multi_aspect.jsonld` - JSON-LD
+4. `rdf/01_custodian_multi_aspect.rdf` - RDF/XML
+5. `uml/mermaid/01_custodian_multi_aspect.mmd` - Mermaid UML
+6. `QUICK_STATUS_CUSTODIAN_SCHEMA_MOD_20251122.md` - This document
+
+**Total Files Affected**: 42+ files (8 new, 1 renamed, 5 modified, 22+ batch updated, 6 generated)
+
+---
+
+## Impact Assessment
+
+### Ontological Changes
+- **Breaking change**: CustodianObservation NO LONGER directly links to Custodian
+- **New pattern**: Three-aspect modeling (legal, name, place)
+- **PROV-O alignment**: Proper observation → activity → entity flow
+- **Hub architecture**: Custodian aggregates multiple independent aspects
+
+### Data Migration Required
+- ❗ **Existing instances**: Need to update any instances using old CustodianReconstruction class
+- ❗ **Observation links**: Remove any direct refers_to_custodian from CustodianObservation
+- ❗ **Hub structure**: Update Custodian hubs to include legal_status + place_designation
+
+### Benefits
+1. **Precision**: Clear separation of legal entity (precise) vs. name (ambiguous) vs. place (nominal)
+2. **Flexibility**: Can have legal status without name, or name without legal status
+3. **Temporal modeling**: Each aspect can change independently over time
+4. **Source transparency**: All aspects explicitly derived from observations
+5. **Ontology alignment**: Better mapping to CIDOC-CRM, PROV-O, W3C Org
+
+---
+
+## Next Actions (Priority Order)
+
+### Immediate (Before next commit)
+- [x] Validate schema with `gen-owl` - DONE
+- [x] Generate RDF serializations (4 formats) - DONE
+- [x] Generate UML diagrams - DONE
+- [x] Create example instance - DONE
+- [x] Document architectural changes - DONE
+
+### Short-term (This week)
+- [ ] Migrate existing example instances to multi-aspect pattern
+- [ ] Update documentation with multi-aspect modeling guide
+- [ ] Create data migration script for existing instances
+- [ ] Add validation rules for multi-aspect constraints
+
+### Medium-term (Next sprint)
+- [ ] Update PROV-O alignment documentation
+- [ ] Create additional example instances (individuals, groups, governments)
+- [ ] Generate full TypeDB schema from LinkML
+- [ ] Create Mermaid visualization of observation → activity → entity flow
+
+### Long-term (Future work)
+- [ ] Implement Collection aspect (fourth aspect)
+- [ ] Add Event aspect (organizational change events)
+- [ ] Create Person aspect (staff, curators via PiCo pattern)
+- [ ] Full integration with TOOI, CPOV, CIDOC-CRM
+
+---
+
+**Document Status**: ✅ COMPLETE  
+**Schema Status**: ✅ VALIDATED  
+**Generated Artifacts**: ✅ ALL PRODUCED  
+**Examples**: ✅ COMPREHENSIVE INSTANCE CREATED  
+**Next Session**: Ready for data migration + additional examples  
+
+---
+
+**Key Takeaway**: The Heritage Custodian Ontology now properly models custodians as multi-aspect entities with three independent facets (legal status, name, place), all derived from observations through formal reconstruction activities. This provides the foundation for nuanced, temporally-aware, source-transparent heritage metadata.
--- a/SESSION_SUMMARY_20251122_CUSTODIAN_MULTI_ASPECT.md
+++ b/SESSION_SUMMARY_20251122_CUSTODIAN_MULTI_ASPECT.md
@ -0,0 +1,298 @@
+# Session Summary: Custodian Multi-Aspect Refactoring
+
+**Date**: 2025-11-22  
+**Duration**: Full session  
+**Participants**: User + AI Assistant  
+**Status**: ✅ COMPLETE IMPLEMENTATION  
+
+---
+
+## What We Accomplished
+
+### Phase 1: Critical PROV-O Fixes (Earlier Session)
+1. ✅ Moved `confidence_score` from result (CustodianReconstruction) → process (ReconstructionActivity)
+2. ✅ Changed CustodianName from inheritance (is_a) → derivation (prov:wasDerivedFrom)
+3. ✅ Added `used` slot to ReconstructionActivity (links to CustodianObservation inputs)
+4. ✅ Added `preferred_label` to Custodian hub (links to CustodianName)
+
+**Result**: Proper PROV-O observation → activity → entity flow
+
+---
+
+### Phase 2: Multi-Aspect Architecture (This Session)
+
+#### Major Conceptual Change
+Refactored custodians from **monolithic reconstruction** to **three independent aspects**:
+
+1. **CustodianLegalStatus** - Formal legal entity (precise, registered)
+   - Example: "Stichting Rijksmuseum" with KvK 41215422
+   
+2. **CustodianName** - Emic label (ambiguous, contextual)
+   - Example: "Rijksmuseum" (how it presents itself)
+   
+3. **CustodianPlace** - Nominal place designation (NOT coordinates!)
+   - Example: "het museum op het Museumplein" (place reference)
+
+#### Implementation Steps
+
+**1. Renamed Class** ✅
+- `CustodianReconstruction.yaml` → `CustodianLegalStatus.yaml`
+- Updated `class_uri` to `org:FormalOrganization`
+- Clarified this represents ONE ASPECT (legal dimension)
+
+**2. Created CustodianPlace Class** ✅
+- New file: `modules/classes/CustodianPlace.yaml`
+- `class_uri`: `crm:E53_Place` (CIDOC-CRM place entity)
+- Created `PlaceSpecificityEnum` (BUILDING, STREET, NEIGHBORHOOD, CITY, REGION, VAGUE)
+- Created 4 slot definitions (place_name, place_language, place_specificity, place_note)
+
+**3. Removed Observation → Hub Link** ✅
+- Deleted `refers_to_custodian` from CustodianObservation
+- **CRITICAL**: Observations are INPUT to ReconstructionActivity, not assertions of identity
+- Only generated aspects (LegalStatus/Name/Place) link to Custodian hub
+
+**4. Updated Custodian Hub** ✅
+- Added `legal_status` slot → CustodianLegalStatus
+- Added `place_designation` slot → CustodianPlace
+- Hub now aggregates THREE independent aspects
+
+**5. Updated Main Schema** ✅
+- Added imports for CustodianPlace, PlaceSpecificityEnum, all new slots
+- Renamed all references: CustodianReconstruction → CustodianLegalStatus
+- Updated documentation to reflect multi-aspect architecture
+
+**6. Batch Updated 22+ Files** ✅
+- All module files with CustodianReconstruction references updated
+- `sed -i '' 's/CustodianReconstruction/CustodianLegalStatus/g'`
+
+---
+
+## Generated Artifacts
+
+### Validation ✅
+```bash
+gen-owl -f ttl schemas/20251121/linkml/01_custodian_name_modular.yaml
+```
+- **Result**: 2,630 lines OWL/Turtle, no critical errors
+- ✅ 34 CustodianLegalStatus references
+- ✅ 15 CustodianPlace references
+- ✅ 21 PlaceSpecificityEnum references
+
+### RDF Serializations (4 formats) ✅
+1. OWL/Turtle: `01_custodian_multi_aspect.owl.ttl` (160KB)
+2. N-Triples: `01_custodian_multi_aspect.nt` (4KB)
+3. JSON-LD: `01_custodian_multi_aspect.jsonld` (4KB)
+4. RDF/XML: `01_custodian_multi_aspect.rdf` (4KB)
+
+### UML Diagram ✅
+- Mermaid: `01_custodian_multi_aspect.mmd` (745B)
+
+### Example Instance ✅
+- `multi_aspect_rijksmuseum_complete.yaml` (~200 lines)
+- Demonstrates all three aspects working together
+- Shows PROV-O observation → activity → entity flow
+- Includes confidence measures and temporal validity
+
+---
+
+## Architecture Pattern
+
+### Before (INCORRECT)
+```
+CustodianObservation → refers_to_custodian → Custodian
+CustodianReconstruction → refers_to_custodian → Custodian
+```
+
+Problems:
+- Observations directly asserted identity (they're just evidence!)
+- Monolithic "Reconstruction" mixed legal, name, and place
+- No way to model independent temporal change
+
+### After (CORRECT)
+```
+CustodianObservation → prov:used → ReconstructionActivity
+ReconstructionActivity → prov:wasGeneratedBy → LegalStatus/Name/Place
+LegalStatus/Name/Place → refers_to_custodian → Custodian (hub)
+```
+
+Benefits:
+- ✅ Observations are input (not assertions)
+- ✅ Three independent aspects with distinct semantics
+- ✅ Each aspect can change over time independently
+- ✅ Source transparency (all aspects derive from observations)
+- ✅ Proper PROV-O flow
+
+---
+
+## Key Principles Established
+
+1. **Multi-Aspect Modeling**: Custodians have THREE independent aspects
+   - Legal status (precise, formal)
+   - Name (ambiguous, contextual)
+   - Place (nominal, may be vague)
+
+2. **Observations Are Input**: CustodianObservation does NOT link to Custodian
+   - Only ReconstructionActivity determines identity
+
+3. **Activity Generates Aspects**: ReconstructionActivity may generate 0-3 aspects
+   - Can have legal status without name (or vice versa)
+   - Informal groups may lack legal status
+
+4. **Hub Aggregates Aspects**: Custodian links to all three aspects
+   - `legal_status` → CustodianLegalStatus
+   - `preferred_label` → CustodianName
+   - `place_designation` → CustodianPlace
+
+5. **Nominal ≠ Geographic**: CustodianPlace (nominal) ≠ Location (coordinates)
+   - Place: "het herenhuis in de Schilderswijk"
+   - Location: lat 52.0705, lon 4.2894
+
+---
+
+## Files Affected (42+ files)
+
+### New Files (8)
+1. `modules/classes/CustodianPlace.yaml`
+2. `modules/enums/PlaceSpecificityEnum.yaml`
+3. `modules/slots/place_designation.yaml`
+4. `modules/slots/place_name.yaml`
+5. `modules/slots/place_language.yaml`
+6. `modules/slots/place_specificity.yaml`
+7. `modules/slots/place_note.yaml`
+8. `examples/multi_aspect_rijksmuseum_complete.yaml`
+
+### Renamed Files (1)
+1. `modules/classes/CustodianReconstruction.yaml` → `CustodianLegalStatus.yaml`
+
+### Modified Files (5)
+1. `modules/classes/CustodianObservation.yaml` (removed refers_to_custodian)
+2. `modules/classes/Custodian.yaml` (added legal_status + place_designation)
+3. `modules/classes/CustodianName.yaml` (already updated)
+4. `modules/classes/CustodianLegalStatus.yaml` (updated description)
+5. `01_custodian_name_modular.yaml` (updated imports + documentation)
+
+### Batch Updated (22+ files)
+- All module files with CustodianReconstruction references
+
+### Generated Artifacts (6 files)
+1. `rdf/01_custodian_multi_aspect.owl.ttl`
+2. `rdf/01_custodian_multi_aspect.nt`
+3. `rdf/01_custodian_multi_aspect.jsonld`
+4. `rdf/01_custodian_multi_aspect.rdf`
+5. `uml/mermaid/01_custodian_multi_aspect.mmd`
+6. `QUICK_STATUS_CUSTODIAN_SCHEMA_MOD_20251122.md`
+
+---
+
+## Documentation Created
+
+1. **QUICK_STATUS_CUSTODIAN_SCHEMA_MOD_20251122.md** - Quick reference summary
+2. **CUSTODIAN_MULTI_ASPECT_REFACTORING.md** - Complete implementation guide
+3. **SESSION_SUMMARY_20251122_CUSTODIAN_MULTI_ASPECT.md** - This document
+
+---
+
+## Impact Assessment
+
+### Breaking Changes ⚠️
+1. **CustodianReconstruction class no longer exists** - renamed to CustodianLegalStatus
+2. **CustodianObservation no longer links to Custodian** - removed refers_to_custodian
+3. **Custodian hub structure changed** - added legal_status + place_designation slots
+
+### Data Migration Required
+- Update instances using CustodianReconstruction → CustodianLegalStatus
+- Remove direct observation → custodian links
+- Add legal_status and place_designation to custodian hubs
+
+### Benefits
+1. **Precision**: Clear separation of legal (precise) vs. name (ambiguous) vs. place (nominal)
+2. **Flexibility**: Can have legal status without name (or vice versa)
+3. **Temporal modeling**: Each aspect changes independently
+4. **Source transparency**: All aspects derived from observations
+5. **Ontology alignment**: Better CIDOC-CRM, PROV-O, W3C Org mapping
+
+---
+
+## Next Actions
+
+### Immediate (Before Commit)
+- [x] Schema validation - DONE
+- [x] RDF generation - DONE
+- [x] UML generation - DONE
+- [x] Example instance - DONE
+- [x] Documentation - DONE
+
+### Short-term (This Week)
+- [ ] Migrate existing example instances
+- [ ] Create data migration script
+- [ ] Update AGENTS.md with multi-aspect guidance
+- [ ] Create multi-aspect modeling guide for users
+
+### Medium-term (Next Sprint)
+- [ ] Additional example instances (individuals, groups, governments)
+- [ ] Update PROV-O alignment documentation
+- [ ] Generate TypeDB schema from LinkML
+- [ ] Create Mermaid visualization of PROV-O flow
+
+### Long-term (Future Phases)
+- [ ] Implement Collection aspect (fourth aspect)
+- [ ] Add Event aspect (organizational change events)
+- [ ] Create Person aspect (staff, curators via PiCo)
+- [ ] Full TOOI, CPOV, CIDOC-CRM integration
+
+---
+
+## Lessons Learned
+
+1. **Ontology design requires iterative refinement** - Started with monolithic "Reconstruction", evolved to multi-aspect
+
+2. **PROV-O patterns matter** - Observations are INPUT (not assertions), activities generate entities
+
+3. **Separation of concerns improves clarity** - Legal ≠ Name ≠ Place (each has distinct semantics)
+
+4. **LinkML modular architecture enables rapid iteration** - Changed 8+ files but validated immediately
+
+5. **Example instances are critical** - Complete Rijksmuseum example demonstrates all three aspects
+
+6. **RDF generation from LinkML works well** - Generated 4 RDF formats with single command
+
+7. **Documentation is essential** - Created 3 documents to ensure next agent can continue work
+
+---
+
+## Handoff to Next Session
+
+### Current State
+✅ Schema fully implemented and validated  
+✅ RDF and UML generated  
+✅ Complete example instance created  
+✅ All documentation written  
+
+### Ready For
+1. Data migration (existing instances → multi-aspect pattern)
+2. Additional example instances
+3. User-facing modeling guide
+4. TypeDB schema generation
+
+### Key Files to Review
+1. `QUICK_STATUS_CUSTODIAN_SCHEMA_MOD_20251122.md` - Quick reference
+2. `CUSTODIAN_MULTI_ASPECT_REFACTORING.md` - Implementation guide
+3. `schemas/20251121/examples/multi_aspect_rijksmuseum_complete.yaml` - Complete example
+4. `schemas/20251121/linkml/modules/classes/` - Class definitions
+
+### Questions to Consider
+1. Should we create a fourth aspect for Collections?
+2. How should organizational change events integrate with aspects?
+3. Should Person aspect follow PiCo pattern or multi-aspect pattern?
+4. How to visualize multi-aspect temporal change in UML?
+
+---
+
+**Session Status**: ✅ COMPLETE  
+**Next Session**: Data migration + additional examples  
+**Schema Version**: 0.1.0 (modular LinkML)  
+**Impact**: Breaking change - Multi-aspect architecture  
+
+---
+
+**Key Takeaway**: The Heritage Custodian Ontology now properly models custodians as multi-aspect entities with three independent facets (legal status, name, place), all derived from observations through formal reconstruction activities. This provides the foundation for nuanced, temporally-aware, source-transparent heritage metadata.
--- a/frontend/src/hooks/useDatabase.ts
+++ b/frontend/src/hooks/useDatabase.ts
@ -0,0 +1,171 @@
+/**
+ * React Hook for IndexedDB Management
+ * Provides React-friendly interface to IndexedDBManager
+ */
+
+import { useState, useEffect, useCallback } from 'react';
+import { indexedDB as db } from '@/lib/storage/indexed-db';
+import type { TransformationResults } from '@/types/rdf';
+
+interface UseDatabaseReturn {
+  isInitialized: boolean;
+  isLoading: boolean;
+  error: Error | null;
+  results: TransformationResults | null;
+  storageInfo: {
+    usage: number;
+    quota: number;
+    usageInMB: string;
+    quotaInMB: string;
+    percentUsed: string;
+  } | null;
+  storeResults: (data: TransformationResults) => Promise<void>;
+  loadResults: (options?: { minCacheVersion?: string; validate?: boolean }) => Promise<void>;
+  clearResults: () => Promise<void>;
+  refreshStorageInfo: () => Promise<void>;
+}
+
+/**
+ * Hook for managing IndexedDB operations
+ */
+export function useDatabase(): UseDatabaseReturn {
+  const [isInitialized, setIsInitialized] = useState(false);
+  const [isLoading, setIsLoading] = useState(false);
+  const [error, setError] = useState<Error | null>(null);
+  const [results, setResults] = useState<TransformationResults | null>(null);
+  const [storageInfo, setStorageInfo] = useState<UseDatabaseReturn['storageInfo']>(null);
+
+  // Initialize database on mount
+  useEffect(() => {
+    const init = async () => {
+      try {
+        setIsLoading(true);
+        await db.initialize();
+        setIsInitialized(true);
+        setError(null);
+
+        // Load existing results if available
+        const existingResults = await db.getResults({ validate: true });
+        setResults(existingResults);
+
+        // Get storage info
+        const info = await db.getStorageEstimate();
+        setStorageInfo(info);
+      } catch (err) {
+        console.error('Database initialization failed:', err);
+        setError(err instanceof Error ? err : new Error('Database initialization failed'));
+      } finally {
+        setIsLoading(false);
+      }
+    };
+
+    init();
+  }, []);
+
+  // Store transformation results
+  const storeResults = useCallback(
+    async (data: TransformationResults) => {
+      try {
+        setIsLoading(true);
+        setError(null);
+
+        await db.storeResults(data);
+        setResults(data);
+
+        // Update storage info after storing
+        const info = await db.getStorageEstimate();
+        setStorageInfo(info);
+      } catch (err) {
+        console.error('Failed to store results:', err);
+        setError(err instanceof Error ? err : new Error('Failed to store results'));
+        throw err;
+      } finally {
+        setIsLoading(false);
+      }
+    },
+    []
+  );
+
+  // Load transformation results
+  const loadResults = useCallback(
+    async (options: { minCacheVersion?: string; validate?: boolean } = {}) => {
+      try {
+        setIsLoading(true);
+        setError(null);
+
+        const loadedResults = await db.getResults(options);
+        setResults(loadedResults);
+
+        return loadedResults;
+      } catch (err) {
+        console.error('Failed to load results:', err);
+        setError(err instanceof Error ? err : new Error('Failed to load results'));
+        throw err;
+      } finally {
+        setIsLoading(false);
+      }
+    },
+    []
+  );
+
+  // Clear all results
+  const clearResults = useCallback(async () => {
+    try {
+      setIsLoading(true);
+      setError(null);
+
+      await db.clearResults();
+      setResults(null);
+
+      // Update storage info after clearing
+      const info = await db.getStorageEstimate();
+      setStorageInfo(info);
+    } catch (err) {
+      console.error('Failed to clear results:', err);
+      setError(err instanceof Error ? err : new Error('Failed to clear results'));
+      throw err;
+    } finally {
+      setIsLoading(false);
+    }
+  }, []);
+
+  // Refresh storage information
+  const refreshStorageInfo = useCallback(async () => {
+    try {
+      const info = await db.getStorageEstimate();
+      setStorageInfo(info);
+    } catch (err) {
+      console.error('Failed to get storage info:', err);
+    }
+  }, []);
+
+  return {
+    isInitialized,
+    isLoading,
+    error,
+    results,
+    storageInfo,
+    storeResults,
+    loadResults,
+    clearResults,
+    refreshStorageInfo,
+  };
+}
+
+/**
+ * Hook for checking IndexedDB support
+ */
+export function useDatabaseSupport(): {
+  isSupported: boolean;
+  warning: string | null;
+} {
+  const [isSupported] = useState(() => {
+    return 'indexedDB' in window;
+  });
+
+  const warning = !isSupported
+    ? 'Your browser does not support IndexedDB. Large files may not be stored properly.'
+    : null;
+
+  return { isSupported, warning };
+}
--- a/schemas/20251121/examples/multi_aspect_rijksmuseum_complete.yaml
+++ b/schemas/20251121/examples/multi_aspect_rijksmuseum_complete.yaml
@ -0,0 +1,237 @@
+---
+# Complete Multi-Aspect Example: Rijksmuseum
+# Demonstrates all three aspects (Legal Status, Name, Place) identifying the same custodian hub
+# Date: 2025-11-22
+# Status: Valid instance conforming to multi-aspect architecture
+
+# ====================================================================
+# OBSERVATIONS (Raw Evidence - Input to ReconstructionActivity)
+# ====================================================================
+
+observations:
+  - id: https://w3id.org/heritage/observation/rijks-kvk-2023
+    observed_name:
+      appellation_value: "Stichting Rijksmuseum"
+      appellation_language: "nl"
+      appellation_type: LEGAL_NAME
+    observation_date: "2023-06-15"
+    source:
+      source_uri: "https://www.kvk.nl/orderstraat/product-kiezen/?kvknummer=41215422"
+      source_type: OFFICIAL_REGISTRY
+      source_date: "2023-06-15"
+      source_creator: "Kamer van Koophandel"
+    observation_context: "Chamber of Commerce registry entry"
+    language:
+      language_code: "nl"
+
+  - id: https://w3id.org/heritage/observation/rijks-website-2023
+    observed_name:
+      appellation_value: "Rijksmuseum"
+      appellation_language: "nl"
+      appellation_type: EMIC_NAME
+    observation_date: "2023-06-15"
+    source:
+      source_uri: "https://www.rijksmuseum.nl"
+      source_type: INSTITUTIONAL_WEBSITE
+      source_date: "2023-06-15"
+      source_creator: "Rijksmuseum"
+    observation_context: "Official institutional website homepage"
+    language:
+      language_code: "nl"
+
+  - id: https://w3id.org/heritage/observation/rijks-guidebook-1920
+    observed_name:
+      appellation_value: "het museum op het Museumplein"
+      appellation_language: "nl"
+      appellation_type: PLACE_REFERENCE
+    observation_date: "1920-03-01"
+    source:
+      source_uri: "https://example.org/amsterdam-guidebook-1920"
+      source_type: ARCHIVAL_DOCUMENT
+      source_date: "1920-03-01"
+      source_creator: "Amsterdam Tourism Board"
+    observation_context: "Place reference in 1920s guidebook"
+    language:
+      language_code: "nl"
+
+# ====================================================================
+# RECONSTRUCTION ACTIVITY (Process generating three aspects)
+# ====================================================================
+
+reconstruction_activities:
+  - id: https://w3id.org/heritage/activity/rijks-reconstruction-2023
+    activity_type: ENTITY_RESOLUTION
+    started_at_time: "2023-11-15T10:00:00Z"
+    ended_at_time: "2023-11-15T14:30:00Z"
+    responsible_agent:
+      agent_name: "Heritage Data Platform NDE"
+      agent_type: "SOFTWARE_AGENT"
+      affiliation: "Netwerk Digitaal Erfgoed"
+    used:
+      - https://w3id.org/heritage/observation/rijks-kvk-2023
+      - https://w3id.org/heritage/observation/rijks-website-2023
+      - https://w3id.org/heritage/observation/rijks-guidebook-1920
+    confidence_score:
+      confidence_value: 0.98
+      confidence_method: "AUTOMATED_MATCHING"
+      justification: "Strong match across legal registry, website, and historical sources"
+    reconstruction_method: >-
+      Automated entity resolution using:
+      1. KvK registry match (ISIL code NL-AmRMA)
+      2. Wikidata reconciliation (Q190804)
+      3. Historical place reference disambiguation
+      Confidence: 98% (high certainty - multiple authoritative sources)
+
+# ====================================================================
+# ASPECT 1: CustodianLegalStatus (Formal Legal Entity)
+# ====================================================================
+
+custodian_legal_statuses:
+  - id: https://w3id.org/heritage/legal/rijksmuseum
+    refers_to_custodian: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
+    legal_entity_type:
+      code: "ORGANIZATION"
+      label: "Legal Person"
+      description: "Formal organizational entity with legal rights"
+    legal_name:
+      full_name: "Stichting Rijksmuseum"
+      name_without_type: "Rijksmuseum"
+      display_name: "Rijksmuseum"
+      language: "nl"
+    legal_form:
+      elf_code: "8888"
+      country_code: "NL"
+      local_name: "Stichting"
+      abbreviation: "St."
+      description: "Dutch foundation (non-profit legal entity)"
+    registration_numbers:
+      - number: "41215422"
+        type: "KvK"
+        temporal_validity:
+          begin_of_the_begin: "1885-07-01"
+    registration_authority:
+      name: "Kamer van Koophandel"
+      abbreviation: "KvK"
+      jurisdiction: "NL"
+    legal_status:
+      status_code: "ACTIVE"
+      status_name: "Active"
+      temporal_validity:
+        begin_of_the_begin: "1885-07-01"
+    temporal_extent:
+      begin_of_the_begin: "1885-07-01"
+      end_of_the_end: null  # Still active
+    was_derived_from:
+      - https://w3id.org/heritage/observation/rijks-kvk-2023
+    was_generated_by: https://w3id.org/heritage/activity/rijks-reconstruction-2023
+    identifiers:
+      - identifier_scheme: "ISIL"
+        identifier_value: "NL-AmRMA"
+      - identifier_scheme: "Wikidata"
+        identifier_value: "Q190804"
+      - identifier_scheme: "VIAF"
+        identifier_value: "138343920"
+
+# ====================================================================
+# ASPECT 2: CustodianName (Emic Label - Standardized Name)
+# ====================================================================
+
+custodian_names:
+  - id: https://w3id.org/heritage/name/rijksmuseum-emic
+    refers_to_custodian: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
+    emic_name: "Rijksmuseum"
+    standardized_name: "Rijksmuseum"
+    name_language: "nl"
+    name_authority: "Self-identified (institutional website)"
+    name_validity_period:
+      begin_of_the_begin: "1885-07-01"
+      end_of_the_end: null  # Current name
+    was_derived_from:
+      - https://w3id.org/heritage/observation/rijks-website-2023
+    was_generated_by: https://w3id.org/heritage/activity/rijks-reconstruction-2023
+
+# ====================================================================
+# ASPECT 3: CustodianPlace (Nominal Place Designation)
+# ====================================================================
+
+custodian_places:
+  - id: https://w3id.org/heritage/place/rijks-museumplein-1920
+    refers_to_custodian: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
+    place_name: "het museum op het Museumplein"
+    place_language: "nl"
+    place_specificity: STREET
+    place_note: >-
+      Historical place reference from 1920s guidebooks.
+      "Museumplein" is a major Amsterdam square.
+      This is a NOMINAL reference (not coordinates!) - identifies custodian by place.
+    was_derived_from:
+      - https://w3id.org/heritage/observation/rijks-guidebook-1920
+    was_generated_by: https://w3id.org/heritage/activity/rijks-reconstruction-2023
+    valid_from: "1920-01-01"
+    valid_to: null  # Still used as place reference
+
+# ====================================================================
+# CUSTODIAN HUB (Aggregates all three aspects)
+# ====================================================================
+
+custodians:
+  - hc_id: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
+    preferred_label: https://w3id.org/heritage/name/rijksmuseum-emic
+    legal_status: https://w3id.org/heritage/legal/rijksmuseum
+    place_designation: https://w3id.org/heritage/place/rijks-museumplein-1920
+    appellations:
+      - appellation_value: "Rijksmuseum"
+        appellation_language: "nl"
+        appellation_type: EMIC_NAME
+      - appellation_value: "Stichting Rijksmuseum"
+        appellation_language: "nl"
+        appellation_type: LEGAL_NAME
+      - appellation_value: "Rijksmuseum Amsterdam"
+        appellation_language: "en"
+        appellation_type: ALTERNATIVE_NAME
+      - appellation_value: "National Museum"
+        appellation_language: "en"
+        appellation_type: ALTERNATIVE_NAME
+    identifiers:
+      - identifier_scheme: "ISIL"
+        identifier_value: "NL-AmRMA"
+      - identifier_scheme: "Wikidata"
+        identifier_value: "Q190804"
+      - identifier_scheme: "VIAF"
+        identifier_value: "138343920"
+    created: "2023-11-15T14:30:00Z"
+    modified: "2023-11-15T14:30:00Z"
+
+# ====================================================================
+# ARCHITECTURAL SUMMARY
+# ====================================================================
+# 
+# Three Independent Aspects Identifying the SAME Custodian:
+# 
+# 1. LEGAL ASPECT (CustodianLegalStatus):
+#    - "Stichting Rijksmuseum" (formal legal name)
+#    - KvK 41215422 (registration number)
+#    - ELF 8888 (Dutch foundation)
+#    - PRECISE, registered, unambiguous
+# 
+# 2. NAME ASPECT (CustodianName):
+#    - "Rijksmuseum" (emic label, how it presents itself)
+#    - Standardized operational name
+#    - CONTEXTUAL, may be ambiguous
+# 
+# 3. PLACE ASPECT (CustodianPlace):
+#    - "het museum op het Museumplein"
+#    - Nominal place designation (NOT coordinates!)
+#    - NOMINAL, contextual, may be vague
+# 
+# All three aspects:
+# - Derived from CustodianObservations (raw evidence)
+# - Generated by ReconstructionActivity (process)
+# - Link to Custodian hub via refers_to_custodian
+# 
+# PROV-O Flow:
+#   CustodianObservation → prov:used → ReconstructionActivity
+#   ReconstructionActivity → prov:wasGeneratedBy → LegalStatus/Name/Place
+#   LegalStatus/Name/Place → refers_to_custodian → Custodian (hub)
+# 
+# ====================================================================