aboutsummaryrefslogtreecommitdiff
path: root/src/main/resources/mzs/app2mzs.xsd
AgeCommit message (Collapse)AuthorFilesLines
2019-04-08Schema FixesChristof Rabensteiner1-2/+2
2019-04-08Update mzs:DeliveryRequest/Receiver Schema to fit zusemsg needsChristof Rabensteiner1-1/+15
- add choice between Identification and Person/Address - add AdditionalCriteria and PreAdvice not
2019-04-08Update mzs:DeliveryRequest SchemaChristof Rabensteiner1-151/+12
- Remove MZSDreq/Sender/ConfirmationAddress (because its already Available in Sender/{WebserviceURL,EmailAddress}) - Simplify MZSDReq/Receiver (no actual schema change, just refactoring) - Remove XML Payload (because this delivery method does not exist in zusemsg) - Simplify Payload Schema and adapt it to zusemsg:Attachment - Remove DayOfBirthType (because dead code) - Metadata: replace mzs definition of metadata with reference to msg:Metadata. Reason: Both interfaces work the exact same way so there is no reason in not reusing the interface. Using the same interface definitions does not affect the integration effort for app developers, because the msg:metadata changed quite drastically and app developers will need to integrate these changes anyways. The changes in zusemsg:Metadata are so invasive that MOAZS cannot prevent them from propagating into the app2mzs interfaces. A benefit from reusing the msg:MetaData interface is that there will be less types, less duplicate code, less repetition, and therefore cleaner and easier to maintain.
2019-04-05mzs:Sender: Remove ProfileIDChristof Rabensteiner1-28/+23
2019-04-03Add msg:AdditionalCriteria and msg:ConfirmationAddress DRq:SenderChristof Rabensteiner1-1/+3
2019-04-03Add msg:logo to mzs:DRq:SenderChristof Rabensteiner1-1/+3
2019-04-03Change MZS Namespaces (again)Christof Rabensteiner1-2/+2
2019-04-03Remove Version Number in Scheme Folder StructureChristof Rabensteiner1-0/+320