Igor Dejanović

> Great! Let's refer to it as TEP-001 :) Agreed :) > Can I comment it directly in the Wiki. Or do I comment it here. Or do I modify...

> I am thinking if the RREL could also be a separate source: e.g. a string instead of a scope provider, Fully agree. We should allow user to override what...

Ah, I think that current mechanism is good, we just provide a callable which the right signature and register on the metamodel like we do now. We won't do anything...

> Is ~ only applying to "extends" or also to "methods"? I think `~` should apply only on part name thus `extends` in the previous case. In order to mark...

On the other hand `^` marks the whole path subexpression. You could have multiple `^` in a single RREL expression if sequence (`,`) is used as in `^some.path,^some.other.path`.

Github is using git for versioning of Wiki pages which is really nice. You can see [here](https://help.github.com/articles/adding-and-editing-wiki-pages-locally/). So to clone wiki for textX you should do: ``` git clone [email protected]:igordejanovic/textX.wiki...

> If this is okay for you I can start making a short table or list next week... That would be great. Thanks! You can start a new section with...

Looks good. I suggest to start putting these examples at the section `Examples` at the end of TEP-001 document itself and polish them until we are satisfied. One correction in...

Thanks. Looks good. I've fixed RREL expression in [example 2, `Reference.ref`](https://github.com/igordejanovic/textX/wiki/Reference-resolving-expression-language-(RREL)#rrel-implementation-1). We need dot after `instance` and this example reveals that we would need grouping of subpath elements for `*`...

Hi @goto40 FYI, I'll be working on the first stage of implementing RREL parsing and the base infrastructure for its interpretation. After that we should see how to integrate with...