| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
I'm not at all sure if this is correct or complies with the standard —
it looks like it conceivably does, but the standard is rather vague in
places, and I don't know for sure what some of the terms in it mean.
|
| | |
|
| |
|
|
|
| |
this may occasionally produce wrong output. In a lot of places I'm
not entirey sure if I understood the standard correctly …
|
| |
|
|
|
|
|
|
|
| |
this implements all the database table schemas defined in VDV 452,
except for the ones which are very obviously not useful for talking
about train timetable data.
Note that I don't really understand what all of these values are
supposed to be yet, so a lot of them are probably unnessary.
|
| |
|
|
|
|
|
| |
this implements the file format specified in VDV 451, which essentially
appears to be a needlessly complicated version of CSV with a couple
extra features which in theory /could/ be very useful but are all either
explicitely not used or made redundant by how the rest of the standards work.
|
| |
|
|
|
|
|
|
| |
includes a message queue, more correct implementation of how the routs
work (why do they work like THAT though???), and other fun stuff.
uh also turns out you can't do schema validation with xml-types easily.
ah well. "be liberal in what you accept" and all that …
|
| |
|
