| Proposal: New optional attibutes on type block [message #941] |
Tue, 30 April 2013 14:43  |
horst.naujoks
Messages: 5
Registered: December 2012
|
Junior Member |
|
|
Hi all,
I'like to propose the following enhancement for an upcoming railML release
(not necessarily 2.2):
The physical location where a block begins and ends could be implicitly
determined by inspecting its
contained blockpart sequences and block parts respectively. From first
found block part the attribute
startOcpRef could be used and analogous from the last one the endOcpRef
attribute.
But this approach requires that all the block parts are present.
We are using railML in a scenario, where present blocks in two different
modes: overview or details.
In the overview mode we are delivering only blocks without containing
details (i.e. block parts).
Nevertheless, we want to provided the above mentioned information about
where a block start and
ends. Today, we are using two custom attributes for that, but we are sure
that it would be even
helpful for the standard railML to have to new, optional attributes
startOcpRef and analogous from
endOcpRef on the type block. Of course, these attributes where redundant
in case of present block
parts.
Kind Regards,
Horst Naujoks
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
