Entity Dataset Bridge

WebMEM Entity Dataset Bridge (WM-EDB) Specification

Part of the WebMEM Protocol
Location: /specification/entity-dataset-bridge/
Status: v1.0 (Draft)
Namespaces (URNs):
urn:webmem:entitydatasetbridge:1.0 (core dataset bridge binding)
Last Updated: 2026-03-08

Entity Dataset Bridge Overview
Relationship to SDT (YAML-in-HTML)
Profiles & Conformance
Bridge Model (DatasetBridgeBinding)
EDB-CORE Field Mapping
Canonicalization & Integrity
Minimal Architecture Diagram
Minimal Example (Schema Dataset Bridge)
Minimal Example (IdentityFragment Payload)
Producer Rules
Consumer Rules
Future Extensions
Changelog

1) Entity Dataset Bridge Overview

WebMEM Entity Dataset Bridge (WM-EDB) defines the handshake between a
known semantic vocabulary (Schema.org Dataset) and an embedded structured
data source contained directly within an HTML document.

WM-EDB allows the document itself to function as a valid dataset host, enabling
structured datasets to be embedded and distributed directly within HTML pages.

WM-EDB consists of:

• Dataset Declaration — a Schema.org Dataset node identifying the dataset and associated entity.
• Bridge Binding — a deterministic connection between the dataset declaration and the WebMEM fragment.
• Payload Binding — the structured WebMEM fragment container containing the dataset payload.

In practical terms:

Schema = Map
WebMEM Fragment = Payload
Entity Dataset Bridge = Handshake between the two

2) Relationship to SDT (YAML-in-HTML)

SDT defines page-layer fragments (such as IdentityFragment, DataFragment,
and ExplainerFragment) published via YAML-in-HTML.

WM-EDB defines the semantic bridge connecting those fragments to a
Schema Dataset declaration.

Together they provide:

Map (Schema Dataset) = dataset identity and discoverability
Payload (WebMEM Fragment) = canonical structured dataset

Consumers may parse the Schema layer for discovery and then follow the bridge to
retrieve the structured fragment payload embedded in the page.

3) Profiles & Conformance

EDB-CORE (required):

datasetId, mainEntity, fragmentSelector, encodingFormat

EDB-INT (optional integrity binding):

sha256, datePublished, dateModified

EDB-FULL: EDB-CORE + EDB-INT + provenance and licensing fields.

4) Bridge Model (DatasetBridgeBinding)

The bridge model binds a Schema Dataset node to the embedded WebMEM
fragment payload.

{
"@type": "Dataset",
"@id": "https://davidbynon.com/#identity-fragment",
"name": "WebMEM Identity Fragment for David W. Bynon",
"mainEntity": {
  "@id": "https://davidbynon.com/#person"
},
"distribution": {
  "@type": "DataDownload",
  "encodingFormat": "application/webmem+yaml",
  "contentUrl": "https://davidbynon.com/#identity-fragment"
}
}

5) EDB-CORE Field Mapping

EDB-CORE Field	JSON-LD Location
datasetId	Dataset.@id
mainEntity	Dataset.mainEntity.@id
fragmentSelector	distribution.contentUrl fragment identifier
encodingFormat	distribution.encodingFormat

The fragment selector refers to the fragment identifier portion of the URL:


https://davidbynon.com/#identity-fragment
                       ↑
                  fragmentSelector

6) Canonicalization & Integrity

Integrity fields allow consumers to verify that the payload has not changed.

Canonicalization steps:

Remove BOM if present
Normalize Unicode to NFC
Normalize CR/LF → LF
Encode UTF-8
Compute SHA-256 over canonical bytes

7) Minimal Architecture Diagram


Web Page
   │
   ├── Person (Schema entity)
   │
   ├── Dataset (Schema map)
   │
   └── IdentityFragment (WebMEM payload)
           │
           ▼
        YAML identity dataset

8) Minimal Example (Schema Dataset Bridge)

{
"@context": "https://schema.org",
"@graph": [

{
"@type": "Person",
"@id": "https://davidbynon.com/#person",
"name": "David W. Bynon",
"url": "https://davidbynon.com/"
},

{
"@type": "Dataset",
"@id": "https://davidbynon.com/#identity-fragment",
"name": "WebMEM Identity Fragment for David W. Bynon",
"mainEntityOfPage": "https://davidbynon.com/",
"mainEntity": {
  "@id": "https://davidbynon.com/#person"
},
"distribution": {
  "@type": "DataDownload",
  "encodingFormat": "application/webmem+yaml",
  "contentUrl": "https://davidbynon.com/#identity-fragment"
}
}

]
}

9) Minimal Example (IdentityFragment Payload)

<template id="identity-fragment"
data-visibility-fragment="identity_fragment">

identity_fragment:
  entity_name: "David W. Bynon"
  entity_type: "Person"
  canonical_role: "Healthcare AI Governance Architect"

  domain_scope:
    - "AI Governance"
    - "Deterministic Semantic Architecture"
    - "Regulated Healthcare Systems"

  canonical_domains:
    - "https://davidbynon.com"
    - "https://webmem.com"
    - "https://trustpublishing.org"

  version: "1.0"
  last_updated: "2026-02-25"

</template>

10) Producer Rules

MUST bind the Dataset to a clear primary entity.
MUST ensure the fragment payload exists within the HTML document.
SHOULD use a stable fragment identifier.
SHOULD provide a clear encodingFormat.
MAY include integrity metadata.

11) Consumer Rules

MUST treat the Schema Dataset node as the dataset identity.
SHOULD resolve the embedded fragment and treat it as the canonical dataset payload when integrity checks pass.
MUST ignore unknown fields gracefully.
SHOULD use entity bindings such as mainEntity when interpreting payload meaning.

12) Future Extensions

multi-fragment dataset bindings
signed fragment payloads
dataset federation across pages
additional payload formats (JSON, CSV, XML)

13) Changelog

1.0 (2026-03-08): Initial Entity Dataset Bridge specification.

Contents