[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [buckminster-dev] How to improve mapping rules in the Aggregator
|
On 2009-12-08 11:44, Filip Hrbek wrote:
When the reference to the IU is established, it refers to a resolved IU
instance
and its proxy URI is undefined at that time.
The proxy URI is generated by the EMF resource implementation at the time
the model is being saved. It is unclear to me how we are going to hack
this.
Even if we do, is that a proper usage of EMF?
The advice to rewrite the URI resolution comes from Ed Merks. I'm not an expert, but he is.
Third, I would provide the GUI necessary to alter the range boundaries
(i.e. tweak the proxy). This is probably just a matter of adding a
custom derived property to the model (or perhaps more then one to
bring clarity).
This is also unclear to me - where do we add the properties? Are they
persistent/transient? How do we edit them?
They are transient. There are some examples in the book on how to do this.
Fourth, I would add the validation that verifies that selected
features don't overlap and doesn't create conflicts.
Sure, good thing. Although I think that feature overlap is not an error,
especially if the overlap comes from different contributions.
Right, overlaps are not errors. But the information is useful anyway.
- thomas
