-
Notifications
You must be signed in to change notification settings - Fork 11
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.
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
definitions added to all requests and responses based on TM #413
Conversation
OJP/OJP_Requests.xsd
Outdated
<xs:element name="OJPFareRequest" type="OJPFareRequestStructure" substitutionGroup="siri:AbstractFunctionalServiceRequest"/> | ||
<xs:element name="OJPFareRequest" type="OJPFareRequestStructure" substitutionGroup="siri:AbstractFunctionalServiceRequest"> | ||
<xs:annotation> | ||
<xs:documentation>This service provides general, stop-specific and trip-specific fare information. This service implements PI Stop Fare Request, PI FQ Fare Product Request, PI FQ Single Trip Fare Request from TM6.</xs:documentation> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I want to know what "FQ" is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh my....
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or make it "TM 6" here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
OJP/OJP_Requests.xsd
Outdated
<xs:annotation> | ||
<xs:documentation>The Location Information service comprises the following four base functions: | ||
matching text input against possible origin and destination locations, retrieval of all location objects (bunch delivery), geographical context service that provides location objects within a bounding box, reverse address resolution service that delivers the nearest address for a given coordinate. | ||
By means of abstraction these functions are assembled within one single service – the Location Information service. This way, even more possible applications have arisen, such as: finding the nearest stops/stations for a given coordinate, matching text input against the names of locations near a given coordinate. This service implements PI QR Location Request from TM 6.</xs:documentation> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QR?
TM 6 -> TM6? (consistency)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me, having the definitions only in the requests would be sufficient, and it would easen maintenance.
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
Co-authored-by: trurlurl <[email protected]>
12225db
to
2b50f47
Compare
This just seems to have been missed when resolving conversations... Co-authored-by: Matthias Günter <[email protected]>
This just seems to have been missed when resolving conversations...
fixes #405