Skip to main content
Jump to: navigation, search

Difference between revisions of "Models as Yet More Entities and Attributes"

Line 1: Line 1:
 
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
 
{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
 
[[Image:Higgins_logo_76Wx100H.jpg|right]]
 
[[Image:Higgins_logo_76Wx100H.jpg|right]]
=Problem=
+
==Problem==
 
Today, IdAS defines a set of special interfaces for accessing a context's model elements.  There are a number of problems with these interfaces:
 
Today, IdAS defines a set of special interfaces for accessing a context's model elements.  There are a number of problems with these interfaces:
 
# They are 'fixed' in nature.  The only way to represent extra information about the model of context elements is to revise these interfaces.  For example, say there's a need to associate an image with the attribute called <nowiki>http://example.com/some/name/space#telephoneNumber</nowiki> (this image might be used by a management UI).  To make that association we need a new method like IAttributeModel.getManagementImage().   
 
# They are 'fixed' in nature.  The only way to represent extra information about the model of context elements is to revise these interfaces.  For example, say there's a need to associate an image with the attribute called <nowiki>http://example.com/some/name/space#telephoneNumber</nowiki> (this image might be used by a management UI).  To make that association we need a new method like IAttributeModel.getManagementImage().   
Line 8: Line 8:
 
# We cannot look up a model with partial information.  For example, say I know there's an attribute with the word "telephoneNumber" in its ID, but I don't know the entire ID.  It would be nice to be able to have a way to find what I need without enumerating through the entire set of attribute models.
 
# We cannot look up a model with partial information.  For example, say I know there's an attribute with the word "telephoneNumber" in its ID, but I don't know the entire ID.  It would be nice to be able to have a way to find what I need without enumerating through the entire set of attribute models.
  
=Proposal=
+
==Proposal==
 
It may be better to move away from the existing special interfaces for the purpose of defining the model of elements, but instead simply re-use the existing interfaces that are used to access normal information within a Context (entities and their attributes).
 
It may be better to move away from the existing special interfaces for the purpose of defining the model of elements, but instead simply re-use the existing interfaces that are used to access normal information within a Context (entities and their attributes).
  
 
Following is a proposal which shows how these model entities might look.  To illustrate the proposal, we start by showing how an instance of a person looks (nothing new) and then examining the model entities that govern instances of entities and attributes:
 
Following is a proposal which shows how these model entities might look.  To illustrate the proposal, we start by showing how an instance of a person looks (nothing new) and then examining the model entities that govern instances of entities and attributes:
  
==A person==
+
===A person===
 
Example of an instance of a person entity.
 
Example of an instance of a person entity.
 
* Java type: some impl of IEntity. The context provider implements this class
 
* Java type: some impl of IEntity. The context provider implements this class
Line 22: Line 22:
 
* getTypeEntity() returns: some impl of IEntity, assume it returns a PersonModel.class
 
* getTypeEntity() returns: some impl of IEntity, assume it returns a PersonModel.class
  
==A person's model==
+
===A person's model===
 
Now, say we look at the “person model” entity we saw above (we got this either by calling IEntity.getTypeEntity(), or IEntity.getType() followed by IContext.getEntity(EntityID)), we see (NOTE: this entity is a model element):
 
Now, say we look at the “person model” entity we saw above (we got this either by calling IEntity.getTypeEntity(), or IEntity.getType() followed by IContext.getEntity(EntityID)), we see (NOTE: this entity is a model element):
 
* Java type: some impl of IEntity – This is implemented by the context provider.  We can assume it's a PersonModel.class.
 
* Java type: some impl of IEntity – This is implemented by the context provider.  We can assume it's a PersonModel.class.
Line 36: Line 36:
 
* getTypeEntity() returns: an implementation of IEntity which represents <nowiki>http://www.w3.org/2002/07/owl#Class</nowiki>.  A default object would be implemented by Higgins, but could be overridden by context providers which wish to add additional capabilities.
 
* getTypeEntity() returns: an implementation of IEntity which represents <nowiki>http://www.w3.org/2002/07/owl#Class</nowiki>.  A default object would be implemented by Higgins, but could be overridden by context providers which wish to add additional capabilities.
  
==The "top" entity model==
+
===The "top" entity model===
 
Ok, now let's look at the instance of the entity called <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#Entity</nowiki>.  This is simply the top-level model definition for all entity model hierarchies.  Thus it contains model definitions for things common to all entities:
 
Ok, now let's look at the instance of the entity called <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#Entity</nowiki>.  This is simply the top-level model definition for all entity model hierarchies.  Thus it contains model definitions for things common to all entities:
 
* Java type: an impl of IEntity (maybe we'll call it Entity.class).  This is implemented by Higgins and is always the same
 
* Java type: an impl of IEntity (maybe we'll call it Entity.class).  This is implemented by Higgins and is always the same
Line 47: Line 47:
 
* getTypeEntity() returns: an implementation of IEntity which represents <nowiki>http://www.w3.org/2002/07/owl#Class</nowiki>.  A default object would be implemented by Higgins, but could be overridden by context providers which wish to add additional capabilities.
 
* getTypeEntity() returns: an implementation of IEntity which represents <nowiki>http://www.w3.org/2002/07/owl#Class</nowiki>.  A default object would be implemented by Higgins, but could be overridden by context providers which wish to add additional capabilities.
  
==The model for entity models==
+
===The model for entity models===
 
What defines an entity model entity?  This does:
 
What defines an entity model entity?  This does:
 
* Java type: an impl of IEntity.  Higgins will provide a default class called EntityModel.class, but a context provider is free to return its own (which may or may not be a subclass of the Higgins EntityModel.class), as long as it contains the <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes</nowiki> and its values mentioned below.  A context provider is free to override and add more values here.
 
* Java type: an impl of IEntity.  Higgins will provide a default class called EntityModel.class, but a context provider is free to return its own (which may or may not be a subclass of the Higgins EntityModel.class), as long as it contains the <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes</nowiki> and its values mentioned below.  A context provider is free to override and add more values here.
Line 58: Line 58:
 
* getTypeEntity() returns this object, or maybe it should be null
 
* getTypeEntity() returns this object, or maybe it should be null
  
==An attribute model==
+
===An attribute model===
 
Now for fun, let's look at an attribute's model, and follow that.  We'll take the example of <nowiki>http://example.com/prop/fullname</nowiki>:
 
Now for fun, let's look at an attribute's model, and follow that.  We'll take the example of <nowiki>http://example.com/prop/fullname</nowiki>:
 
* Java type: an impl of IEntity. This is created by the context provider.
 
* Java type: an impl of IEntity. This is created by the context provider.
Line 69: Line 69:
 
* getTypeEntity() returns: an implementation of IEntity representing <nowiki>http://www.w3.org/2000/01/rdf-schema#Property</nowiki>.  This object would be implemented by Higgins and thus would be the same for all context providers.
 
* getTypeEntity() returns: an implementation of IEntity representing <nowiki>http://www.w3.org/2000/01/rdf-schema#Property</nowiki>.  This object would be implemented by Higgins and thus would be the same for all context providers.
  
==The model for attribute models==
+
===The model for attribute models===
 
And here's that the entity identified by <nowiki>http://www.w3.org/2000/01/rdf-schema#Property</nowiki> looks like:
 
And here's that the entity identified by <nowiki>http://www.w3.org/2000/01/rdf-schema#Property</nowiki> looks like:
 
* Java type: an impl of IEntity.  Higgins will provide a default class called AttributeModel.class, but a context provider is free to return its own (which may or may not be a subclass of the Higgins AttributeModel.class), as long as it contains the <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes</nowiki> and its values mentioned below.  A context provider is free to add more values to the <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes</nowiki> attribute.
 
* Java type: an impl of IEntity.  Higgins will provide a default class called AttributeModel.class, but a context provider is free to return its own (which may or may not be a subclass of the Higgins AttributeModel.class), as long as it contains the <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes</nowiki> and its values mentioned below.  A context provider is free to add more values to the <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes</nowiki> attribute.
Line 83: Line 83:
 
Then of course we have value models.  Again from the bottom-up, here's an entity that describes a value type called <TODO: finish this>
 
Then of course we have value models.  Again from the bottom-up, here's an entity that describes a value type called <TODO: finish this>
  
= TODO =
+
== TODO ==
 +
* The above needs to be revised based on the decision to allow 0..N EntityIds per Entity
 
* We need to be able to specify min/max cardinality on each attributeType associated with a specific entity model so we can preserve the ability to say "person entities must have at least one surname attribute value, and may have a telephone number" without causing all instances of surname to be min=1
 
* We need to be able to specify min/max cardinality on each attributeType associated with a specific entity model so we can preserve the ability to say "person entities must have at least one surname attribute value, and may have a telephone number" without causing all instances of surname to be min=1
 
** The model for <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#attributeTypes</nowiki> values could be a complex value which lists the attr type ID, as well as min//max cardinality.
 
** The model for <nowiki>http://www.eclipse.org/higgins/ontologies/2008/6/higgins#attributeTypes</nowiki> values could be a complex value which lists the attr type ID, as well as min//max cardinality.
  
 
[[Category:Higgins IdAS]]
 
[[Category:Higgins IdAS]]

Revision as of 20:27, 13 April 2009

{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}

Higgins logo 76Wx100H.jpg

Problem

Today, IdAS defines a set of special interfaces for accessing a context's model elements. There are a number of problems with these interfaces:

  1. They are 'fixed' in nature. The only way to represent extra information about the model of context elements is to revise these interfaces. For example, say there's a need to associate an image with the attribute called http://example.com/some/name/space#telephoneNumber (this image might be used by a management UI). To make that association we need a new method like IAttributeModel.getManagementImage().
    1. Even if we felt like it's ok to revise the current I*Model interfaces, we do not know what kinds of information will need to be associated with the models of elements in a context. It may be the case that some people will have needs that we think are unworthy of revising the interfaces for. For example, say someone wants to associate an astrological symbol to each different attribute model. Does that mean we should add a new IAttributeModel.getAstrologicalSymbol()?
  2. There is no way to update a context's model. We have a need to be able to add models for new entity types, attribute types and so-on. We also need to be able to change existing models (such as changing the cardinality of an attribute). Also, we may need to remove models.
  3. We cannot look up a model with partial information. For example, say I know there's an attribute with the word "telephoneNumber" in its ID, but I don't know the entire ID. It would be nice to be able to have a way to find what I need without enumerating through the entire set of attribute models.

Proposal

It may be better to move away from the existing special interfaces for the purpose of defining the model of elements, but instead simply re-use the existing interfaces that are used to access normal information within a Context (entities and their attributes).

Following is a proposal which shows how these model entities might look. To illustrate the proposal, we start by showing how an instance of a person looks (nothing new) and then examining the model entities that govern instances of entities and attributes:

A person

Example of an instance of a person entity.

  • Java type: some impl of IEntity. The context provider implements this class
  • getEntityID() returns: the contextually unique ID for this person
  • getAttributes() returns: typical attributes about this person (things like a full name and email address)
  • getType() returns: an identifier for this person's model entity. assume it's called http://example.com/class#Person
    • Note that getType is only a convenience for getTypeEntity().getEntityID()
  • getTypeEntity() returns: some impl of IEntity, assume it returns a PersonModel.class

A person's model

Now, say we look at the “person model” entity we saw above (we got this either by calling IEntity.getTypeEntity(), or IEntity.getType() followed by IContext.getEntity(EntityID)), we see (NOTE: this entity is a model element):

  • Java type: some impl of IEntity – This is implemented by the context provider. We can assume it's a PersonModel.class.
  • getEntityID() returns: the contextually unique ID for this entity. This is the same value we got when calling IEntity.getType() on the person instance above, so in this case it would be http://example.com/class#Person.
  • getAttributes() returns: the following and other attributes:
    • http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes: This attribute has complex values, each of which represent a valid attribute for this type of entity. Each value has the following literal elements:
      • http://www.w3.org/2000/01/rdf-schema#Property = <attribute type uri like http://example.com/prop#fullname>
      • http://www.w3.org/2002/07/owl#minCardinality = <minimum cardinality for values of this attribute as it applies to the person model.> note that this cannot be less restrictive than the http://www.w3.org/2002/07/owl#minCardinality attribute specified on the property definition representing this attribute. In other words, if this attribute is in fact http://example.com/prop#fullname, there would be an attribute model for http://example.com/prop#fullname and that attribute model might specify a min cardinality of one. In that case, min cardinality here cannot be set to zero.
      • http://www.w3.org/2002/07/owl#maxCardinality = <maximum cardinality for values of this attribute as it applies to the person model.> note that the same rule applies here as applied to min cardinality. this value cannot be less restrictive than that on the attribute's model.
      • Note that the full list of valid attributes for this type of entity must be discovered by looking at this list as well as the list of all this entity model's supertypes. We can talk about possible shortcuts to get them all at once.
    • http://www.w3.org/2000/01/rdf-schema#subClassOf: This has a single, literal value which names the supertype of person. If person is derived from something like http://example.com/class#Mammal it would name that. If person is at the top of it's entity type hierarchy in this context, this attribute would name the well-known entity model entity that defines IEntitys in general (that would be called http://www.eclipse.org/higgins/ontologies/2008/6/higgins#Entity)
  • getType() returns: the well-known identifier http://www.w3.org/2002/07/owl#Class
  • getTypeEntity() returns: an implementation of IEntity which represents http://www.w3.org/2002/07/owl#Class. A default object would be implemented by Higgins, but could be overridden by context providers which wish to add additional capabilities.

The "top" entity model

Ok, now let's look at the instance of the entity called http://www.eclipse.org/higgins/ontologies/2008/6/higgins#Entity. This is simply the top-level model definition for all entity model hierarchies. Thus it contains model definitions for things common to all entities:

  • Java type: an impl of IEntity (maybe we'll call it Entity.class). This is implemented by Higgins and is always the same
  • getEntityID() returns: the unique ID for this entity. This is http://www.eclipse.org/higgins/ontologies/2008/6/higgins#Entity
  • getAttributes() returns: the following attributes:
    • http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes: In the base higgins definition of the top entity model, only one value exists at this point, and that is:
      • http://www.w3.org/2000/01/rdf-schema#Property = http://www.eclipse.org/higgins/ontologies/2006/higgins#EntityID
      • http://www.w3.org/2002/07/owl#minCardinality = 1
      • http://www.w3.org/2002/07/owl#maxCardinality = 1
  • getTypeEntity() returns: an implementation of IEntity which represents http://www.w3.org/2002/07/owl#Class. A default object would be implemented by Higgins, but could be overridden by context providers which wish to add additional capabilities.

The model for entity models

What defines an entity model entity? This does:

  • Java type: an impl of IEntity. Higgins will provide a default class called EntityModel.class, but a context provider is free to return its own (which may or may not be a subclass of the Higgins EntityModel.class), as long as it contains the http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes and its values mentioned below. A context provider is free to override and add more values here.
  • getEntityID() returns: the unique ID for this entity. This is http://www.w3.org/2002/07/owl#Class
  • getAttributes() returns: the following attributes:
    • http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes: Names the attributes (along with their min/max cardinality) valid for entity models. These values exists here (note that a context provider may add to this set of values):
      • {http://www.w3.org/2000/01/rdf-schema#Property = http://www.eclipse.org/higgins/ontologies/2006/higgins#validAttributes, minCard = 0, maxCard = 0}
      • {http://www.w3.org/2000/01/rdf-schema#Property = http://www.w3.org/2000/01/rdf-schema#subClassOf, minCard = 0, maxCard = 1}
  • getType() returns: the well-known identifier http://www.w3.org/2002/07/owl#Class, or maybe null
  • getTypeEntity() returns this object, or maybe it should be null

An attribute model

Now for fun, let's look at an attribute's model, and follow that. We'll take the example of http://example.com/prop/fullname:

  • Java type: an impl of IEntity. This is created by the context provider.
  • getEntityID() returns: the unique ID for this entity. In this case it's http://example.com/prop/fullname
  • getAttributes() returns: the following attributes:
    • http://www.w3.org/2000/01/rdf-schema#range: Each value would be the identifier of a model entity which represents a permitted data type for the value(s) of attribute instances that this attribute model defines. An example might be http://www.w3.org/2001/XMLSchema#string, but could also point at any other value model (for simple types) or entity model (for complex types).
    • http://www.w3.org/2000/01/rdf-schema#subPropertyOf: This attribute would point at another attribute model entity. If fullname is derived from something like http://example.com/prop#name it would point at that. If fullanme is at the top of it's attribute type hierarchy in this context, this attribute would be absent.
    • http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes: This is the list of (metadata) attributes valid for this attribute. If no attributes are valid, this attr is not populated.
  • getType() returns: the well-known identifier http://www.w3.org/2000/01/rdf-schema#Property
  • getTypeEntity() returns: an implementation of IEntity representing http://www.w3.org/2000/01/rdf-schema#Property. This object would be implemented by Higgins and thus would be the same for all context providers.

The model for attribute models

And here's that the entity identified by http://www.w3.org/2000/01/rdf-schema#Property looks like:

  • Java type: an impl of IEntity. Higgins will provide a default class called AttributeModel.class, but a context provider is free to return its own (which may or may not be a subclass of the Higgins AttributeModel.class), as long as it contains the http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes and its values mentioned below. A context provider is free to add more values to the http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes attribute.
  • getEntityID() returns: the unique ID for this entity. This is http://www.w3.org/2000/01/rdf-schema#Property
  • getAttributes() returns: the following attributes:
    • http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes: These values represent the types of attributes allowed on an attribute model entity (note that a context provider may add to this set of values):
      • http://www.w3.org/2000/01/rdf-schema#range
      • http://www.w3.org/2000/01/rdf-schema#subPropertyOf
      • http://www.eclipse.org/higgins/ontologies/2008/6/higgins#validAttributes
  • getType() returns: the well-known identifier http://www.w3.org/2002/07/owl#Class
  • getTypeEntity() returns: an implementation of IEntity representing http://www.w3.org/2002/07/owl#Class. This object would be implemented by Higgins and thus would be the same for all context providers.

Then of course we have value models. Again from the bottom-up, here's an entity that describes a value type called <TODO: finish this>

TODO

  • The above needs to be revised based on the decision to allow 0..N EntityIds per Entity
  • We need to be able to specify min/max cardinality on each attributeType associated with a specific entity model so we can preserve the ability to say "person entities must have at least one surname attribute value, and may have a telephone number" without causing all instances of surname to be min=1
    • The model for http://www.eclipse.org/higgins/ontologies/2008/6/higgins#attributeTypes values could be a complex value which lists the attr type ID, as well as min//max cardinality.

Back to the top