[dais-wg] OO Realization

[Leon Guzenda]

On Page 9, Line 263: Most object databases will require a database, 
federated database or server name, plus an Object Identifier (OID). The 
wrapper could also identify the ODBMS too, in case a request ends up in 
the wrong place.

Best regards,
Leon

Leon Guzenda
CTO, Objectivity, Inc.

Norman Paton wrote:

>
> Here are a few comments on the initial draft:
>
> Page 1: The editor list is too long!  In general, one is named on the 
> front page of DAIS specs as a result of sustained contribution to a 
> document or the discussions relating to its contents.  As this is 
> currently your document, it should just name you on the cover for now.
>
> Page 6, Line 182: JD-OQL as one of the query languages. I am conscious 
> that JDO-QL queries are normally represented as Java objects, so it 
> needs to be stated how these are represented as parameters to a 
> message. If this was an XML structure, then it may be quite 
> straightforward to support this over existing platforms that don't 
> support JDO-QL directly.
>
> Page 9, Line 263: Representation of references to objects.  One might 
> expect this to be some form of wrapper type that states something 
> about the source of the reference.  The spec would then need to state 
> some properties of instances of the wrapper type.  One might expect 
> that the main or perhaps only guarantee is that the reference can be 
> passed as a parameter to some operations on the service whence it 
> came, where if the object still exists and appropriate permissions 
> exist, further behaviour can take place.
>
> Page 9: Line 267: Result format: This seems never to contain the 
> values of properties of the objects, in the way that WebRowSet 
> contains the values of the tuples.  There needs to be some 
> representation for the values of the objects too - are there existing 
> candidates?  I note that a message could contain a parameter that 
> states how deep a copy of the properties of an object should be returned.
>
> Regards, Norman
>
>
>