-
Notifications
You must be signed in to change notification settings - Fork 4
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Design of the reference construct
MUST BE DISCUSSEDMust be discussed during the next CWG meetingMust be discussed during the next CWG meetingStatus: Open.#317 In papinet/papiNet-API;Error in schema of query parameter timestamp
MUST BE DISCUSSEDMust be discussed during the next CWG meetingMust be discussed during the next CWG meetingStatus: Open.#316 In papinet/papiNet-API;shipmentStatus in logistics delivery note for version 5.0.0?
MUST BE DISCUSSEDMust be discussed during the next CWG meetingMust be discussed during the next CWG meetingStatus: Open.#315 In papinet/papiNet-API;Update of Rule 2 in papiNet-JSON-Style-Guide.md to specify all HTTP Status Codes to use.
MUST BE DISCUSSEDMust be discussed during the next CWG meetingMust be discussed during the next CWG meetingStatus: Open.#314 In papinet/papiNet-API;Update Rule 10 in papiNet-JSON-Style-Guide.md
MUST BE DISCUSSEDMust be discussed during the next CWG meetingMust be discussed during the next CWG meetingStatus: Open.#313 In papinet/papiNet-API;transportUnitLevel is not required in unitReferences
MUST BE DISCUSSEDMust be discussed during the next CWG meetingMust be discussed during the next CWG meetingStatus: Open.#312 In papinet/papiNet-API;Error in description of actual DateTime properties in version 3.0.0 and 4.0.0
MUST BE DISCUSSEDMust be discussed during the next CWG meetingMust be discussed during the next CWG meetingStatus: Open.#311 In papinet/papiNet-API;AssignedBy for codes and identifiers, e.g. for transport units
MUST BE DISCUSSEDMust be discussed during the next CWG meetingMust be discussed during the next CWG meetingStatus: Open.#310 In papinet/papiNet-API;- Status: Open.#309 In papinet/papiNet-API;
Possibility to add function to create individual schemas based on the yaml?
Done Ready for ReviewThe change is implemented and ready for review.The change is implemented and ready for review.Status: Open.#308 In papinet/papiNet-API;Best practice is to use PUT instead of POST to create a resource, when the client defines the "id": as a UUID
Done Ready for ReviewThe change is implemented and ready for review.The change is implemented and ready for review.Status: Open.#307 In papinet/papiNet-API;Use cases in version 5.0.0
Approved and Ready to implementThe change is approved by CWG and can be implementedThe change is approved by CWG and can be implementedStatus: Open.#306 In papinet/papiNet-API;