Home » railML newsgroups » railml.common » data model definition vs. data exchange definition
data model definition vs. data exchange definition [message #995] Thu, 25 September 2003 14:31
Joachim Buechse is currently offline  Joachim Buechse
Messages: 8
Registered: September 2003
Junior Member
On yesterdays meeting Mr Milde suggested that RailML follows the same
strategy as the OKSTRA inititive and defines a complete data model
instead of data exchange definitions. [ Mr. Milde gave a brief
introduction of the OKSTRA project which defines schemes for a common
data model for road construction. OKSTRA is sponsored by the german
government. ]

Defining a common data model is certainly a desirable goal.

However: For existing applications it is usualy a high
(re)implementation effort to support a common data model while an
import/export function is usually quite simple. Additionally a common
data model needs to fullfill higher standards in terms of efficiency.

Therefore I would suggest RailML keeps its focus on a pure data exchange
format for the time beeing.

It might however be usefull to use IDs for physical or logical entities
that SHOULD be preserved by applications when importing from and
(re)exporting to RailML. This will allow overlaying a changed file with
an original file using XSLT, in a case where an application drops
attributes or subtags while importing or exporting (ie optional
attributes, attributes defined in a later version of the scheme, etc).


Best regards,
Joachim Buechse



buechse(at)ergonch, Phone +41 1 268 89 58, Fax +41 1 260 20 65
Ergon Informatik AG, Kleinstrasse 15, 8008 Zuerich, Switzerland
http://www.ergon.ch
________________________________________________________
e r g o n smart people - smart software
Previous Topic: RailML-Diskussionen
Next Topic: unique IDs
Goto Forum:
  


Current Time: Thu Mar 28 17:24:12 CET 2024