Your browser does not appear to support JavaScript. You may want to try one of the following:
You may want to try one of the following:
If the above does not work, try reloading the page yourself. Note that you will lose any unsaved changes:
shift
control
Show details
Hide details
This form has to be reloaded. This most likely happened because your session has expired, which might take to the login page. (If you think that you shouldn't see this message and that the problem persists, please contact support.)
In "epSOS_D3.9.1_Appendix_B1_B2_Implementation_v1.4_20110725.pdf" it would appear that addresses are overstated and suffer from some copy/paste problems. You are currently required to either state no address parts or every single mentioned address part with either a value or a nullFlavor (not stated which nullFlavor). Also every address part may appear 1..* R, including city, state, and country. This leads to fragments like:
<addr use="H"> <state nullFlavor="NI"/> <city>MILANO</city> <country>IT</country> <state>ZH</state> <city>ROTTERDAM</city> <country>NL</country> <postalCode nullFlavor="UNK"/> </addr>
I.e. multiple types of NULL and multiple colliding address parts. What is the reason behind this? Any addr specification we have encountered in any context has said that unknown address(parts/es) should just be omitted, and with the exception of streetAddressLine no other parts should be use more than once.