-
Notifications
You must be signed in to change notification settings - Fork 39
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
Enhancement=fare-debit Internal restructuring to enable reuse of payment #620
Conversation
Payment details are modularised onto a separate FARE DEBIT element as per TM . This is a "hygiene" prereq for making further transactions and validation additiosn to enable thr ENTUR customer account CR . Shoudl not functionally
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.
ok for me, but lacks an example. Pls provide it
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.
The xxxDebit structure is build, but nowhere applied. Also no example is provided.
@nick-knowles update is needed
@skinkie should I add an example? and what do we do with the not used structure? |
Ask the creator of this pull request to fix it. |
xsd/netex_part_3/part3_salesTransactions/netex_fareDebit_version.xsd
Outdated
Show resolved
Hide resolved
<xsd:annotation> | ||
<xsd:documentation>Elements for OTHER DEBIT</xsd:documentation> | ||
</xsd:annotation> | ||
<xsd:sequence/> |
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.
What happens 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.
TM: A LOG ENTRY recording data about a debiting action for a payment type other than a FARE PRODUCT SALE DEBIT, TRIP DEBIT, OFFENCE DEBIT or BOOKING DEBIT.
<xsd:annotation> | ||
<xsd:documentation>Elements for TRIP DEBIT</xsd:documentation> | ||
</xsd:annotation> | ||
<xsd:sequence/> |
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.
What is this?
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.
from TM: A LOG ENTRY recording data about a debiting action for post-payment for a specific trip.
To be detailed in the doc
<xsd:annotation> | ||
<xsd:documentation>Elements for BOOKING DEBIT</xsd:documentation> | ||
</xsd:annotation> | ||
<xsd:sequence/> |
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.
What is this?
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.
From TM : A LOG ENTRY recording data about a debiting action for a booking fee.
To be detailed in the doc
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 am talking about the empty sequence.
xsd/netex_part_3/part3_salesTransactions/netex_customerPurchasePackage_version.xsd
Outdated
Show resolved
Hide resolved
xsd/netex_part_3/part3_salesTransactions/netex_fareDebit_support.xsd
Outdated
Show resolved
Hide resolved
xsd/netex_part_3/part3_salesTransactions/netex_fareDebit_support.xsd
Outdated
Show resolved
Hide resolved
xsd/netex_part_3/part3_salesTransactions/netex_fareDebit_support.xsd
Outdated
Show resolved
Hide resolved
xsd/netex_part_3/part3_salesTransactions/netex_fareDebit_support.xsd
Outdated
Show resolved
Hide resolved
xsd/netex_part_3/part3_salesTransactions/netex_fareDebit_version.xsd
Outdated
Show resolved
Hide resolved
xsd/netex_part_3/part3_salesTransactions/netex_fareDebit_version.xsd
Outdated
Show resolved
Hide resolved
xsd/netex_part_3/part3_salesTransactions/netex_salesContract_version.xsd
Outdated
Show resolved
Hide resolved
in my opinion, this should go to next |
…on.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
…ePackage_version.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
…rt.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
…rt.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
…rt.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
…rt.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
…on.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
…on.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
…ersion.xsd Co-authored-by: Stefan de Konink <stefan@konink.de>
Payment details are modularised onto a separate FARE DEBIT element as per TM model (Previously they were included in the SALES TRANSACTION package) . This is a small "hygiene" internal restructure prereq for making further transactions and validation additions to enable the ENTUR customer account CR . Should not functionally change anything. At some point a further change could be introduced to SALES TRANSACTION wrap payment details in a debit tag