8000 Clarity over mandatory entities & fields · Issue #136 · belgif/thematic · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Clarity over mandatory entities & fields #136

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.

Sign up for GitHub

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

Jump to bottom
Open
fhalin opened this issue May 8, 2023 · 2 comments
Open

Clarity over mandatory entities & fields #136

fhalin opened this issue May 8, 2023 · 2 comments
Labels
Mobility

Comments

@fhalin
Copy link
fhalin commented May 8, 2023

Currently the spec does not specify which fields are mandatory or not. This can have a huge impact on the upstream data source needed to provide a compliant NETeX feed. Could you clarify?
@GeertThijs
Copy link

In the AP's (timetables, stopplaces, vehiclescheduling) there are multiplicities for all elements (except for the classes as these are only mandatory if they are at the end of a mandatory relation). So I presume that you refer to the VOC . For VOC's indeed there are no multiplicities as they are only the collection of terms used in the AP's and their identification and definition.

@fhalin
Copy link
Author
fhalin commented Jun 9, 2023

Hello @GeertThijs, sorry but I don't understand your answer. How are multiplicities linked to the mandatory nature of fields?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Mobility
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fhalin @MarcBruyland @GeertThijs
0