Schema is recommended, not required on the write path - #1316
Open
joepio wants to merge 1 commit into
Open
Conversation
Apps can persist and sync without publishing Classes or Properties. Resource::set now accepts unknown Property URLs and still enforces datatype when a Property resource exists. Co-authored-by: joepmeindertsma <joepmeindertsma@gmail.com>
joepio
marked this pull request as ready for review
August 29, 2026 00:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related Issues
No issue — answers the question: can an app use
atomic_libwithout publishing an ontology?Yes. Persistence, commits, and sync already work without Classes or Property resources. Atomic Schema stays the recommended path (forms, types, required fields, shared meaning). It is no longer a write-path requirement.
Policy:
planning/optional-schema.md.What changed
Resource::setaccepts an unknown Property URL and trusts theValue. If a Property resource exists, datatype andallowsOnlyare still enforced.defineSchema/ code-first schema remains the recommended on-ramp (planning/json-schema-code-first.md).Checklist