Forum: railml.common » [railML3] Extension methods

Home » railML newsgroups » railml.common » [railML3] Extension methods (Should we consider other ways to extend railML?)

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: [railML3] Extension methods [message #3003 is a reply to message #2976]

Fri, 29 April 2022 18:45

Jörgen Strandberg
Messages: 15
Registered: August 2017

Junior Member

Hi,

I have too found it hard to implement a solution for our non-railml data. But I am not sure that it's a bad thing that handling non-standard data is tedious or discouraging.

Could even some new use cases be defined out of the needs for the additional data you indirectly speak of?

A technical question related to the solution where xsi:type is used to define a subclass of a standard type:
Will that not pose a requirement on standard-compliant tools to be able to load foreign namespaces dynamically, to be able to access the standard attribute values?

Report message to a moderator

[Message index]

		[railML3] Extension methods By: Thomas Nygreen JBD on Fri, 11 January 2019 17:01
		Re: [railML3] Extension methods By: Milan Wölke on Thu, 09 December 2021 16:58
		Re: [railML3] Extension methods By: Dirk Bräuer on Fri, 18 March 2022 16:09
		Re: [railML3] Extension methods By: Milan Wölke on Thu, 24 March 2022 14:31
		Re: [railML3] Extension methods By: Jörgen Strandberg on Fri, 29 April 2022 18:45
		Re: [railML3] Extension methods By: Milan Wölke on Mon, 30 May 2022 19:57

Previous Topic:	[railML3] Refactoring of OrganizationalUnits
Next Topic:	[railML3] Binding position of Meta-Data in railML-Scheme

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed May 01 08:03:20 CEST 2024