Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turning prose into data - On the peculiarities of ETCS specifications #4

Open
morido opened this issue Dec 7, 2015 · 2 comments
Open

Comments

@morido
Copy link

morido commented Dec 7, 2015

As a matter of fact, ETCS specifications do not make for a nice bedtime read. Let's see how we can change that!

In this session we will...

  • ... take a look at the status quo (How is relevant information currently conveyed?)
  • ... see how openETCS tackled the problem of integrating the specifications into their toolchain (Word to ReqIF converter)
  • ... examine the ongoing shift towards a more open culture (change management, data exchange)
  • ... discuss ways to improve the current situation (consistency, ambiguity, traceability, long term availability, etc.)

If anyone feels like co-hosting this slot with me, get in touch. I'd be happy.

@jastram
Copy link
Member

jastram commented Dec 8, 2015

@morido,

If anyone feels like co-hosting this slot with me, get in touch. I'd be happy.

I just proposed #7, which is related (but with a different focus). If you are interested we could decide to join the sessions on the spot in Munich, depending on the response.

@morido
Copy link
Author

morido commented Dec 8, 2015

If you are interested we could decide to join the sessions on the spot in Munich, depending on the response.

Sounds good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants