Home » railML newsgroups » railML.infrastructure » [railML3] Proposal for removing "any" elements (this post just points to another post where the proposal is presented)
Re: [railML3] Proposal for removing "any" elements [message #3024 is a reply to message #3016] Mon, 04 July 2022 14:16 Go to previous messageGo to previous message
Jörgen Strandberg is currently offline  Jörgen Strandberg
Messages: 15
Registered: August 2017
Junior Member
Hi,
The example of how to define and use the extension concept to represent data seems reasonable.

As a tool vendor, I still have a doubt about how to support the extension concept when parsing.
This specifically when xsi:type defines an unknown subclass of a standard railML type.

The railML parser we are developing is generated by and based on the Eclipse Modeling Framework (EMF). It will not, out of the box, support unknown subclasses.
EMF provides a pattern for handling unknown elements/attributes, which could be a part of the solution. But I would rather not have to resort to it because of the additional implementation effort.

Is there already a standard mechanism or concept of XML parsers that can be used to ignore any unknown xsi:type values, but still read all attribute values of the standard railML type?

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3] LevelCrossing Best Practice Example
Next Topic: [railML 2] Semantic Constraint at trackBegin and trackEnd
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu May 09 18:21:03 CEST 2024