17 Dec
2009
17 Dec
'09
3:36 p.m.
On Dec 17, 2009, at 3:08 PM, Fabio Mancinelli wrote:
On Dec 17, 2009, at 1:48 PM, Vincent Massol wrote:
The way I view it is that an object (or Entity or Resource) will have
2 methods:
- getReference() (corresponds to Node.getPath() in JCR I believe)
- getUUID()
In other words, it's possible to have several References pointing to
the same object (or Entity or Resource). This is very useful for
implementing renames for example.
In addition, FTM I'm not sure if a Reference should include the version
I need for think a bit more about this since I'm not 100% sure. If you
have ideas let me know.
Thanks
-Vincent
Proposal
=======
I'd like to propose ModelReference for the base object and then
DocumentReference, SpaceReference, WikiReference,
AttachmentReference.
Note: This is different from Identity which is unique (a UUID).
References do not point to unique objects.
I am not sure of having understood the note. In particular what you
mean when you say "references do not point to unique objects" Reference makes sense to me since it means what
it means... :)
For example the API: Document getDocument(DocumentReference) is
pretty
clear IMO.
I would say ResourceReference for the base object
and DocumentReference, SpaceReference, WikiReference,
AttachmentReference for the specific resource type references.
-Fabio