Schemas are a very broad term in our system. We are making strong efforts to leverage the power a distributed system offers with a proper Schema System. However, in this note, I refer strictly to constraints on our attributes and attribute values.

I want to start new features with a Product Requirement Documents. This way, I can set the stage based on all our team conversations and user needs, reducing the initial uncertainties of breaking ground on a new project.

I've reached the point where I want to add Status to User Stories. However, we already have Status for Tasks. The problem is that User Stories and Tasks hold different sets of statuses. We need to fix this! I understand that the solution is the Schemas project, and some inspiration is Notion:

The Status attribute should allow different values depending on the document type/context.

For example:

Task.status ∈ {Backlog, In Progress, Done}

UserStory.status ∈ {Draft, Ready, Accepted}

References

Hypermedia Protocol Schemas

Problems Design Constraints Solution Notes and References

Roadmap for Schemas

Arbitrary Metadata Query options Global Schemas Pattern matching Obsidian Ecosystem is a dangerous place

Tables and Attributes Feedback

Please add your feedback to this document!

Could not load embed