Follow-up: coordinate ontology, schema evolution, lenses and headless webhooks #47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Track later research separately from the immediate table acceptance milestone. Existing PR #37 (lenses) and WIP PR #39 (semantic templates) are separate experiments, not prerequisites for the 20 October demo.
Topics: shared predicate/shape identities and namespace policy; schema version/evolution and concurrent changes; lens migrations; backend webhooks using the native NextGraph headless SDK. Do not introduce RDF linked lists. Do not silently change existing predicate identities or treat exploratory call discussion as an approved hashing protocol. Split this tracking issue when a concrete follow-up is selected.
Inventory finding: the existing separate
db-table-editor-issue-trackerapp still encodes ordered fields with list-cell resources. It is outside the 20 October reference editor. Plan an explicit, data-preserving migration to position metadata or another agreed non-linked-list representation; do not silently rewrite existing issue data during the demo work.The lenses-react app is a separate piece of research we can leave in its folder.
Same for table-editor-templates, I'm not so sure about how the Atomic templates fit into the bigger picture.
In the longer run I want to evolve towards something like versioned linked data including versioned schemas. For now, I will just support schema edits through the table editor and deal with incoming schema edits, as well as same for incoming and outgoing data edits but not schema edit history or data edit history.