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
Users/aedler/appendix de cash register integration patches #146
Users/aedler/appendix de cash register integration patches #146
Conversation
@@ -1,3 +1,3 @@ | |||
# Appendix: DE - KassSichV | |||
|
|||
This appendix expands on the information provided in the General Part by adding details specific to the German market. This additional information is provided only where applicable. The remaining chapters, for which there is no additional information required, were omitted. | |||
This appendix expands on the General Part's information by adding details specific to the German market. This additional information is provided only where applicable. The remaining chapters, for which there is no further information required, were omitted. |
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 liked it better the way it was before :D so information provided in the General Part section.
doc/appendix-de-kassensichv/cash-register-integration/cash-register-integration.md
Outdated
Show resolved
Hide resolved
doc/appendix-de-kassensichv/cash-register-integration/cash-register-integration.md
Outdated
Show resolved
Hide resolved
|
||
### Receipt Creation Process | ||
|
||
This chapter describes the general process of creating receipts with fiskaltrust.Middleware and its workflow, in accordance with the German law. It requires to give a scope to an ongoing action over time. This scope is named a transaction. Calls to fiskaltrust.Middleware are processed just in time and cannot be async over multiple minutes. Therefore and in accordance with German law, a single call is maybe not able to scope a complete transaction. To solve this, multiple calls are used, scoping the same transaction. | ||
This chapter describes the general process of creating receipts with fiskaltrust.Middleware and its workflow, following German law. It requires to give a scope to an ongoing action over time. This scope is named a transaction. Calls to fiskaltrust.Middleware are processed just in time and cannot be async over multiple minutes. Therefore and in accordance with German law, a single call is maybe not able to scope a complete transaction. To solve this, multiple calls are used, scoping the same transaction. |
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.
This scope is named a transaction. Calls to fiskaltrust.Middleware are processed just in time and cannot be async over multiple minutes. >> I don understand, the name of the scope described is "transaction"?.
The part over multiple minutes is not very clear to me either. It meant that they cannot be processed asynchronously? If so, the "async over multiple minutes" could be replaced with "cannot be processed asynchronously". besides, async is not a verb or an adjective!
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 also do not understand this part...
No description provided.