{"id":79,"date":"2024-02-23T15:02:19","date_gmt":"2024-02-23T14:02:19","guid":{"rendered":"http:\/\/localhost\/?page_id=79"},"modified":"2024-09-17T08:46:17","modified_gmt":"2024-09-17T06:46:17","slug":"faq-general","status":"publish","type":"page","link":"https:\/\/transmodel-cen.eu\/index.php\/faq-general\/","title":{"rendered":"FAQ General"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

General FAQ<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t<\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\tWhy so many standards?\u200b<\/a>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t

We can find explanations for why there are many and divers PT standards in both the functional scope involved, some specific technology needs, and of course history.<\/p>

Functional scope
<\/b><\/p>

Public transport encompasses many functions and many stakeholders; from the very small to very large; and operating in quite different modes, so naturally its data requirements span many different categories of data and many different use cases.\u00a0Superficial discussion on the subject often tends to focus on a few specific categories of data that people are familiar\u00a0<\/b>with from their own use of using public transport, such as timetables, or real time departures,\u00a0but they are of course only part of the wider picture<\/b>. There are many other aspects to running a transport system, from\u00a0managing the network infrastructure to planning and scheduling<\/b>, through to the\u00a0collecting of fares<\/b>, each needing the exchange of data.\u00a0Informing the public with passenger information requires just a few categories out of many others.<\/b><\/p>

Technology needs
<\/b><\/p>

An important point to note is that the different functions have an evolving temporal dimension \u2013 with different process taking place, before, during and after travel and this means that\u00a0different technologies are needed to handle the real-time and dynamic aspects of a system as opposed to the static aspects.<\/b><\/p>

Each different category of information thus has its own inherent submodel<\/b>\u00a0(for example for, stops, timetables, tariff structures, control, etc), and in most legacy formats has had different formats. Furthermore, the protocols that are efficient for the occasional bulk exchange of static or slow changing reference data are quite different from the protocols best suited for dynamic APIs, so we need two separate families of standards for gathering and for delivering data.<\/p>

History<\/b><\/p>

History is also instructive. If you look at what has been happening over the past 20 years, we see that in the late 1990\u2019s we started out with numerous separate national formats as well as quite a few proprietary formats, mostly mode specific (predominately rail), not all very well documented and not all open or easy to extend. Over time, thanks to\u00a0Transmodel, a gradual alignment of terminology and concepts\u00a0<\/b>allowed a common conceptual model to emerge in the early 2000\u2019s, which in turn allowed a\u00a0new generation of European national timetable standards to be developed<\/b>\u00a0that adopted the common terminology and took advantage of the reusable concepts that had been developed to simplify their representations.<\/p>

By the end of the decade, the various national timetable formats were close enough to consider creating a common XML format, to cover the network and timetables. This was done creating NeTEx, though there wasn\u2019t actually a pressing business case for anyone to move to it and most countries concentrated on the uptake of their own still quite new national standards. On the API front , an early win was the development of the SIRI real-time API which was based on the German VDV 453 , harmonised to use the Transmodel terminology. This replaced a number of different national standards and is by now in widespread use in many European countries. APIs are of course easier and quicker to implement than bulk exchange formats since they are views over existing data sets and data feeds and SIRI was . New data sets requiring a much bigger investment in database and tools to create data.<\/p>

No country has a standard format for exchanging multimodal fare data, yet alone one that can describe the sophisticated new types of electronic fare product made possible by smartcards and mobile devices. The Transmodel fare model was implemented as a further module of NeTEx to cover this gap. Although it is a distinct module\u00a0 \u00a0of NeTEx and has a large submodel of its own , it reuses existing NeTEx components for example stops, zones and lines and operators , where ever possible<\/p>

So even if there are still a confusingly number of PT standards out there, there are a great deal fewer than there would be if we hadn\u2019t already made progress in standardisation.<\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t

\n\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t<\/path><\/svg><\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\tWhat is the difference between the different standards\/formats?\u200b<\/a>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t

Standardisations can take many flavours. You may have standardised designs, standards for protocols at different levels in the technology stack, standard formats for exchanging data, or even meta standards, that is standards for writing standards or for using a particular technology. Thus,\u00a0different standards may apply at different levels of abstraction.<\/b><\/p>

An important case in point is Transmodel itself: Transmodel isn\u2019t a concrete format. It operates at a more abstract level, providing a common set of concepts and data structures with which to describe public transport entities and their relationships. As such it has a\u00a0critical role as a unifying framework from which to develop concrete standards<\/b>. But it means that when we consider a given format we are actually dealing with two standards at the same time. The good news is that Transmodel spans the entire domain \u2013 there is only one conceptual standard!<\/p>

Concrete exchange formats and protocols necessarily have a smaller scope<\/b>. And can be placed within the \u201cbigger picture\u201d A standard with relatively broad scope, such as NeTEx, actually needs to be carefully modularised so that it can be used selectively.<\/p>

Considering the wider context of what we are really aiming at, that of\u00a0gathering information from many sources to build useful applications,<\/b>\u00a0we see that\u00a0we need exchange formats not just for the \u201cdownstream\u201d processes that deliver information to the passenger<\/b>. But also, for the\u00a0\u201cupstream\u201d processes that create and manage the data in the first place<\/b>.<\/p>

Although there are many common components, these\u00a0upstream processes contain additional concepts that don\u2019t need to be in the downstream data sets<\/b>. For example, when you are creating schedules, you need to know the times over the links of a network in order to work out the timings that will ultimately be shown to the passenger in the finalised timetable. Downstream formats may use simplified views.\u00a0 However, with the massive growth in mobile devices and smart mobility apps,\u00a0the long-term trend is to want more sophisticated function in the downstream systems too.<\/b>\u00a0It is therefor\u00a0attractive to have a richer format than can be used selectively in multiple different use cases.<\/b><\/p><\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

For more technical information about the different standards of transmodel check the FAQ pages of the DATA4PT wiki<\/a>.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

General FAQ Why so many standards?\u200b We can find explanations for why there are many and divers PT standards in both the functional scope involved, some specific technology needs, and of course history. Functional scope Public transport encompasses many functions and many stakeholders; from the very small to very large; and operating in quite different […]<\/p>\n","protected":false},"author":3,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-79","page","type-page","status-publish","hentry","entry"],"_links":{"self":[{"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/pages\/79","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/comments?post=79"}],"version-history":[{"count":59,"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/pages\/79\/revisions"}],"predecessor-version":[{"id":3148,"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/pages\/79\/revisions\/3148"}],"wp:attachment":[{"href":"https:\/\/transmodel-cen.eu\/index.php\/wp-json\/wp\/v2\/media?parent=79"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}