search

QasimRiaz / akomantoso

Automatically exported from code.google.com/p/akomantoso
0 stars 1 forks source link

Uppercase / Lowercase / CamelCase in element names #9

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Understanding the rationale in elements name may arise when reading the 
documentation about 
Akoma Ntoso. Here I expose (maybe for the first time) my understanding about 
the 
use of cases in element names.

Although this situation is not as clear-cut as the plural/singular one, there 
is a basic approach 
designing element names: 

lowercase elements are concrete elements, that contain a specific instance of 
the concept 
represented by the name. 

Uppercase elements are abstract elements or generic elements, that contain 
either a 
representation of the concept itself (as opposed to a representation of an 
instance of the 
concept) or a generic element (i.e., an instance of a concept whose actual name 
does not exist in 
the schema and needs to be added in a generic way). 

Thus: <Block> is a generic term, FRBRWork is an abstraction, etc.

Original issue reported on code.google.com by fvit...@gmail.com on 27 Oct 2007 at 1:54

GoogleCodeExporter commented 9 years ago

Original comment by fvit...@gmail.com on 17 Nov 2007 at 6:58

GoogleCodeExporter commented 9 years ago

Original comment by fvit...@gmail.com on 18 Nov 2007 at 5:15

GoogleCodeExporter commented 9 years ago

Original comment by fvit...@gmail.com on 18 Nov 2007 at 5:16

GoogleCodeExporter commented 9 years ago

Original comment by fvit...@gmail.com on 18 Nov 2007 at 5:33

GoogleCodeExporter commented 9 years ago

Original comment by ashok.ha...@gmail.com on 4 Mar 2010 at 6:53