Skip to content
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

Catalogue Response #702

Closed
AchillesDougalis opened this issue Oct 7, 2024 Discussed in #524 · 2 comments
Closed

Catalogue Response #702

AchillesDougalis opened this issue Oct 7, 2024 Discussed in #524 · 2 comments
Assignees
Labels
module: eCatalogue eCatalogue type: use case Use Case (User story)
Milestone

Comments

@AchillesDougalis
Copy link
Contributor

Discussed in #524

Originally posted by idolum July 3, 2023
As part of the catalogue choreographies defined in prEN 17015-1 by CEN/TC 440/WG 5, a reponse document to a sent catalogue is needed.

User Stories

A catalogue provider sends a catalogue to the catalogue receiver. The catalogue is validated by the catalogue receiver and accepted. The catalogue receiver sends a response to indicated to the catalogue provider that the catalogue was accepted and in operation in the ordering system on the buying side.

Another catalogue provider sends a catalogue to the catalogue receiver. The catalogue is validated by the catalogue receiver and was rejected. To reaons why the catalogue was rejected is sent in the response. The reasons for the rejection

  1. are provided for the whole catalgue
  2. are provided for some of the catalogue lines

Examples

Proposal

Based on the current draft and Peppol:

image

@AchillesDougalis
Copy link
Contributor Author

AchillesDougalis commented Oct 7, 2024

check comments
#453 (comment)
#453 (comment)

To update descriptions of the epo-cat concepts accordingly.

related to #496

@andreea-pasare andreea-pasare added this to the 5.0.0 milestone Dec 13, 2024
@andreea-pasare
Copy link
Collaborator

Closing issue since the definition alignment for epo-ord:hasResponseDescription is tracked under a different issue: #730

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module: eCatalogue eCatalogue type: use case Use Case (User story)
Projects
None yet
Development

No branches or pull requests

2 participants