What should OSDM after v3.7 concentrate on?

[schlpbch]

OSDM has reached a high level of maturity and more and more people have implemented a version.

What should the OSDM working group be concentrating on?

• improve documentation
  • document on how to sell passes
  • document on seat maps
  • how to transform fares into products
• making the documentation searchable
• sunsetting OSDM v.2.0 (only used by H2O to the best of our knowledge)
• finalizing OSDM v.4.0 with goals to improve consistency, process harmonization (passenger type, fulfillment,..), and removing some ambiguity in the specification
  • Here we see the biggest issue in persuading parties to upgrade once they have a working OSDM v.3 implementation
• marketing especially OSDM to new/smaller parties
• working with CEN/CENELEC
  • offline fares to Netex
  • contributing to EUDIT

[ManuelQuemerais]

Hello Andreas,

speaking mostly for myself :

• I know for a fact that some stakeholders indeed work on some 4.0 implementations, and I think that it would be preferable to avoid having a forever moving publication date for OSDM "next" major release.
  • I obviously understand the importance to reinsure parties deploying OSDM 3.x implementations at that stage
  • But at the end of the day if we want OSDM to strive, we need to keep it alive and avoid premature fossilization (not a critic of 3.x state, 3.7 is real good)
• I do think that working on NETEX Fares support (extension to "product" model I guess) would be a right move
  • Most of OSDM specifications are already ready for proper usage on urban transit
  • The main remaing gaps are on proper support of EU tarif norm, i.e. NETEXT Fares, and on Fufillments (c.f. some improvements that may be useful for typical urban transit ticketing methods)
• I'd definitely be interested into documentation on "how to transform fares into products"

Picking up topics that are not on proposed list, we may also consider adding extensions to OSDM to cover for retailer specific usage/needs (e.g. proper actionnable structure to orchestrate purchaser payments or reimbursements, offers or bookedOffers grouping facilities that are not as constraining than current offer/bookedOffer packages, ...)

Best,
Manuel