Skip to content

Design Principle: Data Model vs. Syntax #68

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

Closed
echeran opened this issue Mar 5, 2020 · 1 comment
Closed

Design Principle: Data Model vs. Syntax #68

echeran opened this issue Mar 5, 2020 · 1 comment
Labels
design Design document or issues related to design resolve-candidate This issue appears to have been answered or resolved, and may be closed soon.

Comments

@echeran
Copy link
Collaborator

echeran commented Mar 5, 2020

A dedicated issue for discussing a newly proposed design dimension, similar to those proposed in #50.

Data Model vs. Syntax

Do we focus our efforts on agreeing to a data model of the inputs? Or do we need to think in terms of defining a syntax for the inputs? Can these concerns be decoupled? What are the tradeoffs (advantages / concerns)?

(Issue created from #64)

@mihnita mihnita added the design Design document or issues related to design label Sep 24, 2020
@eemeli eemeli added the resolve-candidate This issue appears to have been answered or resolved, and may be closed soon. label Jun 17, 2023
@eemeli
Copy link
Collaborator

eemeli commented Jun 17, 2023

This seems obsolete. We tried to first work on the data model, got blocked, then figured out the syntax first instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design Design document or issues related to design resolve-candidate This issue appears to have been answered or resolved, and may be closed soon.
Projects
None yet
Development

No branches or pull requests

4 participants