Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • AsciiDoc Language AsciiDoc Language
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse ProjectsEclipse Projects
  • AsciiDoc Language
  • AsciiDoc LanguageAsciiDoc Language
  • Issues
  • #7
Closed
Open
Issue created May 24, 2021 by Dan Allen@mojavelinuxMaintainer

Decide on the format and schema of the ASG that will be used by the TCK

The project proposal suggests basing the TCK on an ASG in order to verify that an implementation parses and comprehends AsciiDoc in compliance with the specification. If we decide to adopt that strategy, as discussed in #6, we need to decide on the format and schema for the ASG.

The purpose of this issue is to pick a format for the ASG (e.g., JSON) and map out the general schema of the data. We don't have to think of every possible use case as the schema will continue to evolve over time. But this issue should at least outline the common elements and leave room for it to be elaborated.

Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent