Hi devs,
We need to decide if we want to keep the current:
ResourceName, DocumentName, SpaceName, WikiName, AttachmentName
or instead use a variation.
There are 2 things to decide:
- The prefix for the base object (Resource, Item, Model, etc)
- The suffix (Name, Path, Reference, etc)
Proposal
On Dec 17, 2009, at 3:08 PM, Fabio Mancinelli wrote:
On Dec 17, 2009, at 1:48 PM, Vincent Massol wrote:
Proposal
===
I'd like to propose ModelReference for the base object and then
DocumentReference, SpaceReference, WikiReference,
AttachmentReference.
Note: This is different from
On Dec 17, 2009, at 2:47 PM, Sergiu Dumitriu wrote:
On 12/17/2009 01:54 PM, Vincent Massol wrote:
On Dec 17, 2009, at 1:48 PM, Vincent Massol wrote:
Hi devs,
We need to decide if we want to keep the current:
ResourceName, DocumentName, SpaceName, WikiName, AttachmentName
or instead use
On Dec 17, 2009, at 3:36 PM, Vincent Massol wrote:
On Dec 17, 2009, at 3:08 PM, Fabio Mancinelli wrote:
On Dec 17, 2009, at 1:48 PM, Vincent Massol wrote:
Proposal
===
I'd like to propose ModelReference for the base object and then
DocumentReference, SpaceReference,
On Thu, Dec 17, 2009 at 15:38, Vincent Massol vinc...@massol.net wrote:
On Dec 17, 2009, at 2:47 PM, Sergiu Dumitriu wrote:
On 12/17/2009 01:54 PM, Vincent Massol wrote:
On Dec 17, 2009, at 1:48 PM, Vincent Massol wrote:
Hi devs,
We need to decide if we want to keep the current:
Hi,
We'd have:
Entity
EntityReference
EntityType
EntityReferenceFactory, EntityReferenceSerializer
I think I prefer it slighty more than Resource. What do others think?
For me Entity sounds little bit too generic. I'd prefer Resource
instead. A Resource implies I can use it for something
On Dec 17, 2009, at 5:52 PM, Asiri Rathnayake wrote:
Hi,
We'd have:
Entity
EntityReference
EntityType
EntityReferenceFactory, EntityReferenceSerializer
I think I prefer it slighty more than Resource. What do others think?
For me Entity sounds little bit too generic. I'd prefer
Hi Vincent,
Well Entity is pretty common in modeling (see http://bit.ly/5r2Liw)
Also it's used in Entity Bean (Java EE) and is defined as:
An entity bean represents a business object in a persistent storage
mechanism. Some examples of business objects are customers, orders,
and products
Hi,
Big +1 for getUUID() and storing UUID as byte[] and returning java.util.UUID
Storage as byte[] will improve db load times.
Whatever you like for a name is fine for me but I would caution against over
generic words such as Model, Context, Factory, and Manager because
when I first began
If you look in semantic web definitions, the difference between an entity
and a resource is really hard to tell:)
Entity seems to be the most generic word to describe something that exists
or has existed.
On wikipedia, i found this definition:
A *resource* is any physical or virtual entity of
Sergiu Dumitriu wrote:
On 12/17/2009 09:31 PM, Caleb James DeLisle wrote:
Hi,
Big +1 for getUUID() and storing UUID as byte[] and returning java.util.UUID
Storage as byte[] will improve db load times.
Whatever you like for a name is fine for me but I would caution against over
generic
On Thu, Dec 17, 2009 at 11:07 PM, Sergiu Dumitriu ser...@xwiki.com wrote:
On 12/17/2009 10:30 PM, Pascal Voitot wrote:
If you look in semantic web definitions, the difference between an entity
and a resource is really hard to tell:)
Entity seems to be the most generic word to describe
12 matches
Mail list logo
