Skip to content

Add hasFormat relation for alternate-format sibling Building Blocks - #84

Draft
fmigneault wants to merge 1 commit into
opengeospatial:masterfrom
crim-ca:feature/hasformat-relation
Draft

Add hasFormat relation for alternate-format sibling Building Blocks#84
fmigneault wants to merge 1 commit into
opengeospatial:masterfrom
crim-ca:feature/hasformat-relation

Conversation

@fmigneault

Copy link
Copy Markdown
Member
  • Add hasFormat to bblock.schema.yaml: identifiers of other Building Blocks that represent the same content as this one, in an alternate format (dcterms:hasFormat/isFormatOf) - siblings, not a specialization like isProfileOf
  • Normalize bblocks:// prefixes on hasFormat like the existing dependsOn/isProfileOf handling
  • Map hasFormat to dct:hasFormat in the JSON-LD register context; also add the previously-missing seeAlso -> rdfs:seeAlso context term (the property name itself had no mapping before)
  • Companion viewer-side rendering (undirected, dashed edges distinct from isProfileOf/dependsOn): Make dependency graph height configurable and fix graph rendering gaps ogcincubator/bblocks-viewer#14

hasFormat represents dcterms:hasFormat/isFormatOf semantics: two Building
Blocks that are substantially the same content in another format (e.g. a
JSON vs an XML serialization of the same model), as opposed to isProfileOf's
specialization/inheritance semantics.

- bblock.schema.yaml: add hasFormat (array of bblock references), symmetric,
  intended to be declared on every sibling that should be linked
- models.py: normalize bblocks:// prefixes on hasFormat like dependsOn/isProfileOf
- register-context.yaml: map hasFormat to dct:hasFormat, and add the
  previously-missing seeAlso -> rdfs:seeAlso mapping (the property name itself
  had no JSON-LD context term, unlike its raw rdfs:seeAlso IRI counterpart)
fmigneault added a commit to crim-ca/bblocks-prov-jsonld-alt that referenced this pull request Sep 11, 2026
The 5 W3C PROV representation profiles are alternate formats of the same
content, not just generically "related" - dcterms:hasFormat/isFormatOf is
the precise relation (see companion opengeospatial/bblocks-postprocess#84).
w3c-prov-base's own seeAlso to the OGC PROV Chain forms block is unrelated
and unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant