| class and type [message #1180] |
Thu, 01 February 2007 13:58  |
Joachim.Rubröder
Messages: 33
Registered: September 2004
|
Member |
|
|
Hello,
We started to use part of the rollingstock scheme for exchanging
rollingstock data via web service.
While generating a lot of classes and data types, we realised that the
vehicleType has a sub element "class". The operator has an attribute named
"class" as well and the manufacturer with the meaningless attribute "type"
like many other attributes in railML. This leads for example to generating
the class named "class", not forbidden but very confusing.
I therefore suggest to define a short list of forbidden names ("class",
"type", "element", "date" ...) and to rename the existing ones to
"classification", "operatorClass", "manufacturerType" and so on.
Kind regards
Joachim
|
|
|
|
| Re: class and type [message #1181 is a reply to message #1180] |
Sat, 10 February 2007 08:29  |
Joerg von Lingen
Messages: 148
Registered: May 2011
|
Senior Member |
|
|
Hello Joachim,
good suggestion I will look into these issues when returning from my business trip.
On 01.02.2007 13:58, jrubroeder(at)sma-partnerch wrote:
> Hello,
> We started to use part of the rollingstock scheme for exchanging
> rollingstock data via web service.
>
> While generating a lot of classes and data types, we realised that the
> vehicleType has a sub element "class". The operator has an attribute named
> "class" as well and the manufacturer with the meaningless attribute "type"
> like many other attributes in railML. This leads for example to generating
> the class named "class", not forbidden but very confusing.
>
> I therefore suggest to define a short list of forbidden names ("class",
> "type", "element", "date" ...) and to rename the existing ones to
> "classification", "operatorClass", "manufacturerType" and so on.
>
> Kind regards
> Joachim
>
--
Best regards,
Jörg von Lingen
|
|
|
|
| Re: class and type [message #1182 is a reply to message #1180] |
Mon, 05 March 2007 17:01 |
Joerg von Lingen
Messages: 148
Registered: May 2011
|
Senior Member |
|
|
Hello,
with respect to Joachim's suggestions I have revised the scheme for ambigious names and published
the new version at http://www.railml.org/genesis/rollingstock/rollingstock_1.05 .xsd.
On 01.02.2007 13:58, jrubroeder(at)sma-partnerch wrote:
> Hello,
> We started to use part of the rollingstock scheme for exchanging
> rollingstock data via web service.
>
> While generating a lot of classes and data types, we realised that the
> vehicleType has a sub element "class". The operator has an attribute named
> "class" as well and the manufacturer with the meaningless attribute "type"
> like many other attributes in railML. This leads for example to generating
> the class named "class", not forbidden but very confusing.
>
> I therefore suggest to define a short list of forbidden names ("class",
> "type", "element", "date" ...) and to rename the existing ones to
> "classification", "operatorClass", "manufacturerType" and so on.
>
> Kind regards
> Joachim
>
--
Mit freundlichen Grüßen/Best regards,
----------------------------------------
Jörg von Lingen
|
|
|
|
Members
Search
Help
Login
Home
