Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

peer review: <Mitchell Weingust Team 22> Critical Portion of the Document Not Formalized #219

Open
mitcholll opened this issue Jan 21, 2025 · 0 comments
Labels
peer review To be used with different parties for review purposes

Comments

@mitcholll
Copy link

artifact under review.

Design Document

team number (for the team doing the review).

Team 22

description of issue.

One of the requirements for the design document is to formalize an important part of the document, using correct mathematical notation.
The closest to formal mathematical notation I could find is under the MIS of Inference Module section, with Exported Access Programs and State Variables, however, neither were using correct mathematical notation.

For example, 'JSON(tasks = [task_1, ..., task_n) where task_i = id' could be expressed as: tasks = {task_i | task_i = id ∧ 1 ≤ i ≤ n}.

I suggest modifying the MIS of Inference Module section to incorporate formal math notation to meet the criteria.

@CSchank

@mitcholll mitcholll added the peer review To be used with different parties for review purposes label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
peer review To be used with different parties for review purposes
Projects
None yet
Development

No branches or pull requests

1 participant