glam/schemas/20251121/linkml/modules/classes/DigitalPlatform.yaml

id: https://nde.nl/ontology/hc/class/digital-platform
name: digital_platform_class
title: DigitalPlatform Class
imports:
- linkml:types
- ./Custodian
- ./CustodianObservation
- ./ReconstructionActivity
- ./DigitalPlatformType
- ./DigitalPlatformTypes
- ./AuxiliaryDigitalPlatform
- ./TimeSpan
- ./CollectionManagementSystem
- ./DataServiceEndpoint
- ./OAIPMHEndpoint
- ./SearchAPI
- ./METSAPI
- ./FileAPI
- ./IIPImageServer
- ./EADDownload
- ../slots/auxiliary_platforms
- ../slots/has_or_had_powered_by_cm
- ../slots/has_or_had_access_restriction
- ../slots/preservation_level
- ../slots/has_or_had_api_endpoint
- ../slots/metadata_standard
- ../slots/sparql_endpoint
- ../slots/oai_pmh_endpoint
- ../slots/platform_type
- ../slots/platform_name
- ../slots/storage_location
- ../slots/serves_finding_aid
- ./ReconstructedEntity
- ../slots/has_or_had_data_service_endpoint
- ../slots/collection_web_address
- ../slots/fixity_check_date
- ../slots/homepage_web_address
- ../slots/iiif_support
- ../slots/inventory_web_address
- ../slots/linked_data
- ../slots/platform_id
- ../slots/programming_language
- ../slots/refers_to_custodian
- ../slots/repository_software
- ../slots/specificity_annotation
- ../slots/template_specificity
- ../slots/temporal_extent
- ../slots/was_derived_from
- ../slots/was_generated_by
- ./SpecificityAnnotation
- ./TemplateSpecificityScores
prefixes:
  linkml: https://w3id.org/linkml/
  hc: https://nde.nl/ontology/hc/
  schema: http://schema.org/
  foaf: http://xmlns.com/foaf/0.1/
  dcat: http://www.w3.org/ns/dcat#
  dcterms: http://purl.org/dc/terms/
  crm: http://www.cidoc-crm.org/cidoc-crm/
  doap: http://usefulinc.com/ns/doap#
  premis: http://www.loc.gov/premis/rdf/v3/
  prov: http://www.w3.org/ns/prov#
classes:
  DigitalPlatform:
    is_a: ReconstructedEntity
    class_uri: schema:WebSite
    description: "Digital platform or online system associated with a heritage custodian.\n\n**CRITICAL DISTINCTION**:\n\n\
      **DigitalPlatform CLASS** (this class):\n- Represents the DIGITAL INFRASTRUCTURE of any custodian\n- Used by PHYSICAL\
      \ institutions (museums, archives, libraries) to represent their websites\n- Used by DIGITAL-FIRST institutions to represent\
      \ their primary platform\n- Examples: Rijksmuseum website, museum online catalog, archive digital portal\n\n**DigitalPlatformType**\
      \ (custodian type):\n- Classification for DIGITAL-FIRST custodians (online-only, no physical building)\n- Example: Europeana\
      \ (aggregation platform), Internet Archive (born-digital)\n\n**Decision Rules**:\n\n1. **Physical Institution with Website**:\n\
      \   - Custodian.custodian_type = MUSEUM/ARCHIVE/LIBRARY (not DIGITAL_PLATFORM)\n   - Custodian.digital_platform → DigitalPlatform\
      \ instance (this class)\n   - Example: Rijksmuseum (MUSEUM) has Rijksstudio (DigitalPlatform)\n\n2. **Digital-First\
      \ Institution**:\n   - Custodian.custodian_type = DIGITAL_PLATFORM (DigitalPlatformType)\n   - Custodian.digital_platform\
      \ → DigitalPlatform instance (primary platform)\n   - Example: Europeana (DIGITAL_PLATFORM) operates at https://europeana.eu/\n\
      \n**Relationship to Custodian Hub**:\n\nDigitalPlatform is DIRECTLY connected to Custodian via refers_to_custodian,\n\
      just like CustodianPlace, CustodianName, and CustodianLegalStatus.\n\nThis allows modeling:\n- Multiple digital platforms\
      \ per custodian (website + API + mobile app)\n- Platform evolution over time (temporal validity)\n- Platform features\
      \ and technical capabilities\n- Access points for digital heritage\n\n- Schema.org: schema:WebSite (primary), schema:WebApplication\n\
      - DCAT: dcat:Catalog (for aggregation platforms), dcat:DataService (for APIs)\n- FOAF: foaf:homepage, foaf:Document\n\
      - CIDOC-CRM: crm:E73_Information_Object (digital objects)\n\n**Example - Physical Museum with Digital Platform**:\n\
      ```yaml\nCustodian:\n  hc_id: \"https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804\"\n  preferred_label: \"Rijksmuseum\"\
      \n  custodian_type: MUSEUM  # Physical institution\n  digital_platform:\n    - platform_name: \"Rijksmuseum Website\"\
      \n      homepage_web_address: \"https://www.rijksmuseum.nl/\"\n      platform_type: DISCOVERY_PORTAL\n      iiif_support:\
      \ true\n      linked_data: true\n```\n\n**Example - Digital-First Platform**:\n```yaml\nCustodian:\n  hc_id: \"https://nde.nl/ontology/hc/eu-europeana\"\
      \n  preferred_label: \"Europeana\"\n  custodian_type: DIGITAL_PLATFORM  # Digital-first\n  digital_platform:\n    -\
      \ platform_name: \"Europeana Platform\"\n      homepage_web_address: \"https://www.europeana.eu/\"\n      platform_type:\
      \ AGGREGATION_PLATFORM\n      api_endpoint: \"https://api.europeana.eu/\"\n      iiif_support: true\n      linked_data:\
      \ true\n      programming_languages: [\"Java\", \"Python\", \"JavaScript\"]\n```\n"
    exact_mappings:
    - schema:WebSite
    - foaf:homepage
    close_mappings:
    - schema:WebApplication
    - schema:SoftwareApplication
    - dcat:Catalog
    - dcat:DataService
    - crm:E73_Information_Object
    - doap:Project
    - premis:IntellectualEntity
    related_mappings:
    - foaf:Document
    - schema:SoftwareApplication
    - dcat:accessURL
    slots:
    - has_or_had_access_restriction
    - has_or_had_api_endpoint
    - auxiliary_platforms
    - collection_web_address
    - has_or_had_data_service_endpoint
    - fixity_check_date
    - homepage_web_address
    - iiif_support
    - inventory_web_address
    - linked_data
    - metadata_standard
    - oai_pmh_endpoint
    - platform_id
    - platform_name
    - platform_type
    - has_or_had_powered_by_cm
    - preservation_level
    - programming_language
    - refers_to_custodian
    - repository_software
    - serves_finding_aid
    - sparql_endpoint
    - specificity_annotation
    - storage_location
    - template_specificity
    - temporal_extent
    - was_derived_from
    - was_generated_by
    slot_usage:
      platform_id:
        slot_uri: dcterms:identifier
        description: 'Unique identifier for this digital platform instance.

          Format: URI following NDE Heritage Custodian ontology conventions.

          '
        range: uriorcurie
        required: true
        identifier: true
        examples:
        - value: https://nde.nl/ontology/hc/platform/rijksmuseum-website
          description: Platform ID for Rijksmuseum website
      platform_name:
        slot_uri: schema:name
        description: 'Human-readable name for this digital platform.


          Examples:

          - "Rijksmuseum Website"

          - "Europeana Platform"

          - "National Archives Digital Repository"

          - "Museum API"

          '
        range: string
        required: true
        examples:
        - value: Rijksmuseum Website
          description: Main website name
        - value: Europeana Platform
          description: Aggregation platform name
      platform_type:
        slot_uri: dcterms:type
        description: "Type of digital platform using DigitalPlatformType class hierarchy.\n\n**Class-based Type System** (replaces\
          \ DigitalPlatformTypeEnum):\n\nPlatform types are organized into 8 high-level categories:\n- REPOSITORY: Digital\
          \ archives, libraries, institutional repositories\n- AGGREGATOR: Aggregation and harvesting platforms  \n- DISCOVERY:\
          \ Search portals, catalogs, discovery interfaces\n- VIRTUAL_HERITAGE: 3D, VR/AR, immersive experiences\n- RESEARCH:\
          \ Research data platforms, annotation tools\n- INTERACTIVE: Crowdsourcing, social, user contribution\n- COMMERCE:\
          \ Licensing, print-on-demand, e-commerce\n- AUXILIARY: APIs, mobile apps, specialized tools\n\nEach category contains\
          \ multiple concrete subclasses with Wikidata mappings.\nSee DigitalPlatformTypes.yaml for 69 concrete platform types.\n\
          \nA platform may have multiple types (e.g., digital archive + aggregator).\n"
        range: DigitalPlatformType
        multivalued: true
        required: false
        examples:
        - value: DigitalArchivePlatform
          description: Digital archive platform (wd:Q1224984)
        - value: AggregationPlatform
          description: Aggregation platform (wd:Q7894)
      homepage_web_address:
        slot_uri: foaf:homepage
        description: 'Primary homepage URL for this digital platform.


          FOAF: homepage for main web address.


          This is the entry point users access to interact with the platform.

          Must be a valid HTTP/HTTPS URL.

          '
        range: uri
        required: true
        pattern: ^https?://
        examples:
        - value: https://www.rijksmuseum.nl/
          description: Rijksmuseum homepage
        - value: https://www.europeana.eu/
          description: Europeana homepage
      collection_web_address:
        slot_uri: dcat:accessURL
        description: 'URLs for accessing digital collections on this platform.


          DCAT: accessURL for collection access points.


          Examples:

          - "https://www.rijksmuseum.nl/nl/rijksstudio" (Rijksstudio collections)

          - "https://www.europeana.eu/en/collections" (Europeana collections browse)

          - "https://archive.org/details/texts" (Internet Archive text collections)

          '
        range: uri
        multivalued: true
        examples:
        - value: https://www.rijksmuseum.nl/nl/rijksstudio
          description: Rijksstudio collection access
      inventory_web_address:
        slot_uri: dcat:landingPage
        description: 'URLs for archival inventories, finding aids, or collection catalogs.


          DCAT: landingPage for human-readable collection descriptions.


          Examples:

          - "https://www.nationaalarchief.nl/onderzoeken/index" (National Archives inventories)

          - "https://archief.amsterdam/inventarissen" (Amsterdam City Archives inventories)

          '
        range: uri
        multivalued: true
        examples:
        - value: https://www.nationaalarchief.nl/onderzoeken/index
          description: National Archives finding aids
      has_or_had_api_endpoint:
        slot_uri: dcat:endpointURL
        description: 'API endpoint URL for programmatic access.


          DCAT: endpointURL for API base address.


          Examples:

          - "https://api.europeana.eu/record/v2/" (Europeana REST API)

          - "https://www.rijksmuseum.nl/api/" (Rijksmuseum API)

          - "https://archive.org/advancedsearch.php" (Internet Archive API)

          '
        range: uri
        examples:
        - value: https://api.europeana.eu/record/v2/
          description: Europeana REST API endpoint
      sparql_endpoint:
        slot_uri: dcat:endpointURL
        description: 'SPARQL endpoint URL for linked data queries.


          DCAT: endpointURL for SPARQL service.


          Indicates platform supports RDF triple queries.


          Examples:

          - "https://api.europeana.eu/sparql" (Europeana SPARQL)

          - "https://data.collectienederland.nl/sparql" (Collectie Nederland SPARQL)

          '
        range: uri
        examples:
        - value: https://api.europeana.eu/sparql
          description: Europeana SPARQL endpoint
      oai_pmh_endpoint:
        slot_uri: dcat:endpointURL
        description: 'OAI-PMH endpoint URL for metadata harvesting.


          DCAT: endpointURL for OAI-PMH service.


          Supports Open Archives Initiative Protocol for Metadata Harvesting.


          Examples:

          - "https://www.europeana.eu/oai" (Europeana OAI-PMH)

          - "https://repository.example.edu/oai" (Institutional repository OAI-PMH)

          '
        range: uri
        examples:
        - value: https://www.europeana.eu/oai
          description: Europeana OAI-PMH endpoint
      programming_language:
        slot_uri: doap:programming-language
        description: 'Programming languages used to build this platform.


          DOAP: programming-language for software implementation languages.

          (DOAP = Description of a Project, W3C vocabulary for software projects)


          Examples:

          - "Java", "Python", "JavaScript", "Ruby", "PHP"

          - "TypeScript", "Go", "Rust"


          Useful for technical assessment and developer onboarding.

          '
        range: string
        multivalued: true
        examples:
        - value: Java
          description: Primary backend language
        - value: Python
          description: Data processing language
        - value: JavaScript
          description: Frontend language
      repository_software:
        slot_uri: doap:repository
        description: 'Repository or content management software powering this platform.


          DOAP: repository for software/system identification.

          (DOAP = Description of a Project, W3C vocabulary for software projects)


          Examples:

          - "DSpace 7.x"

          - "Fedora Commons 6.x"

          - "CollectiveAccess"

          - "ResourceSpace"

          - "Omeka S"

          - "Custom-built"

          '
        range: string
        examples:
        - value: DSpace 7.2
          description: Digital repository software
      has_or_had_powered_by_cm:
        slot_uri: crm:P33i_was_used_by
        range: CollectionManagementSystem
        multivalued: true
        required: false
        description: "Collection Management System(s) powering this digital platform.\n\nCIDOC-CRM: P33i_was_used_by (inverse\
          \ of P33_used_specific_technique).\nThe CMS provides the backend/technique for the digital platform.\n\n**Bidirectional\
          \ Relationship**:\n- Forward: DigitalPlatform → CollectionManagementSystem (powered_by_cms)\n- Reverse: CollectionManagementSystem\
          \ → DigitalPlatform (powers_platform)\n\n**Use Cases**:\n1. \"What CMS powers this website?\" → Follow powered_by_cms\n\
          2. \"What websites use CollectiveAccess?\" → Follow powers_platform\n3. Technical assessment: Determine backend\
          \ infrastructure of platforms\n\n**Notes**:\n- Multivalued: Platform may use multiple CMS (e.g., hybrid architecture)\n\
          - If null, CMS may be unknown or platform is custom-built\n- Distinct from repository_software: CMS is the full\
          \ system, \n  repository_software is the underlying software package\n"
        examples:
        - value: https://nde.nl/ontology/hc/cms/rijksmuseum-adlib
          description: Platform powered by Rijksmuseum's Adlib CMS
      iiif_support:
        slot_uri: dcterms:conformsTo
        description: 'Does this platform support IIIF (International Image Interoperability Framework)?


          Dublin Core: conformsTo indicates standard compliance.

          When true, implies conformance to IIIF API specifications:

          - https://iiif.io/api/image/3/ (Image API 3.0)

          - https://iiif.io/api/presentation/3/ (Presentation API 3.0)


          IIIF enables:

          - Image API (deep zoom, tiles)

          - Presentation API (manifests, viewers)

          - Content Search API (full-text search)

          - Authentication API (access control)


          Boolean true/false or null if unknown.

          '
        range: boolean
        examples:
        - value: true
          description: Platform supports IIIF
        - value: false
          description: No IIIF support
      linked_data:
        slot_uri: dcterms:conformsTo
        description: 'Does this platform provide linked open data (RDF)?


          Dublin Core: conformsTo indicates LOD compliance.


          Linked data features:

          - RDF triples (Turtle, JSON-LD, N-Triples)

          - SPARQL endpoint

          - Dereferenceable URIs

          - Linked to external vocabularies (Wikidata, Getty, etc.)


          Boolean true/false or null if unknown.

          '
        range: boolean
        examples:
        - value: true
          description: Platform provides linked data
        - value: false
          description: No linked data
      metadata_standard:
        slot_uri: dcterms:conformsTo
        description: 'Metadata standards implemented by this platform.


          Dublin Core: conformsTo for standard compliance.


          Examples:

          - "Dublin Core"

          - "MARC21"

          - "EAD (Encoded Archival Description)"

          - "LIDO"

          - "MODS"

          - "EDM (Europeana Data Model)"

          - "Schema.org"

          - "CIDOC-CRM"

          '
        range: string
        multivalued: true
        examples:
        - value: Dublin Core
          description: Basic descriptive standard
        - value: MARC21
          description: Library catalog standard
      has_or_had_access_restriction:
        slot_uri: dcterms:accessRights
        description: 'Access restrictions or rights management for this platform.


          Dublin Core: accessRights for access control.


          Examples:

          - "Public access"

          - "Registration required"

          - "Institutional access only"

          - "API key required"

          - "Subscription-based"

          - "Restricted to researchers"

          '
        range: string
        examples:
        - value: Public access
          description: Open to all users
        - value: API key required
          description: Developer registration needed
      has_auxiliary_platform:
        slot_uri: dcterms:hasPart
        description: "Subordinate or project-based digital platforms associated with this main DigitalPlatform.\n\n**DCAT\
          \ Alignment**:\n\n`dcterms:hasPart` - Links main catalog/platform to sub-catalogs.\n\n**Hierarchical Pattern - Mirrors\
          \ CustodianName/CustodianAppellation**:\n\n- DigitalPlatform (main entry point) → primary foaf:homepage\n- AuxiliaryDigitalPlatform\
          \ (project sites) → secondary platforms\n\nLike CustodianAppellation provides alternative names for CustodianName,\n\
          AuxiliaryDigitalPlatform provides subordinate platforms for DigitalPlatform.\n\n**Use Cases**:\n\n1. **Project Websites**:\
          \ Research project portals, grant-funded sites\n2. **Exhibition Microsites**: Temporary exhibition portals, virtual\
          \ tours\n3. **APIs and Tools**: Developer APIs, collection browsers, mobile apps\n4. **Legacy/Archived**: Previous\
          \ website versions, deprecated systems\n5. **Educational Portals**: Teacher resources, learning modules\n\n**Example\
          \ - Rijksmuseum**:\n```yaml\nDigitalPlatform:\n  platform_name: \"Rijksmuseum Website\"\n  homepage_web_address:\
          \ \"https://www.rijksmuseum.nl/\"\n  has_auxiliary_platform:\n    - platform_name: \"Rijksstudio\"\n      auxiliary_platform_type:\
          \ PROJECT_WEBSITE\n    - platform_name: \"Rijksmuseum Data API\"\n      auxiliary_platform_type: API_ENDPOINT\n\
          \    - platform_name: \"Night Watch Experience\"\n      auxiliary_platform_type: EXHIBITION_MICROSITE\n```\n\n**Temporal\
          \ Considerations**:\n\nAuxiliary platforms often have finite lifespans:\n- Exhibition microsite opens/closes with\
          \ exhibition\n- Project portals run during funding period\n- Legacy platforms archived but accessible\n\nEach AuxiliaryDigitalPlatform\
          \ tracks has_or_had_archival_status and archived_at.\n"
        range: AuxiliaryDigitalPlatform
        multivalued: true
        inlined_as_list: true
        required: false
        examples:
        - value:
          - platform_name: Rijksstudio
            auxiliary_platform_type: PROJECT_WEBSITE
            platform_url: https://www.rijksmuseum.nl/nl/rijksstudio
          - platform_name: Rijksmuseum Data API
            auxiliary_platform_type: API_ENDPOINT
            platform_url: https://data.rijksmuseum.nl/
          description: Rijksmuseum subordinate digital platforms
      temporal_extent:
        slot_uri: crm:P4_has_time-span
        description: 'Temporal period during which this platform was operational.


          CIDOC-CRM: P4_has_time-span for platform lifecycle.


          Use when:

          - Platform launched (begin_of_the_begin)

          - Platform shut down (end_of_the_end)

          - Platform migrated to new URL


          For current platforms, leave end dates null.

          '
        range: TimeSpan
        examples:
        - value:
            begin_of_the_begin: '2008-11-20'
            end_of_the_begin: '2008-11-20'
          description: Europeana launched November 20, 2008
      was_derived_from:
        slot_uri: prov:wasDerivedFrom
        description: 'CustodianObservation(s) documenting this platform.


          PROV-O: wasDerivedFrom for observation provenance.


          Examples:

          - Website screenshot observation

          - API documentation observation

          - Technical specification observation

          '
        range: CustodianObservation
        multivalued: true
        required: false
      was_generated_by:
        slot_uri: prov:wasGeneratedBy
        description: 'ReconstructionActivity that created this platform record.


          PROV-O: wasGeneratedBy for generation activity.


          If present: Platform record created through formal reconstruction

          If null: Platform record extracted directly

          '
        range: ReconstructionActivity
        required: false
      refers_to_custodian:
        slot_uri: dcterms:references
        description: 'The Custodian hub that operates this digital platform (REQUIRED).


          Links the digital platform to the custodian it represents.


          Dublin Core: references for entity reference.

          '
        range: Custodian
        required: true
        examples:
        - value: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
          description: Rijksmuseum custodian hub
      preservation_level:
        slot_uri: premis:policy
        description: 'Digital preservation commitment level for this platform.


          PREMIS: policy links to PreservationPolicy describing preservation actions.


          Values indicate the level of digital preservation applied:

          - "full_preservation": Complete digital preservation with format migration

          - "bit_preservation": Bit-level integrity preservation only

          - "access_only": No formal preservation commitment

          - "dark_archive": Preserved but not publicly accessible


          See Library of Congress PREMIS preservation levels:

          http://id.loc.gov/vocabulary/preservation/preservationLevelRole

          '
        range: string
        required: false
        examples:
        - value: full_preservation
          description: Complete digital preservation with format migration
        - value: bit_preservation
          description: Bit-level integrity preservation only
      storage_location:
        slot_uri: premis:storedAt
        description: 'Primary storage location or infrastructure for digital content.


          PREMIS: storedAt links to StorageLocation describing where content is stored.


          Examples:

          - "AWS S3 eu-west-1" (cloud storage)

          - "On-premises data center, Amsterdam" (physical infrastructure)

          - "DANS Data Archive" (trusted digital repository)

          - "Internet Archive" (third-party preservation service)


          Note: For detailed storage information, use auxiliary properties

          or link to a dedicated StorageLocation entity.

          '
        range: string
        required: false
        examples:
        - value: AWS S3 eu-west-1
          description: Cloud storage in EU West region
        - value: DANS Data Archive
          description: Dutch trusted digital repository
      fixity_check_date:
        slot_uri: premis:fixity
        description: "Date of most recent fixity/checksum verification.\n\nPREMIS: fixity property indicates integrity verification.\n\
          \nRegular fixity checks ensure digital content has not been \ncorrupted or altered. This date indicates when the\
          \ last \nverification occurred.\n\nBest practices recommend:\n- Monthly fixity checks for actively accessed content\n\
          - Quarterly checks for archived content\n- Immediate verification after any storage migration\n"
        range: date
        required: false
        examples:
        - value: '2025-11-15'
          description: Last fixity check date
      serves_finding_aid:
        slot_uri: rico:isOrWasProviderOf
        range: uriorcurie
        multivalued: true
        inlined_as_list: true
        required: false
        description: 'Finding aids hosted/served by this digital platform.


          **INVERSE RELATIONSHIP**:

          - Forward: FindingAid.served_by → DigitalPlatform (finding aid is served by platform)

          - Inverse: DigitalPlatform.serves_finding_aids → FindingAid[] (platform serves finding aids)


          **RiC-O ALIGNMENT**:

          `rico:isOrWasProviderOf` - The agent (platform) provides the finding aid.


          **USE CASES**:

          1. "What finding aids are available on this platform?" → Follow serves_finding_aids

          2. "Which platforms host EAD finding aids?" → Query platforms with EAD-format finding aids

          3. Platform inventory: Map all finding aids served by each digital infrastructure


          **EXAMPLES**:

          - National Archives website serves collection guides and inventories

          - Regional archive portal serves EAD-encoded finding aids

          '
        examples:
        - value: https://nde.nl/ontology/hc/finding-aid/na/voc-inventory
          description: VOC Archives inventory finding aid
        - value: https://nde.nl/ontology/hc/finding-aid/rm/paintings-catalogue
          description: Rijksmuseum paintings catalogue
      has_or_had_data_service_endpoint:
        slot_uri: dcat:servesDataset
        range: DataServiceEndpoint
        multivalued: true
        inlined_as_list: true
        required: false
        description: "Data service endpoints exposed by this digital platform.\n\n**DCAT ALIGNMENT**:\n`dcat:servesDataset`\
          \ - Links a DataService to the datasets it serves.\n\n**ENDPOINT TYPES**:\nThis polymorphic slot can contain any\
          \ subclass of DataServiceEndpoint:\n- OAIPMHEndpoint: OAI-PMH metadata harvesting endpoints\n- SearchAPI: REST/JSON\
          \ search API endpoints\n- METSAPI: METS document retrieval endpoints\n- FileAPI: File/asset download endpoints\n\
          - IIPImageServer: IIP/IIIF image server endpoints\n- EADDownload: EAD finding aid download endpoints\n\n**USE CASES**:\n\
          1. \"What APIs does this platform expose?\" → Follow data_service_endpoints\n2. \"Which platforms support OAI-PMH?\"\
          \ → Filter by OAIPMHEndpoint type\n3. Technical integration: Discover all programmatic access points\n4. Data harvesting:\
          \ Find endpoints for metadata aggregation\n\n**RELATIONSHIP TO SIMPLE SLOTS**:\n- `api_endpoint`, `sparql_endpoint`,\
          \ `oai_pmh_endpoint` (simple URI slots) provide quick access\n- `data_service_endpoints` provides FULL documentation\
          \ of each endpoint with:\n  - Protocol details and versions\n  - Authentication requirements\n  - Rate limits and\
          \ usage policies\n  - Response formats and metadata standards\n  - Discovery provenance\n\n**EXAMPLE - Nationaal\
          \ Archief**:\n```yaml\nhas_or_had_data_service_endpoint:\n  - endpoint_type: OAIPMHEndpoint\n    endpoint_name:\
          \ \"NA OAI-PMH Endpoint\"\n    endpoint_url: \"https://www.nationaalarchief.nl/onderzoeken/oai-pmh\"\n    protocol_version:\
          \ \"2.0\"\n    metadata_prefixes: [\"oai_dc\", \"ese\", \"edm\"]\n  - endpoint_type: SearchAPI\n    endpoint_name:\
          \ \"NA Search API\"\n    endpoint_url: \"https://www.nationaalarchief.nl/onderzoeken/api/zoeken\"\n    http_method:\
          \ POST\n    response_formats: [\"application/json\"]\n  - endpoint_type: IIPImageServer\n    endpoint_name: \"NA\
          \ Image Server\"\n    endpoint_url: \"https://service.archief.nl/iipsrv\"\n    server_software: \"IIPImage Server\"\
          \n    iiif_image_api_version: \"3.0\"\n```\n"
        examples:
        - value:
          - endpoint_id: https://nde.nl/ontology/hc/endpoint/na-oai-pmh
            endpoint_name: Nationaal Archief OAI-PMH
            endpoint_url: https://www.nationaalarchief.nl/onderzoeken/oai-pmh
            protocol: OAI_PMH
            status: ACTIVE
          description: Nationaal Archief data service endpoints
      specificity_annotation:
        range: SpecificityAnnotation
        inlined: true
      template_specificity:
        range: TemplateSpecificityScores
        inlined: true
    comments:
    - DigitalPlatform is DIRECTLY linked to Custodian hub (not a subclass of CustodianObservation)
    - Used by BOTH physical institutions (website) and digital-first custodians (primary platform)
    - 'Multivalued on Custodian: one custodian can have multiple platforms (website + API + mobile app)'
    - Temporal validity tracks platform lifecycle (launch, shutdown, migration)
    - IIIF and linked data flags enable discovery of interoperable platforms
    - 'NEW: auxiliary_platforms links to subordinate AuxiliaryDigitalPlatform sites (project portals, microsites, APIs)'
    - Hierarchical pattern mirrors CustodianName → CustodianAppellation relationship
    see_also:
    - https://schema.org/WebSite
    - https://www.w3.org/ns/dcat
    - https://iiif.io/
    - http://usefulinc.com/ns/doap#
    - https://www.loc.gov/standards/premis/
    examples:
    - value:
        platform_id: https://nde.nl/ontology/hc/platform/rijksmuseum-website
        platform_name: Rijksmuseum Website
        platform_type:
        - DiscoveryPortal
        homepage_web_address: https://www.rijksmuseum.nl/
        collection_web_address:
        - https://www.rijksmuseum.nl/nl/rijksstudio
        api_endpoint: https://www.rijksmuseum.nl/api/
        iiif_support: true
        linked_data: true
        metadata_standard:
        - Dublin Core
        - LIDO
        access_restrictions: Public access, API key required for API
        refers_to_custodian: https://nde.nl/ontology/hc/nl-nh-ams-m-rm-q190804
      description: Rijksmuseum digital platform (physical museum with website)
    - value:
        platform_id: https://nde.nl/ontology/hc/platform/europeana
        platform_name: Europeana Platform
        platform_type:
        - AggregationPlatform
        - APIService
        homepage_web_address: https://www.europeana.eu/
        collection_web_address:
        - https://www.europeana.eu/en/collections
        api_endpoint: https://api.europeana.eu/record/v2/
        sparql_endpoint: https://api.europeana.eu/sparql
        oai_pmh_endpoint: https://www.europeana.eu/oai
        programming_language:
        - Java
        - Python
        - JavaScript
        iiif_support: true
        linked_data: true
        metadata_standard:
        - EDM (Europeana Data Model)
        - Dublin Core
        - LIDO
        - EAD
        access_restrictions: Public access, API key required for API
        temporal_extent:
          begin_of_the_begin: '2008-11-20'
          end_of_the_begin: '2008-11-20'
        refers_to_custodian: https://nde.nl/ontology/hc/eu-europeana
      description: Europeana platform (digital-first aggregation platform)