Note that for class and property names, we tend to stick to typical programming convantions, which is

 * class - first letter capital
 * property / method name - first letter lower-case

One reason to do this is to be able to distinguish a class name on its own, e.g. in an ADL archetype, and not mix it up with a property name. The ADL workbench does this, and  I would argue we want to keep these rules.

Nothing is ever completely simple...

- thomas


On 30/11/2017 15:01, Pieter Bos wrote:
I agree about the case insensitivity. Archie still does this case sensitive, so 
I just created https://github.com/openEHR/archie/issues/8 (

Pieter

On 30/11/2017, 15:23, "openEHR-technical on behalf of Thomas Beale" 
<openehr-technical-boun...@lists.openehr.org on behalf of thomas.be...@openehr.org> wrote:

I think the string matching should be case-insensitive, and the current
     regexes allow for any case. Various tools implementers would need to
     check to see if their tools match 'ehr_extract' to 'EHR_EXTRACT' etc.
- thomas On 30/11/2017 13:55, Bert Verhees wrote:
     > So, there are also considerations I did not see.
     >
     > I can live a few days more without having a definite policy ;-)
     > But the classes are there and people will want to use them.
     >
     > I think Thomas proposal is in line with the other rmNames, like EHR
     > and DEMOGRAPHIC (which are capitalized), and therefor indeed
     > EHR_EXTRACT seems to me the best solution. Sorry for agreeing with
     > previous suggestions.
     >
     > Bert
_______________________________________________
     openEHR-technical mailing list
     openEHR-technical@lists.openehr.org
     
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org


--
Thomas Beale
Principal, Ars Semantica <http://www.arssemantica.com>
Consultant, ABD Team, Intermountain Healthcare <https://intermountainhealthcare.org/> Management Board, Specifications Program Lead, openEHR Foundation <http://www.openehr.org> Chartered IT Professional Fellow, BCS, British Computer Society <http://www.bcs.org/category/6044> Health IT blog <http://wolandscat.net/> | Culture blog <http://wolandsothercat.net/>
_______________________________________________
openEHR-technical mailing list
openEHR-technical@lists.openehr.org
http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org

Reply via email to