-
Notifications
You must be signed in to change notification settings - Fork 0
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
Can we have multiple instances of the same Annotation associated to a certain Node? #32
Comments
I think there's not much to be gained by having this constraint. It's a constraint that M2-authors can put in themselves, if they like. |
Ok, so in general we should allow for multiple instances of the same Annotation to be associated with a certain Node. |
Does this mean that we should have a flag |
I would leave it unspecified (in the M2), and just allow multiple instances of the same Annotation being applied to a particular Node (in the M1). If constraints are necessary these should be specified next to/in conjunction with the M2 (in a nice constraint language which we need to have anyway). |
I think we decided on this in #13: An |
I'm reluctant to say anything more about this, but: Is it even necessary to have a |
In the end it is only a constraint -- we can still have an (invalid) model that has two instances of the same annotation (with I don't recall the discussion around this exactly. One argument was the influence on APIs ( Shall we raise this again next week? |
When to call a model "valid" is also still very much up for debate, so we might want to tackle that one first ;) |
Latest round of discussion on 2023-10-27 In general: We don't have enough experience to make an informed decision. Pro (having
Con:
|
We've decided some time ago not to have |
Let's suppose that I have an
Annotation
calledDocumentationComment
. Can I have multiple instances of this Annotation associated to the same Node? Is this true for all the Annotation or should this be something we define for each Annotation?The text was updated successfully, but these errors were encountered: