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

Christophe Strobbe strobbe at hdm-stuttgart.de
Mon Oct 15 08:32:57 EDT 2012



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.


>
> The special API is a great idea. I foresee it as especially interesting in
> avoiding the same term being defined several times with the very same
> meaning (e.g.: "foreground colour" && "foreground-colour" &&
> "foregroundColour") and that's something that the transformer could handle
> easily* --btw, the "color vs. colour" issue could also be handled with the
> help of a good AmE. BrE. translator...

On second thought, I wonder if the aliases can solve this problem.

Best regards,

Christophe

>
>
> Best regards,
> Andrés
>
> * as Colin said in Stuttgart "the developer last words"
> --
> Andrés Iglesias Pérez
> Investigador  I+D+i | R&D Researcher
> Departamento de I+D+i | R&D Department
> Dirección de Tecnologías Accesibles e I+D+i | Accessible Technology and
> R&D&i Management
> Technosite, Grupo Fundosa | Fundosa Group
> C/ Albasanz, 16, 3ºB. 28037. Madrid. Spain
> Tel:             +34 91.121.03.30
> Fax: +34 91.375.70.51
> aiglesias at technosite.es
>
> -----Mensaje original-----
> De: accessforall-bounces at fluidproject.org
> [mailto:accessforall-bounces at fluidproject.org] En nombre de Christophe
> Strobbe
> Enviado el: viernes, 12 de octubre de 2012 15:42
> Para: AccessForAll
> CC: GPII Architecture
> Asunto: [Accessforall] Format of Registry names (spaces, camelCase)
>
> Hi,
>
> While working on preference sets for the personas that we will use in the
> smart house simulation, the following question came up:
> * Many of the names in our Registry for Property and Condition Terms
> contain spaces, e.g. "adaptation type", "background colour" and "colour
> coding avoidance". These names are what we call the "Local Unique IDs".
> * The example preference sets I have seen so far typically use camel case
> for these names, e.g. screenEnhancement, foregroundColor, etc.
> * We wanted to use URIs as property names (see item 3 at
> <http://wiki.gpii.net/index.php/Discussion_on_Profile_Structure>.
> * In URIs, spaces are special characters that need to be percent-encoded;
> see RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax":
> <http://tools.ietf.org/html/rfc3986#section-2.1>. For example, a space
> would be encoded as %20.
>
> So the question is: Do we want to keep the spaces in the names and
> percent-encode them in URIs, or should we rename our Local Unique IDs in
> camel case to avoid percent-encoding of space characters? (Or is the
> Registry going to provide an API that does automatic conversion between
> camel case and the notation with spaces?)
>
> Best regards,
>
> Christophe
>
>
> --
> Christophe Strobbe
> Akademischer Mitarbeiter
> Adaptive User Interfaces Research Group
> Hochschule der Medien
> Nobelstraße 10
> 70569 Stuttgart
> Tel. +49 711 8923 2749
>
> _______________________________________________
> Accessforall mailing list
> Accessforall at fluidproject.org
> http://lists.idrc.ocad.ca/cgi-bin/mailman/listinfo/accessforall
>
>
>


-- 
Christophe Strobbe
Akademischer Mitarbeiter
Adaptive User Interfaces Research Group
Hochschule der Medien
Nobelstraße 10
70569 Stuttgart
Tel. +49 711 8923 2749



More information about the Accessforall mailing list