Home » railML newsgroups » railML.infrastructure » "default" attribute raises implementation problems
"default" attribute raises implementation problems [message #268] Tue, 15 November 2011 10:05
Susanne Wunsch railML is currently offline  Susanne Wunsch railML
Messages: 0
Registered: January 2020
Hi,

Some years ago there was already some issue with "reserved vocabulary"
by programming languages.

The "default" attribute (in 'epsgCode' element) raises implementation
problems in the .NET environment.

Maybe we could rename it to "general" or so with the next major
release.

This way I would forbid "default" as element/attribute name or
enumeration value in our "Coding Policy". [1]

Any hints, questions, remarks, comments, +/-1, welcome. :-)

Kind regards...
Susanne

[1] http://www.assembla.com/spaces/railML/wiki/Coding_Policy

--
Susanne Wunsch
Schema Coordinator: railML.common
Previous Topic: Infrastructure semantics
Next Topic: RailML-files with as less infrastructure as possible
Goto Forum:
  


Current Time: Fri Mar 29 01:54:00 CET 2024