[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [higgins-dev] idas model as entities
|
I just re-read this and noticed I missed something:
>>> Paul Trevithick <paul@xxxxxxxxxxxxxxxxx> 09/02/08 8:51 PM >>>
<snip>
>http://wiki.eclipse.org/Higgins/ModelAPIs#An_attribute_model:
>* I see that you've chosen not to return rdf:domain as an attribute. Is this because you're trying to avoid allowing your attribute models to be used on more than one of your entity models?
In IdAS, a consumer finds the attributes of an entity by calling IEntity.getAttributes(). So it seems natural in the class definition for an entity type to call out which attributes the consumer might expect to find or might be able to add to entities of that type. So, the relationship between an entity's class definition and the attributes which are valid for it are on the class definition (in the validAttributes attribute) rather than the relationship being at the attribute type definition, pointing back at all the entity class definitions that allow that attribute.
Multiple entity classes may name the same attribute type in their validAttributes attr, so I'm not preventing that (nor do I want to).
Is there a need to allow each attribute type definition to list all the entity classes which it's valid for? This would just be redundant data, correct?
