any23-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (JIRA)" <>
Subject [jira] [Commented] (ANY23-144) Implement comprehensive naming of o.a.a.api.vocab classes
Date Wed, 06 Feb 2013 19:07:13 GMT


Lewis John McGibbney commented on ANY23-144:

{bq}My preference is for all uppercase vocabulary class names if the commonly used prefix
is an acronym, and camel-case where it is not, however, in some cases that distinction is
not necessarily clear.{bq}
OK so in an attempt to move towards a more appropriate (partial) solution... the DOAP vocab
would remain named as DOAP and LIKF-Core would be  changed to CamelCase e.g. LKIFCoreAction,
etc... Can you confirm? It appears that this was not so much of a pressing issue before Simo
pointed it out and you commented. This being said I appreciate that and I think it is important
to get it right :)

{bq}To clear up the naming I would prefer if we avoided the getInstance() pattern.... like
access to the properties without storing them in a local private field to get around the getInstance()
Excuse me if I am wrong, but I see this as a fundamental different issue from renaming of
classes. Can we address this more directly in a related but separate issue?
> Implement comprehensive naming of o.a.a.api.vocab classes 
> ----------------------------------------------------------
>                 Key: ANY23-144
>                 URL:
>             Project: Apache Any23
>          Issue Type: Improvement
>          Components: api
>    Affects Versions: 0.7.0
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 0.8.0
>         Attachments: ANY23-144.patch
> As Simo pointed out we currently have a rather naff naming convention for all classes
contained within the above package.
> This issue should address that and rename all classes.
> Thread for reference 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message