| Re: Sequence of ocpTT elements [message #801 is a reply to message #799] |
Thu, 31 May 2012 10:36   |
Andreas Tanner
Messages: 52
Registered: March 2012
|
Member |
|
|
Hi Susanne,
couldn't there be the case that the times in two ocptts are identical,
in particular, if times are minute-based?
I have to say that non-ordered ocptts would currently break our import.
The wiki is not versioned, but if preconditions are altered it may pose
problems. In this case, one would have to add versioning to the
documentation and changes could be only to non-released versions.
Best,
--Andreas.
Am 30.05.2012 17:31, schrieb Susanne Wunsch:
> Hi all,
>
> The Wiki page about the<ocpTT> element states (Constraints) [1]:
>
> "The sequence of the ocpTT elements inside a trainPart has to be
> according to the train path."
>
> A general rule for XML design is _not_ to evaluate the order of elements
> unless it is of importance, e.g. mixed content issues in document
> specific markup.
>
> In this case the logical sequence of the<ocpTT> elements is defined by
> its arrival and departure times (including days). There is no need to
> require this order with the XML syntax.
>
> We introduced an additional attribute for ordering if it was needed.
>
> It's the same issue with all<trackElements> in the Infrastructure
> sub-schema that don't have to be ordered neither by the relative
> nor by the absolute mileage.
>
> An export interface possibly orders its ocpTT elements chronologically.
> But an import interface should be aware of the possible chronological
> mix of ocpTT elements.
>
> I would change the Wiki page after some possible discussion.
>
> [1] http://wiki.railml.org/index.php?title=TT:ocpTT
>
> Kind regards...
> Susanne
>
|
|
|
|
Members
Search
Help
Login
Home
