Syntax/Semantics for the system manifest

Open
#70 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
xml
Domain
compilers

Research direction

Start by reviewing the issue's proposal for an explicit EBNF grammar and associated manifest rules, including the XML and HJSON alternatives and SysMLv2/AADL generation use cases. No files or tests are named, so first locate the existing system-manifest parser and validation entry points. Done means the manifest syntax and semantic rules are explicit and support consistent validation and generation across manifest languages.

Written by the indexing model from the issue text.

Description

There was a brief discussion at the summit that maybe using XML for the system description is not the best (hjson anyone?:-) ). Either way, there should be proper grammar (EBNF?) and associated rules for the manifest language.

Why?

  1. then switching between different manifest languages should be trivial
  2. generating the manifest from other tools should be simpler (think SysMLv2/AADL -> microkit)
  3. with proper rules we can ensure the manifest is well formed (I know you are already doing a number of checks, but we should be explicit about it)
Dominant language
Rust
Stars
201
Forks
80
Avg merge
1d 4h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from seL4/microkit

All issues in seL4/microkit

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.