aboutsummaryrefslogtreecommitdiff
path: root/src/main/resources/mzs/mzs_mypersondata_en.xsd
AgeCommit message (Collapse)AuthorFilesLines
2019-05-08WIP delivery request validationChristof Rabensteiner1-1/+0
2019-05-08Implement Pipeline Flow and mzs2msg ConversionChristof Rabensteiner1-9/+0
- Implement and test conversion from mzs:DeliveryRequest to msg:DeliveryRequest with the "convert-pojos-by-hand"-strategy. Reason: The chosen strategy benefits from JAXB's strong typing, which is useful in this scenario: Differences between msg and mzs are nuanced and easy to overlook. The chosen strategy is, unfortunately, verbose and could become expensive to maintain. - Update SameThreadDeliveryPipeline: Integrate tnvz query, conversion, and msg query. - Add MsgClient stub. tnvz: - Change TnvzClient stub interface. - Implement mimetype mismatch check from tnvz Response. - Put p:Identification from tnvz response into msg:DeliveryRequest. MZS Schema changes: - Replace DeliveryRequest/Sender/Person with CorporateBody (because thats the only sender that is allowed by zusemsg) and add a SenderProfile choice. - Add ID Attribute to DeliveryRequest/Sender because msg/DeliveryRequest/Sender/AbstractSenderPersonType also has an id attribute. - Remove PersonDataType because it's dead code.
2019-04-09Propagate changes of zusemsg2.0.c into mzsChristof Rabensteiner1-16/+2
- Add Target to CorporateBodyType - Remove Authority - make DateOfBirth optional
2019-04-08Update mzs:DeliveryRequest SchemaChristof Rabensteiner1-12/+0
- 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-05Schema changesChristof Rabensteiner1-1/+6
- Add MessegerService, make InternetAddressType url mandatory
2019-04-05Add PostalAddress TypeChristof Rabensteiner1-0/+10
2019-04-05Remove Country Code RestrictionChristof Rabensteiner1-0/+5
2019-04-05Remove Country Code RestrictionChristof Rabensteiner1-6/+1
2019-04-05Remove AnyAttribute from AbstractAddressTypeChristof Rabensteiner1-1/+0
2019-04-05Remove AnyAttribute from AbstractPersonTypeChristof Rabensteiner1-1/+0
2019-04-05Whitespace FixChristof Rabensteiner1-4/+4
2019-04-05PersonName: Add AffixChristof Rabensteiner1-0/+33
2019-04-03Make Corporate/FullPerson MandatoryChristof Rabensteiner1-1/+1
- Reason: mandatory in zusemsg2.0.0
2019-04-03Make PhysicalPerson Child Nodes MandatoryChristof Rabensteiner1-2/+2
- Name and DateOfBirth - Reason: They are Mandatory in zusemsg2.0.0
2019-04-03Make AbstractPersonType abstractChristof Rabensteiner1-1/+1
- such that clients don't start instantiating AbstractPersons
2019-04-03Add msg:Authority and aux types to mzs_mypersondata schemeChristof Rabensteiner1-10/+32
- Aux types: msg:FullName, msg:Target, msg:Organization
2019-04-03Change MZS Namespaces (again)Christof Rabensteiner1-2/+2
2019-04-03Remove Version Number in Scheme Folder StructureChristof Rabensteiner1-0/+266
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-26 20:07:55 +0000