| Concerns about RailML interoperability [message #1100] |
Fri, 06 May 2011 11:56  |
tuomas.tiihonen
Messages: 15
Registered: May 2011
|
Junior Member |
|
|
Hi,
I am concerned. My concern is the semantic interoperability of the RailML
standard now and in the future.
RailML syntax is defined in schema files, so it is easy for any member of
community or outside of community to make implementation that can accept
RailML as long as it passes XML validation. Problem comes from semantics.
As I have understood, the semantics are documented only in wiki pages.
Wiki pages are not complete and creates this huge risk for fragmenting the
railML to different branches, where each branch is one-to-one agreement
between users of the railML.
How is this handled currently? Does every implementation using railML have
separate agreements of semantics? Are there n-amount of undocumented
semantics?
Does the community recognize this problem and are there any actions
ongoing to make the semantics complete? I have now only power of guessing
in most parts of railML semantics.
I know that there exists standards where this problem has risen too late.
So late that there can be tens or hundreds of different implementations of
valid standard-using-software, but that can only inter operate
out-of-the-box with 1-3 other implementations.
This is huge stumbling stone and must be overcome to keep railML usable.
Overcoming comes more difficult day by day.
With Kindest Regards,
Tuomas Tiihonen
--
----== posted via PHP Headliner ==----
|
|
|
|
Members
Search
Help
Login
Home
