[Accessforall] [Architecture] Format of Registry names (spaces, camelCase)

Gregg Vanderheiden gv at trace.wisc.edu
Mon Oct 15 13:30:04 EDT 2012

HI Colin

I think that is a good idea.  We might want to have consistency for example for terms we make core. 

My son was just lamenting trying to use different code modules when everyone used different capitalization conventions. 

Gregg Vanderheiden Ph.D.
Director Trace R&D Center
Professor Industrial & Systems Engineering
and Biomedical Engineering University of Wisconsin-Madison
Technical Director - Cloud4all Project - http://Cloud4all.info
Co-Director, Raising the Floor - International - http://Raisingthefloor.org
and the Global Public Inclusive Infrastructure Project -  http://GPII.net

On Oct 15, 2012, at 8:01 AM, Colin Clark <colinbdclark at gmail.com> wrote:

> Hi all,
> On 2012-10-15, at 8:32 AM, Christophe Strobbe wrote:
>> Am Mo, 15.10.2012, 10:58 schrieb Andres Iglesias:
>>> Hi Christophe,
>>> Since we're going to accept new terms coming from vendors, independent
>>> organizations etc. I think we won't be able to impose any naming
>>> convention on this, as everyone expresses their terms in her own naming
>>> policies.
>> I agree.
>> But part of my question was also about the inconsistency between the use
>> of spaces in the temporary registry and the use of camel case in the
>> preference sets.
> I think we do want to impose some minimal naming conventions to make it easier for programmers in a variety of languages to use these local names without extra effort. It doesn't seem inappropriately restrictive to simply ask contributors to the registry to avoid certain characters (such as spaces) when specifying their local names. Validation in the Registry's UI can prompt the user, and if we find a desire for more consistency beyond that, we can come up with a style guide for contributors.
> Colin
> ---
> Colin Clark
> Technical Lead, Fluid Project
> http://fluidproject.org
> _______________________________________________
> Architecture mailing list
> Architecture at lists.gpii.net
> http://lists.gpii.net/cgi-bin/mailman/listinfo/architecture

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/accessforall/attachments/20121015/7002ed95/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 7318 bytes
Desc: not available
URL: <http://lists.idrc.ocad.ca/pipermail/accessforall/attachments/20121015/7002ed95/attachment.bin>

More information about the Accessforall mailing list