FAQ NeTEX - Revision history

Admin at 20:58, 30 July 2025

2025-07-30T20:58:54Z

← Older revision		Revision as of 22:58, 30 July 2025
Line 273:		Line 273:
	4) Create your own .xml examples based on the XSD and the examples available in GitHub. If the user has no technical background, then IT tool provider is needed to support him/her following the same steps. A general list of tools is available in [https://data4pt.org/w/index.php?title=NeTEX#Software_.26_tools_.F0.9F.A7.B0 DATA4PT wiki.]		4) Create your own .xml examples based on the XSD and the examples available in GitHub. If the user has no technical background, then IT tool provider is needed to support him/her following the same steps. A general list of tools is available in [https://data4pt.org/w/index.php?title=NeTEX#Software_.26_tools_.F0.9F.A7.B0 DATA4PT wiki.]

	5) Validate the example with the XML editor and the Greenlight validator ~~https://greenlight.itxpt.eu/~~. The latter is the tool that provides feedback both on errors that concern the NeTEx XSD but also the content (plausibility checks). ~~More artefacts about the tool where customisation of the rules is possible is available in [https://github.com/ITxPT/DATA4PTTools /ITxPT/DATA4PTTools] GitHUb repository.~~		5) Validate the example with the XML editor and the Greenlight validator. The latter is the tool that provides feedback both on errors that concern the NeTEx XSD but also the content (plausibility checks).

	6) Use the [https://data4pt-project.eu/requests-requirements/ DATA4PT helpdesk] for more technical guidance.		6) Use the [https://data4pt-project.eu/requests-requirements/ DATA4PT helpdesk] for more technical guidance.

Anonymous: added new questions according to netex website

2024-08-29T13:29:50Z

added new questions according to netex website

← Older revision		Revision as of 15:29, 29 August 2024
Line 320:		Line 320:
	== Can I have different journey timings for different times of day? ==		== Can I have different journey timings for different times of day? ==
	Part 2 of NeTEx includes reusable components for constructing timetables of journeys from reusable components, NeTEx separates the concerns of where the timing of a PT route takes place (The TIMING PATTERN made up of TIMING POINTs and TIMING LINKs) from the actual timing values (which are held separately as RUN TIMEs and WAIT TIMEs). Different sets of timing values belong to different TIME DEMAND TYPEs (Peak, off peak, late night, etc) can be used with the same TIMING PATTERN to generate accurate timetables for journeys at different times of day.		Part 2 of NeTEx includes reusable components for constructing timetables of journeys from reusable components, NeTEx separates the concerns of where the timing of a PT route takes place (The TIMING PATTERN made up of TIMING POINTs and TIMING LINKs) from the actual timing values (which are held separately as RUN TIMEs and WAIT TIMEs). Different sets of timing values belong to different TIME DEMAND TYPEs (Peak, off peak, late night, etc) can be used with the same TIMING PATTERN to generate accurate timetables for journeys at different times of day.

			== Can NeTEx describe zone-based fares? ==
			NeTEx can be used to describe zone-based fare systems of any topology ranging from a simple patchwork (adjacent zones) to the complex, (honeycomb, doughnut) etc). The TARIFF ZONE allows zones to be associated with stops and stations. Mixed zonal and stage systems are also possible. Fare pricing may be a flat fare system per zone, or zone to zone using a (DISTANCE MATRIX ELEMENT), or be differentially priced for particular sequences of zones (using FARE STRUCTURE ELEMENTs in SEQUENCE).

			== Can I restrict certain products to certain classes of user? ==
			Among the many different usage conditions that can be specified for NeTEx fare products are restrictions on the type of user – child, senior, student, disabled, etc using a USER PROFILE that may be given precise eligibility criteria (e.g. on age, membership, domicile, etc). A GROUP PROFILE allows the number and makeup of groups to be specified; it can also be used to specify companion criteria for disabled users and other special cases.

			== Can I specify time-based constraints on travel? ==
			Some fare products only allow travel at particular times – such constraints can be expressed using USAGE PARAMETERs. Others only allow travel for a particular duration; FARE STRUCTURE ELEMENTs with TIME STUCTURE FACTORs can be used to describe the different durations. Furthermore, sometimes journey time is related to journey length, so for example a longer time is allowed for a two-zone trip than a one zone trip; all this can be precisely specified in NeTEx.

			Temporal conditions may also apply to the purchase or refund of tickets, likewise, expressed as USAGE PARAMETERs attached to fare products.

			As well as the routine examples given above, NeTEx can also handle more complex cases. For example, in the periphery of a large city, off peak times may start at different times in each station since by the time a journey to the centre starting from the station ends, the peak period will have ended.

			== Does NeTEx support dynamic/yield managed pricing? ==
			For long-distance travel, especially on-rail, there is increasing use of yield managed fares with dynamic pricing, provided by web services. Note that such applications increase rather than decrease the need for standards such as NeTEx as such applications nonetheless require a machine-readable definition of the access rights fare structure and usage conditions that apply to the products for which prices are supplied. Furthermore, the search parameters used to find the best fare for a user (such as age, possession of rail cards, fulfilment method etc) need to correspond to the properties of the fare product. The NeTEx Part3 specification and UML model includes an annex showing a sample fare query which shows all the NeTEx model elements relevant for constructing a Fare API.

			== Can NeTEx define products for modern e-card based ticketing? ==
			Yes. Electronic payment cards such as OV Chipkart (NL), Oyster (London region), Navigo (Paris region) Sube T (Madrid), BIP Card (Turin) are becoming increasingly common and etc transport operators are able to devise increasingly sophisticate products. For example,, Oyster has fares that adjust according to consumption, capping the cost of trips made in a day to that of a day pass. NeTEx is able to describe the fare structures and scope and conditions for such complex products, as well as to supporting a record of consumption for account-based products. (A NeTEx SALES TRANSACTION records an individual PRODUCT SALE).

			As products on cards are physical invisible to the user, the ability to create user readable representations become increasingly important – such applications require a machine-readable format with corresponding human readable rendering, such as is available through NeTEx.

			== Does NeTEx support Flexible and Demand Responsive Travel? ==
			Yes, unlike classical route and timetable standards, NeTEx is also designed to support FTS (Flexible Transport Service) and DRT (Demand Responsive Transport). DRT and FTS often cover similar services; FTS being more generic since flexibility may not be directly linked to the demand, but may be related to some operating needs or cost optimisations.

			The flexibility can be applied to the line, route and stop structure (areas, corridors, hail and ride, etc.) or to their scheduling (dynamic and/or demand responsive passing times, with all necessary booking arrangements and contact details).

			== Can I create applications to run in different national Languages? ==
			Yes, NeTEx includes full support for internationalisation. All text elements may be created in multiple languages so that place names and other names and descriptions can be provided in one or more languages. Other aspects important for multiregional use are parameterized such as time zones, currency, etc. and the Calendar functions allow conditions based on different national holidays to be described.

			== Can I have different versions of data for the same element extant at the same time? ==
			Yes, every NeTEx data element can be versioned, and multiple versions can coexist. Coherent sets of data are assembled for exchange using a ‘version frame’, which itself has a version and knows the version of the elements in it. There are specific types of version frame for different types of data that are commonly exchanged together (SERVICE, TIMETABLE, FARE etc).

			== Can I create Network maps with NeTEx? ==
			Yes, one of the additional capabilities of NeTEx is the ability to define and exchange the full topology of a network as presented in simplified view to a user (often with presentational attributes such as colour), with non-directional network segments, loops etc, while also retaining a projection onto the actual underlying stops and route. This allows automatic creation of interactive map applications.

			* The LINE element names the line and sets basic properties

			* The LINE NETWORK and LINE SECTION elements can be used to describe the topology

			* The ROUTE, ROUTELINK, and ROUTE POINT elements can be used to define the directional elements of the underlying line

			* The SCHEDULED STOP POINT can be used to define the stops of a line.

			All these objects can have their own geographic positions and geometry or/and be projected onto a custom drawn map using a SCHEMATIC MAP element.

			== I have my own classification for Stops/ Lines / etc. Can NeTEx handle this? ==
			Yes, NeTEx allows arbitrary user defined code classifications for elements using the TYPE OF STOP, TYPE OF LINE and other ‘Type of Entity’ elements that. In addition, NeTEx, to encourage standardised use, also provides fixed enumerations of many commonly found classifications of specific elements, including types of equipment, on-board facilities, etc. The ‘Key Value’ extension mechanism allows Also allows additional user defined attributes to be added, which can include classifier.

Anonymous: updated FAQ

2024-08-29T13:11:26Z

updated FAQ

← Older revision		Revision as of 15:11, 29 August 2024
Line 314:		Line 314:

	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 17:38, 25 March 2024 (CET)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 17:38, 25 March 2024 (CET)

			== Can NeTEx handle frequency-based services? ==
			Frequency based serves are typically specified as operating at a given interval, rather than particular times. From a passenger point of view multiple journeys will typically be presented as a single journey running at an approximate interval, for example “every six to 10 minutes”. NeTEx uses TEMPLATE VEHICLE journeys to describe such journeys. From an operational point of view there will still need to be specific service journeys scheduled to fulfil the required frequency of service and NeTEx can also include these to support real time journeys.

			== Can I have different journey timings for different times of day? ==
			Part 2 of NeTEx includes reusable components for constructing timetables of journeys from reusable components, NeTEx separates the concerns of where the timing of a PT route takes place (The TIMING PATTERN made up of TIMING POINTs and TIMING LINKs) from the actual timing values (which are held separately as RUN TIMEs and WAIT TIMEs). Different sets of timing values belong to different TIME DEMAND TYPEs (Peak, off peak, late night, etc) can be used with the same TIMING PATTERN to generate accurate timetables for journeys at different times of day.

Anasfou at 15:39, 25 March 2024

2024-03-25T15:39:09Z

← Older revision		Revision as of 17:39, 25 March 2024
Line 298:		Line 298:


	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 12:18, 16 February ~~2023~~ (CET)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 12:18, 16 February 2024 (CET)

			== Does a scheduledStopPoint ID need to be unique per public transport Line? ==

			A scheduledStopPoint ID does not need to be unique per Line.
			In situations where several Lines use the exact same stop point they may refer to this same stop point using the same scheduledStopPoint ID. If there is a unique ID for the exact same stop that can be used globally it is also ideal from interoperability point of view.

			More precisely, based on NeTEx terminology, a LINE is defined as "A group of ROUTEs which is generally known to the public by a similar name or number."
			A ROUTE is defined as "An ordered list of located POINTs defining one single path through the road (or rail) network. A ROUTE may pass through the same POINT more than once."
			JOURNEY PATTERN, defined as "An ordered list of SCHEDULED STOP POINTs and TIMING POINTs on a single ROUTE, describing the pattern of working for public transport vehicles. A JOURNEY PATTERN may pass through the same POINT more than once. The first point of a JOURNEY PATTERN is the origin. The last point is the destination."

			In order not to make confusion, when parsing the XML input, the data user needs to sufficiently preserving awareness of the context in which the scheduledStopPoint ID is being used. With a correct awareness of the context, the ID can be augmented, for example via a composite ID made up of Line plus stop IDs. This would make different occurrences of the same stop have different IDs, without breaking the NeTEx rules.



			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 17:38, 25 March 2024 (CET)

Anasfou: /* How to implement DayTypeAssignment in NeTEx? Using OperatingPeriodRef or UicOperatingPeriodRef? */

2024-02-16T11:50:00Z

How to implement DayTypeAssignment in NeTEx? Using OperatingPeriodRef or UicOperatingPeriodRef?

← Older revision		Revision as of 13:50, 16 February 2024
Line 292:		Line 292:
	== How to implement DayTypeAssignment in NeTEx? Using OperatingPeriodRef or UicOperatingPeriodRef? ==		== How to implement DayTypeAssignment in NeTEx? Using OperatingPeriodRef or UicOperatingPeriodRef? ==

	Both "OperatingPeriodRef" and "UicOperatingPeriodRef" are in the same substitutionGroup named OperatingPeriods, therefore both options may be used without impacting the interoperability of the file. UicOperatingPeriodRef is probably cleaner to reference a UicOperatingPeriod.		Both "OperatingPeriodRef" and "UicOperatingPeriodRef" are in the same substitutionGroup named OperatingPeriods, therefore both options may be used without impacting the interoperability of the file. UicOperatingPeriodRef is probably cleaner to reference a UicOperatingPeriod.In NeTEx EPIP (European Passenger Information Profile) UicOperatingPeriod is mandatory (providing the ValidDayBits is mandatory).
	[[File:Image.png\|thumb]]		[[File:Image.png\|thumb]]

Anasfou: /* How to implement DayTypeAssignment in NeTEx? Using OperatingPeriodRef or UicOperatingPeriodRef? */

2024-02-16T11:25:11Z

How to implement DayTypeAssignment in NeTEx? Using OperatingPeriodRef or UicOperatingPeriodRef?

← Older revision		Revision as of 13:25, 16 February 2024
Line 293:		Line 293:

	Both "OperatingPeriodRef" and "UicOperatingPeriodRef" are in the same substitutionGroup named OperatingPeriods, therefore both options may be used without impacting the interoperability of the file. UicOperatingPeriodRef is probably cleaner to reference a UicOperatingPeriod.		Both "OperatingPeriodRef" and "UicOperatingPeriodRef" are in the same substitutionGroup named OperatingPeriods, therefore both options may be used without impacting the interoperability of the file. UicOperatingPeriodRef is probably cleaner to reference a UicOperatingPeriod.
			[[File:Image.png\|thumb]]

Anasfou at 11:23, 16 February 2024

2024-02-16T11:23:04Z

← Older revision		Revision as of 13:23, 16 February 2024
Line 284:		Line 284:

	Relevant material is available [https://data4pt.org/w/index.php?title=NeTEX#NeTEx_part_5_for_.F0.9F.86.95_modes here]		Relevant material is available [https://data4pt.org/w/index.php?title=NeTEX#NeTEx_part_5_for_.F0.9F.86.95_modes here]


	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 10:45, 6 November 2023 (CET)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 10:45, 6 November 2023 (CET)



			== How to implement DayTypeAssignment in NeTEx? Using OperatingPeriodRef or UicOperatingPeriodRef? ==

			Both "OperatingPeriodRef" and "UicOperatingPeriodRef" are in the same substitutionGroup named OperatingPeriods, therefore both options may be used without impacting the interoperability of the file. UicOperatingPeriodRef is probably cleaner to reference a UicOperatingPeriod.




			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 12:18, 16 February 2023 (CET)

Anasfou: /* How to start implementing NeTEx Part 5 for new modes (vehicle sharing, rental, taxis etc.)? */

2023-11-13T14:13:11Z

How to start implementing NeTEx Part 5 for new modes (vehicle sharing, rental, taxis etc.)?

← Older revision		Revision as of 16:13, 13 November 2023
Line 265:		Line 265:
	Simple steps for new users/implementers of NeTEx Part 5:		Simple steps for new users/implementers of NeTEx Part 5:

	1) Watch the introduction webinar for NeTEx Part 5, available on DATA4PT website (direct ~~links~~ to the video and presentation of the webinar).		1) Watch the introduction webinar for NeTEx Part 5, available on [https://data4pt-project.eu/knowledge-database/training-material/ DATA4PT website] under the title “DATA4PT webinar 24 November 2022: NeTEx and SIRI standards for new modes” (direct link to the [https://www.youtube.com/watch?v=F_lK1mfKgbk video] and presentation of the [https://data4pt-project.eu/wp-content/uploads/2022/12/DATA4PT-NeTEx-validation-tool-webinar_Presentation.pdf webinar]).

	2)Read the pdf – official CEN documentation CEN/TS 16614-5 (where also some examples are given). The ~~doc~~ can be bought from any national standardization body.		2) Read the pdf – official CEN documentation CEN/TS 16614-5 (where also some examples are given). The document can be bought from any national standardization body.

	3) Use XML editor (there are commercial tools ~~like XML spy, oxygen~~ or free tools), to check the XSD and check the examples from Github.		3) Use XML editor (there are commercial tools or free tools - a short list is available by [https://data4pt.org/w/index.php?title=NeTEX#Software_.26_tools_.F0.9F.A7.B0 DATA4PT wiki]), to check the [https://github.com/NeTEx-CEN/NeTEx/tree/master/xsd/netex_part_5 XSD for Part 5] and check the [https://github.com/NeTEx-CEN/NeTEx/tree/master/examples/functions/newModes examples] from [https://github.com/NeTEx-CEN/NeTEx/tree/master Github NeTEx repository].

	4) Create ~~their~~ own .xml examples based on the XSD and the examples available in GitHub. ~~Contact tool providers to see if they support NeTEx files creation for new modes (check the list of the tools dedicated for EPIP – might have been extended for NeTEx Part 5. The truth is that if~~ the user has no ~~IT skills at all~~, then ~~only an~~ IT tool provider ~~can~~ support him/her following the same steps.		4) Create your own .xml examples based on the XSD and the examples available in GitHub. If the user has no technical background, then IT tool provider is needed to support him/her following the same steps. A general list of tools is available in [https://data4pt.org/w/index.php?title=NeTEX#Software_.26_tools_.F0.9F.A7.B0 DATA4PT wiki.]

	5) Validate the example with the XML editor and the Greenlight validator https://greenlight.itxpt.eu/. The latter is the tool that provides feedback both on errors that concern the NeTEx XSD but also the content (plausibility checks).		5) Validate the example with the XML editor and the Greenlight validator https://greenlight.itxpt.eu/. The latter is the tool that provides feedback both on errors that concern the NeTEx XSD but also the content (plausibility checks). More artefacts about the tool where customisation of the rules is possible is available in [https://github.com/ITxPT/DATA4PTTools /ITxPT/DATA4PTTools] GitHUb repository.

	6)Use the DATA4PT helpdesk for more technical guidance. To start with, it is important the operators to learn about the theoretical background. There is already available on DATA4PT website a webinar and corresponding presentation under the title “DATA4PT webinar 24 November 2022: NeTEx and SIRI standards for new modes”		6) Use the [https://data4pt-project.eu/requests-requirements/ DATA4PT helpdesk] for more technical guidance.

	~~Additional very important material is the XSD for Part 5. https://data4pt.org/w/index.php?title=NeTEX#NeTEx_Part_5_for_New_Modes. In NeTEx – CEN Github, there are also some examples of XML files.~~

	~~There are tools provided either for free or not, with which someone can create NeTEx files. Information about existing tools are available~~ [https://data4pt.~~org~~/w/~~index.php?title=NeTEX#Software_.26_tools_.F0.9F.A7.B0 here~~]. ~~However, there is a need to contact the tool providers and ask them if Part 5 is also included nowadays.~~

	Finally, a useful material for small operators that they use already GBFS is:		Finally, a useful material for small operators that they use already GBFS is:

Anasfou: /* Is it possible to get access to the fares/schedule data? */

2023-11-06T08:48:55Z

Is it possible to get access to the fares/schedule data?

← Older revision		Revision as of 10:48, 6 November 2023
Line 35:		Line 35:
	http://netex-cen.eu/wp-content/uploads/2015/12/10.NeTEx-Fare-WhitePaper_1.04.pdf		http://netex-cen.eu/wp-content/uploads/2015/12/10.NeTEx-Fare-WhitePaper_1.04.pdf

	Fares can be quite big topic and people defining them have a lot of imagination. This resulted in NeTex Part 3 being quite big and it is strongly advised to use only a small subset of it which is relevant to your needs. This what we call a Profile. France, Nordic countries, and UK have a fares national profiles. Information about current national profiles is about existing profiles is available [[NeTEX\|here]]. A minimum European profile is currently under specification with the support of DATA4PT and it is planned to be delivered to CEN processes by end of June 2024.		Fares can be quite big topic and people defining them have a lot of imagination. This resulted in NeTex Part 3 being quite big and it is strongly advised to use only a small subset of it which is relevant to your needs. This what we call a Profile. France, Nordic countries, and UK have a fares national profiles. Information about current national profiles is about existing profiles is available [https://data4pt.org/w/index.php?title=NeTEX#Published_profiles here]. A minimum European profile is currently under specification with the support of DATA4PT and it is planned to be delivered to CEN processes by end of June 2024.

	--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 10:28, 06 November 2023 (CEST)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 10:28, 06 November 2023 (CEST)

Anasfou: /* How to model "hail and ride" section? */

2023-11-06T08:45:53Z

How to model "hail and ride" section?

← Older revision		Revision as of 10:45, 6 November 2023
Line 210:		Line 210:


			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 11:50, 3 May 2023 (CET)







	== How to model a transport ticket that costs 6 euros on the 1st day and 3 euros for each additional day? ==		== How to model a transport ticket that costs 6 euros on the 1st day and 3 euros for each additional day? ==

Line 244:		Line 237:


			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 11:13, 1 September 2023 (CET)
			== How to model "hail and ride" section? ==
			Hail and ride usually is modelled by using a FlexibleStopPlace that can refer to HailAndRide areas as shown in the UML diagrams below. Hail and Ride is described in CEN TS 16614-1. Examples can be found in [https://github.com/NeTEx-CEN/NeTEx/tree/master/examples NeTEx-CEN GitHub] like this [https://github.com/NeTEx-CEN/NeTEx/blob/master/examples/functions/timetable/Netex_01.4_Bus_SimpleTimetable_WithConnection.xml one].

			[[File:FlexibleStopPlace with HailandRideArea.png\|thumb\|UML diagram of FlexibleStopPlace with HailAndRide]]


			[[File:HailAndRide.png\|thumb\|364x364px]]


Line 260:		Line 258:


	~~== How to model "hail and ride" section? ==~~
	Hail and ride usually is modelled by using a FlexibleStopPlace that can refer to HailAndRide areas as shown in the UML diagrams below. Hail and Ride is described in CEN TS 16614-1. Examples can be found in [https://github.com/NeTEx-CEN/NeTEx/tree/master/examples NeTEx-CEN GitHub] like this [https://github.com/NeTEx-CEN/NeTEx/blob/master/examples/functions/timetable/Netex_01.4_Bus_SimpleTimetable_WithConnection.xml one].

	~~[[File:FlexibleStopPlace with HailandRideArea.png\|thumb\|UML diagram of FlexibleStopPlace with HailAndRide]]~~

			--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 16:40, 17 October 2023 (CET)

	~~[[File:HailAndRide~~.~~png\|thumb\|364x364px]]~~		== How to start implementing NeTEx Part 5 for new modes (vehicle sharing, rental, taxis etc.)? ==
			Simple steps for new users/implementers of NeTEx Part 5:

			1) Watch the introduction webinar for NeTEx Part 5, available on DATA4PT website (direct links to the video and presentation of the webinar).

			2)Read the pdf – official CEN documentation CEN/TS 16614-5 (where also some examples are given). The doc can be bought from any national standardization body.

			3) Use XML editor (there are commercial tools like XML spy, oxygen or free tools), to check the XSD and check the examples from Github.

			4) Create their own .xml examples based on the XSD and the examples available in GitHub. Contact tool providers to see if they support NeTEx files creation for new modes (check the list of the tools dedicated for EPIP – might have been extended for NeTEx Part 5. The truth is that if the user has no IT skills at all, then only an IT tool provider can support him/her following the same steps.

	~~== How to start implementing~~ NeTEx ~~Part 5 for new modes~~ (~~vehicle sharing, rental, taxis etc~~.~~)?"~~		5) Validate the example with the XML editor and the Greenlight validator https://greenlight.itxpt.eu/. The latter is the tool that provides feedback both on errors that concern the NeTEx XSD but also the content (plausibility checks).

	~~Simple steps for new users/implementers of NeTEx Part 5:~~		6)Use the DATA4PT helpdesk for more technical guidance. To start with, it is important the operators to learn about the theoretical background. There is already available on DATA4PT website a webinar and corresponding presentation under the title “DATA4PT webinar 24 November 2022: NeTEx and SIRI standards for new modes”
	~~1) Watch the introduction webinar for NeTEx Part 5, available on DATA4PT website (direct links to the video and presentation of the webinar).~~
	~~2) Read the pdf – official CEN documentation CEN/TS 16614-5 (where also some examples are given). The doc can be bought from any national standardization body.~~
	~~3) Use XML editor (there are commercial tools like XML spy, oxygen or free tools), to check the XSD and check the examples from Github~~
	4) Create their own .xml examples based on the XSD and the examples available in GitHub. Contact tool providers to see if they support NeTEx files creation for new modes (check the list of the tools dedicated for EPIP – might have been extended for NeTEx Part 5). The truth is that if the user has no IT skills at all, then only an IT tool provider can support him/her following the same steps.
	5) Validate the example with the XML editor and the Greenlight validator https://greenlight.itxpt.eu/. The latter is the tool that provides feedback both on errors that concern the NeTEx XSD but also the content (plausibility checks).
	6) Use the DATA4PT helpdesk for more technical guidance.To start with, it is important the operators to learn about the theoretical background. There is already available on DATA4PT website a webinar and corresponding presentation under the title “DATA4PT webinar 24 November 2022: NeTEx and SIRI standards for new modes” ~~(they need to scroll down in the list to find it or you share the direct links to the video and ppt).~~

	Additional very important material is the XSD for Part 5. https://data4pt.org/w/index.php?title=NeTEX#NeTEx_Part_5_for_New_Modes. In NeTEx – CEN Github, there are also some examples of XML files.		Additional very important material is the XSD for Part 5. https://data4pt.org/w/index.php?title=NeTEX#NeTEx_Part_5_for_New_Modes. In NeTEx – CEN Github, there are also some examples of XML files.

	There are tools provided either for free or not, with which someone can create NeTEx files. https://data4pt.org/w/index.php?title=NeTEX#~~Editing_~~.~~2FManagement_~~.~~26_visualisation_tools_for_NeTEx_data~~. However, there is a need to contact the tool providers and ask them if Part 5 is also included nowadays.		There are tools provided either for free or not, with which someone can create NeTEx files. Information about existing tools are available [https://data4pt.org/w/index.php?title=NeTEX#Software_.26_tools_.F0.9F.A7.B0 here]. However, there is a need to contact the tool providers and ask them if Part 5 is also included nowadays.

	Finally, a useful material for small operators that they use already GBFS is:		Finally, a useful material for small operators that they use already GBFS is:
	~~- the canonical mapping between GBFS and NeTEx/SIRI to get their head around the fields/attributes they need at a quick glance~~
	~~- the .xml example that is GBFS-based from the NeTEx GitHub repo.~~

			-the canonical mapping between GBFS and NeTEx/SIRI to get their head around the fields/attributes they need at a quick glance

			- the .xml example that is GBFS-based from the NeTEx GitHub repo.

			Relevant material is available [https://data4pt.org/w/index.php?title=NeTEX#NeTEx_part_5_for_.F0.9F.86.95_modes here]

	~~I would also recommend you to connect the small operators with some large operators that they have already similar development~~ (~~for example authorities that they have under their responsibility all modes including new ones~~)~~. We may also help in bringing them in contact with operators/authorities working on the topic in other countries to exchange knowledge~~ (~~for example Italy has defined national profile to support new modes, PTA in Vienna works on the implementation of NeTEx new modes- preparing their local profile, etc.~~)		--[[User:Anasfou\|DATA4PT Team]] ([[User talk:Anasfou\|talk]]) 10:45, 6 November 2023 (CET)