coulomb/markitect-main
2
0
Fork 0
Code Issues 60 Pull Requests Actions 1 Projects 12 Releases 1 Wiki Activity

Define metaschema for JSON schema structure #50

New Issue
Closed
opened 2025-10-01 00:01:13 +00:00 by tegwick · 0 comments
tegwick commented 2025-10-01 00:01:13 +00:00
Owner
Copy Link

UseCase: As a developer working on schema generation, I need a well-defined metaschema that describes the structure and capabilities of MarkiTect JSON schemas, so that I can implement outline-aware schema generation and content instruction features.

Technical Requirements:
Define a JSON Schema specification that extends the standard JSON Schema to include MarkiTect-specific features like heading text capture, content field instructions, and outline structure representation.

Acceptance Criteria:

  • Schema metaschema supports heading text capture
  • Schema metaschema supports content field instructions
  • Schema metaschema supports outline structure representation
  • Schema metaschema is backward compatible with existing schemas
  • Schema metaschema includes validation rules for new features
  • Documentation explains the metaschema structure and usage

Dependencies:

  • Current schema generation system (Issue #5)
  • JSON Schema validation (Issue #7)
UseCase: As a developer working on schema generation, I need a well-defined metaschema that describes the structure and capabilities of MarkiTect JSON schemas, so that I can implement outline-aware schema generation and content instruction features. Technical Requirements: Define a JSON Schema specification that extends the standard JSON Schema to include MarkiTect-specific features like heading text capture, content field instructions, and outline structure representation. Acceptance Criteria: - [ ] Schema metaschema supports heading text capture - [ ] Schema metaschema supports content field instructions - [ ] Schema metaschema supports outline structure representation - [ ] Schema metaschema is backward compatible with existing schemas - [ ] Schema metaschema includes validation rules for new features - [ ] Documentation explains the metaschema structure and usage Dependencies: - Current schema generation system (Issue #5) - JSON Schema validation (Issue #7)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
priority:critical
Critical priority issue
 priority:high
High priority issue
 priority:low
Low priority issue
 priority:medium
Medium priority issue
 status:active
Issues currently being worked on
 status:blocked
Issues blocked by dependencies
 status:done
Completed issues
 status:review
Issues under review
 status:todo
Issues ready to be worked on
 type:bug
Bug report
 type:documentation
Documentation update
 type:enhancement
Enhancement to existing feature
 type:feature
New feature request
 wish
Feature wishlist item - idea to be discussed and refined
 wish/archived
Archived or rejected wishlist item
 wish/discussion
Wishlist item currently being discussed and refined
 wish/draft
Wishlist item with initial draft specification
 wish/ready
Wishlist item ready to become a regular issue
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bubble-reader tegwick
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coulomb/markitect-main#50
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?