Home » railML newsgroups » railml.infrastructure » Re: Missing 'any' attributes/elements
Re: Missing 'any' attributes/elements [message #1256] Mon, 28 September 2015 14:59 Go to next message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear railML IS users,

in the timetable scheme there has been the request to add more "any
elements" to the railML schema. I would like to ask you if this request
is also valid for infrastructure modeling? Please let me know if you
need appropriate schema extensions. If required I would further ask you
to create a list with all the elements where you need these new "any
elements".

Thank you very much and best regards
Christian Rahmig

Am 28.09.2015 um 14:42 schrieb Philip Wobst:
> Hello Christian,
>
> this approach would include the any-attributes you have suggested to add
> for the circulation element
> ( http://www.railml.org/forum/ro/nextarticle.php?group=2&o ffset=0&thread=121&article=429,
> TRAC ticket #267). This was discussed with the other schema coordinators
> but there does not seem to be an actual need for such a change in 2.3.
> For that reason a ticket #268 (https://trac.railml.org/ticket/268) was
> created for railML 2.3 limited to the <timetable> element only (IS in
> discussion).
>
> The elements you have specified will be extended accordingly, if there
> are no concerns from the TT community as response to this thread.
>
> Best regards,
>
> Philip
>
> With regard to the other schemas there is currently no need to add
>
> Am 15.09.2015 um 15:32 schrieb Christian Rößiger:
>> Hello all,
>>
>> in addition to my request for an any attribute for the circulation
>> element, I would like to propose a general extension of elements with
>> "any"-attributes / -elements as an input for railML 2.3. In general, I
>> think there is a lack of "any" attributes / elements within the
>> <timetable> schema. One purpose of any elements / attributes is to
>> extend railML in the short term without waiting for the next schema
>> release. This means, that these extensions must be implemented in the
>> schema before someone discovers the need for it. Since it's hard to
>> predict, for which element extensions are needed in the future, it
>> cannot be decided individually, which elements should have an any
>> element or attribute. To minimize the effort for extending the schema, I
>> wouldn't extend all elements globally. So I would propose the following
>> rules to to limit the amount of relevant elements:
>>
>> 1) all elements that have at least one attribute should also have an
>> any-attribute, elements without attributes should not have an any
>> attribute.
>> 2) all elements that contain at least on sub element should also have an
>> any-element, elements without sub elements should not have an any
>> element.
>> 3) exceptions are pure container elements, that exclusively group sub
>> elements of one type, e.g. <trains>, <trainParts>,
>> <rostering><blockParts>. These elements should not have any any elements
>> or attributes.
>>
>> [...]

--
Christian Rahmig
railML.infrastructure coordinator
Re: Missing 'any' attributes/elements [message #1257 is a reply to message #1256] Fri, 23 October 2015 10:31 Go to previous message
Christian Rahmig is currently offline  Christian Rahmig
Messages: 151
Registered: January 2011
Senior Member
Dear railML IS community,

this is the last call for extending the railML 2.3 infrastructure schema
with further "any elements" and "any attributes": Please let me know
about your wishes until next Friday, Octobre 31, 2015. Thank you very much.

*** German version ****
Wenn noch weitere "Any-Elemente" oder "Any-Attribute" für die nächste
railML-Version 2.3 benötigt werden, meldet sie mir bitte bis zum
kommenden Freitag. Vielen Dank.

Best regards
Christian

Am 28.09.2015 um 14:59 schrieb Christian Rahmig:
> Dear railML IS users,
>
> in the timetable scheme there has been the request to add more "any
> elements" to the railML schema. I would like to ask you if this request
> is also valid for infrastructure modeling? Please let me know if you
> need appropriate schema extensions. If required I would further ask you
> to create a list with all the elements where you need these new "any
> elements".
>
> Thank you very much and best regards
> Christian Rahmig
>
> Am 28.09.2015 um 14:42 schrieb Philip Wobst:
>> Hello Christian,
>>
>> this approach would include the any-attributes you have suggested to add
>> for the circulation element
>> ( http://www.railml.org/forum/ro/nextarticle.php?group=2&o ffset=0&thread=121&article=429,
>>
>> TRAC ticket #267). This was discussed with the other schema coordinators
>> but there does not seem to be an actual need for such a change in 2.3.
>> For that reason a ticket #268 (https://trac.railml.org/ticket/268) was
>> created for railML 2.3 limited to the <timetable> element only (IS in
>> discussion).
>>
>> The elements you have specified will be extended accordingly, if there
>> are no concerns from the TT community as response to this thread.
>>
>> Best regards,
>>
>> Philip
>>
>> With regard to the other schemas there is currently no need to add
>>
>> Am 15.09.2015 um 15:32 schrieb Christian Rößiger:
>>> Hello all,
>>>
>>> in addition to my request for an any attribute for the circulation
>>> element, I would like to propose a general extension of elements with
>>> "any"-attributes / -elements as an input for railML 2.3. In general, I
>>> think there is a lack of "any" attributes / elements within the
>>> <timetable> schema. One purpose of any elements / attributes is to
>>> extend railML in the short term without waiting for the next schema
>>> release. This means, that these extensions must be implemented in the
>>> schema before someone discovers the need for it. Since it's hard to
>>> predict, for which element extensions are needed in the future, it
>>> cannot be decided individually, which elements should have an any
>>> element or attribute. To minimize the effort for extending the schema, I
>>> wouldn't extend all elements globally. So I would propose the following
>>> rules to to limit the amount of relevant elements:
>>>
>>> 1) all elements that have at least one attribute should also have an
>>> any-attribute, elements without attributes should not have an any
>>> attribute.
>>> 2) all elements that contain at least on sub element should also have an
>>> any-element, elements without sub elements should not have an any
>>> element.
>>> 3) exceptions are pure container elements, that exclusively group sub
>>> elements of one type, e.g. <trains>, <trainParts>,
>>> <rostering><blockParts>. These elements should not have any any elements
>>> or attributes.
>>>
>>> [...]
>

--
Christian Rahmig
railML.infrastructure coordinator
Previous Topic: need for new attribute "virtual" of trainDetector
Next Topic: Additional attribute for crossing roads/rivers
Goto Forum:
  


Current Time: Wed Mar 29 11:12:25 CEST 2017