Re: [henshin-dev] Proposal to remove direct creation of edges

[Stefan Jurack <henshin.stj@xxxxxxxxx>]

The actual proposal is:
A nested rule might only have those parts in its Lhs/Rhs, which matter
for its application (analogously to ACs), i.e., the whole kernel is not
forced to be embedded.  Of course, the matching of all kernel rule
elements needs to be considered in terms of injectivity.

Question: Are there any implications we have missed which absolutely
require the whole kernel to be copied? Is this to far from the theory
(although the semantics remains the same)? Are there any other objections?

Regards,
Stefan

Am 12.12.2011 12:15, schrieb Gregor Bonifer:
>
> I discussed the issue with Stefan and we came up with the following
> solution. The necessity to force connected edges arose from the
> assumtion that multiRules have to include the complete kernel. The
> design rationale for AmalgamationUnits was based on the easy
> implementation of the application logic by means of RuleApplications.
> This can not be transfered to nested amalgamation, which requires a
> more laborious implementation. Therefore the discussion of editor
> features regarding the automatic synchronization of multiRules is
> moot. The editor continues to allow creation of unconnected and
> untyped Edges.
> Since there has been no feedback whether or not somebody is
> implementing the interpretation of nested amalgamation, I will start
> this now.

Attachment: signature.asc
Description: OpenPGP digital signature