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

define the names of syntactic parts of OM objects in 2.1.3 #56

Open
kohlhase opened this issue Oct 5, 2017 · 2 comments
Open

define the names of syntactic parts of OM objects in 2.1.3 #56

kohlhase opened this issue Oct 5, 2017 · 2 comments
Assignees

Comments

@kohlhase
Copy link
Member

kohlhase commented Oct 5, 2017

We often use names for the syntactic parts of the OM objects without really defining them. For instance "binder" is not defined anywhere. I propose to define all of these in 2.1.3 where the syntactic shape of complex OM Objects is first introduced. In particular

  • in (ii) application define "function" and "argument sequence" and maybe "n-th argument" (which is the n+1th child.
  • in (iii) attribution define "syntactic head" ("head" will be defined with flattening), "key", "attribute value", and "attribute sequence".
  • in (iv) binding define "binder", "bound variables", and "body".
  • in (v) error define ????? how do we call S and the A_i?
    And once we have defined these, we can clean up the text below and refer to these definitions via the referencing mechanisms posited in markup for definienda and definienses #55
@kohlhase
Copy link
Member Author

kohlhase commented Oct 5, 2017

I would really like to have the vocab at my disposal when writing about things like alpha-renmaming.

@kohlhase kohlhase added this to the OM2 Revision 2 milestone Oct 8, 2017
@kohlhase
Copy link
Member Author

kohlhase commented Dec 9, 2017

I will start on this in the next days (I am skiing and this is the optimal apres-ski occupation).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants