[higgins-dev] IdAS questions

["Sergey Lyakhov" <slyakhov@xxxxxxxxxxxxxx>]

Hello Jim,

I have some questions about IdAS interfaces:

1. Now only IContext interface extends IHasRelationships interface.
Formerly IDigitalSubject extended this (IHasRelationships) interface too,
but IHasRelationships was removed from IDigitalSubject and replaced with
higgins:SubjectRelationship attributre. I propose to remove
IHasRelationships interface from IContext and add ContextRelationship
attribute to higgins schema instead of it. In this case we can remove
IHasRelationships and IRelationship interfaces from IdAS.

2. ISimpleValue interface contains a mapping between Higgins OWL
datatypes/XML schema types/Java classes returned by ISimpleValue.getData()
and IdAS basic value implementations. We need to use this mapping to
determine which implementation of ISimpleValue (BasicValueString,
BasicValueNormalizedString etc) should we use for appropiate subproperty of
higgins:simpleValue (for example we need to use
org.eclipse.higgins.idas.impl.BasicValueInteger class in case of
higgins:integerSimpleValue property). We need the same mechanism for
properties of ComplexValue, or, more formally, properties like pwa:state
should be subproperties of higgins:simpleValue (higgins:stringSimpleValue,
higgins:integerSimpleValue etc).

3. I propose to add some methods (like as begin(), commit() and rollback()) 
to IContext  for transaction support.

4. IContextFactory interface extends IHasMetadata interface. What is a
purpose of this interface and how should we implement it?

Thanks,
Sergey Lyakhov

----- Original Message ----- 
From: "Paul Trevithick" <paul@xxxxxxxxxxxxx>
To: "'Sergey Lyakhov'" <slyakhov@xxxxxxxxxxxxxx>
Cc: "'Vadim Synakh'" <synakh@xxxxxxxxxxxxxx>; "'Valery Kokhan'"
<vkokhan@xxxxxxxxxxxxxx>
Sent: Wednesday, November 15, 2006 5:42 PM
Subject: RE: IdAS questions


> > Subject: IdAS questions
> >
> >
> > > Paul,
> > >
> > > There are some questions about IdAS:
> > >
> > > 1. In which a way should we use higgins:ContextObject class? Should
> > > ontology document of Context have only one Individual of
> > > higgins:ContextObject,
>
> Yes.
>
> that will contain all references/metadata of this
> > > Context? (By the way we can use owl:Ontology class instead of
> > > higgins:ContextObject).
>
> The ContextObject instance is necessary because  (a) we need to have an
> object to which to attach ContextRelationships (the LDAP folks will create
> a
> tree of Contexts (by connecting the singleton ContextObject instances in
> each Context into a tree (b) We need (e.g. for SecondLife) to have a place
> to attach a couple of metadata properties (e.g. lastConnectionAttempt,
> lastConnection) that are about the entire Context
>
> > > 2. Interface IContext extends interface IHasMetadata. However
> > > properties
> > > higgins:complexMetadata and higgins:simpleMetadata do not have
> > > higgins:ContextObject as domain class.
>
> This is a bug. Sorry about that. I'll fix this.
>
> > > 3. Now SubjectRelationship is a complex attribute. Is there any sense
> > > to
> > > use higgins:ContextRelationship as attribute (not Relationship) too and
> > > remove IRelationship interface from IdAS (in this case IContext should
> > > extend IHasAttributes instead of IHasRelationships)?
>
> I don't know the answer. Please work with Valery to rewrite this question
> to
> make the English even more clear and then email to JimS and cc higgins-dev
>
> > > 4. ISimpleValue interface contains a mapping between Higgins OWL
> > > datatypes/XML schema types/Java classes returned by
> > ISimpleValue.getData()
> > > and IdAS basic value implementations. We need to use this mapping to
> > > determine which implementation of ISimpleValue (BasicValueString,
> > > BasicValueNormalizedString etc) should we use for appropiate
> > > subproperty
> > > of higgins:simpleValue (for example we need to use
> > > org.eclipse.higgins.idas.impl.BasicValueInteger class in case of
> > > higgins:integerSimpleValue property). We need the same mechanism for
> > > properties of ComplexValue, or, more formally, properties like
> > > pwa:state
> > > should be subproperties of higgins:simpleValue
> > (higgins:stringSimpleValue,
> > > higgins:integerSimpleValue etc).
>
> Interesting question. I think you should email to JimS and cc higgins-dev
>
> > > 5. Higgins.owl schema doesn't contain all types of simple attribute (as
> > an
> > > example, there is no higgins:booleanSimpleValue property for
> > > org.eclipse.higgins.idas.impl.BasicValueBoolean).
>
> I have been meaning to add these. If you just this one thing for me
> (today)
> and email it to me, I'll add some other fixes and republish it.
>
> > > 6. I propose to add some methods to IContext to support transactions
> > > (like as begin(), commit() and rollback()).
>
> Please propose this to JimS and cc the higgins-dev list.
>
> > > 7.IContextFactory should have some information about a context (name of
> > > file of ontology document, URL of context's schema, database parameters
> > > etc). Where ContextFactory should it get (store) from? Also, there is
> > > IContext.setSchema(String schema) method, however we need a schema
> > > (more
> > > likely its URL) only when we create new ontology. How should we use
> > > this
> > > method? Perhaps we need always to pass both URL of ontology document
> > > and
> > > URI of schema to Context's constructor, but use this schema URL (add as
> > > imported ontology) only if create new ontology document.
>
> Please propose some ideas on this to JimS and cc higgin-dev. We plan to
> discuss this at the F2F tomorrow and Fri.
>
> > > 8. IContextFactory interface extends IHasMetadata interface. What is a
> > > purpose of this interface and how should we implement it?
>
> I have no idea what JimS was thinking, please ask him and cc the list.