{"action":"created","issue":{"url":"https://api.github.com/repos/erasmus-without-paper/ewp-specs-architecture/issues/13","repository_url":"https://api.github.com/repos/erasmus-without-paper/ewp-specs-architecture","labels_url":"https://api.github.com/repos/erasmus-without-paper/ewp-specs-architecture/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/erasmus-without-paper/ewp-specs-architecture/issues/13/comments","events_url":"https://api.github.com/repos/erasmus-without-paper/ewp-specs-architecture/issues/13/events","html_url":"https://github.com/erasmus-without-paper/ewp-specs-architecture/issues/13","id":183253121,"number":13,"title":"Decide on the format of postal addresses","user":{"login":"wrygiel","id":2168535,"avatar_url":"https://avatars.githubusercontent.com/u/2168535?v=3","gravatar_id":"","url":"https://api.github.com/users/wrygiel","html_url":"https://github.com/wrygiel","followers_url":"https://api.github.com/users/wrygiel/followers","following_url":"https://api.github.com/users/wrygiel/following{/other_user}","gists_url":"https://api.github.com/users/wrygiel/gists{/gist_id}","starred_url":"https://api.github.com/users/wrygiel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wrygiel/subscriptions","organizations_url":"https://api.github.com/users/wrygiel/orgs","repos_url":"https://api.github.com/users/wrygiel/repos","events_url":"https://api.github.com/users/wrygiel/events{/privacy}","received_events_url":"https://api.github.com/users/wrygiel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-10-16T07:06:37Z","updated_at":"2016-10-18T09:59:07Z","closed_at":null,"body":"We should decide on the XML Schema for addresses - both physical ones and postal ones.\r\n\r\nWe need a list of solutions to pick from. Everyone is welcome to submit their proposals. **Let's assign numbers to each proposal for easy referral.**\r\n\r\n@erasmus-without-paper/all-members "},"comment":{"url":"https://api.github.com/repos/erasmus-without-paper/ewp-specs-architecture/issues/comments/254462429","html_url":"https://github.com/erasmus-without-paper/ewp-specs-architecture/issues/13#issuecomment-254462429","issue_url":"https://api.github.com/repos/erasmus-without-paper/ewp-specs-architecture/issues/13","id":254462429,"user":{"login":"wrygiel","id":2168535,"avatar_url":"https://avatars.githubusercontent.com/u/2168535?v=3","gravatar_id":"","url":"https://api.github.com/users/wrygiel","html_url":"https://github.com/wrygiel","followers_url":"https://api.github.com/users/wrygiel/followers","following_url":"https://api.github.com/users/wrygiel/following{/other_user}","gists_url":"https://api.github.com/users/wrygiel/gists{/gist_id}","starred_url":"https://api.github.com/users/wrygiel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wrygiel/subscriptions","organizations_url":"https://api.github.com/users/wrygiel/orgs","repos_url":"https://api.github.com/users/wrygiel/repos","events_url":"https://api.github.com/users/wrygiel/events{/privacy}","received_events_url":"https://api.github.com/users/wrygiel/received_events","type":"User","site_admin":false},"created_at":"2016-10-18T09:59:07Z","updated_at":"2016-10-18T09:59:07Z","body":"### Solution 4\r\n\r\nI did some more research. I analyzed the SQL structures of some public databases. It seems that all of them settled on using a single common format. It's quite similar to the format proposed in Solution 2, but a bit more flexible, with 3-4 address lines instead of a single street element (which can be easily combined into a single line, if need be).\r\n\r\nI have built this schema based on all I found (it's just a first version, but the elements won't change, I think):\r\n\r\n```xml\r\n<xs:element name=\"addressLine\" minOccurs=\"0\" maxOccurs=\"4\" type=\"xs:string\">\r\n  <xs:annotation>\r\n    <xs:documentation>\r\n      There are many valid options here. These fields (there can be as much as 4 of\r\n      them) may contain street name, building number, the name of the addressed\r\n      entity (e.g. the name of the faculty, or a person), a post-office box number,\r\n      etc.\r\n\r\n      Server developers SHOULD attempt to provide this data in a form of multiple\r\n      &lt;addressLine&gt; elements, but they are also allowed to have it all in a\r\n      single line (e.g. comma-separated).\r\n\r\n      Client developers MAY combine the lines with commas, if their databases do not\r\n      allow them to hold 4 address lines.\r\n    </xs:documentation>\r\n  </xs:annotation>\r\n</xs:element>\r\n<xs:element name=\"locality\" minOccurs=\"0\" type=\"xs:string\">\r\n  <xs:annotation>\r\n    <xs:documentation>\r\n      The name of the settlement (city/town/village). Both postal and map localities\r\n      are allowed.\r\n\r\n      If this address is supposed to be postal address, then it is recommended to use\r\n      a postal locality here (postal authority often situated in a nearby large town).\r\n      Note however, that a map locality is also acceptable, as the postal code will\r\n      usually resolve any problems here, to allow correct delivery even if the\r\n      official post-locality is not used.\r\n    </xs:documentation>\r\n  </xs:annotation>\r\n</xs:element>\r\n<xs:element name=\"region\" minOccurs=\"0\" type=\"xs:string\">\r\n  <xs:annotation>\r\n    <xs:documentation>\r\n      An optional name of the region (many countries don't use them). Any kind of\r\n      administrative division such as state, province, voivodeship, etc.\r\n    </xs:documentation>\r\n  </xs:annotation>\r\n</xs:element>\r\n<xs:element name=\"postalCode\" minOccurs=\"0\" type=\"xs:string\">\r\n  <xs:annotation>\r\n    <xs:documentation>\r\n      The postal code. This is often (but not always) required if the address is\r\n      supposed to be the postal address. It may include dashes and other formatting\r\n      characters. Note, that in some countries it can be as long as 10 characters.\r\n    </xs:documentation>\r\n  </xs:annotation>\r\n</xs:element>\r\n<xs:element name=\"country\" minOccurs=\"0\" type=\"CountryIsoCode\">\r\n  <xs:annotation>\r\n    <xs:documentation>\r\n      ISO 3166-1 alpha-2 country code.\r\n    </xs:documentation>\r\n  </xs:annotation>\r\n</xs:element>\r\n```\r\n\r\n#### Examples\r\n\r\n```xml\r\n<example1>\r\n  <addressLine>Janina Mincer-Daszkiewicz</addressLine>\r\n  <addressLine>Faculty of Mathematics, Informatics and Mechanics</addressLine>\r\n  <addressLine>Banacha 2</addressLine>\r\n  <locality>Warszawa</locality>\r\n  <postalCode>02-097</postalCode>\r\n  <country>PL</country>\r\n</example1>\r\n\r\n<example2>\r\n  <addressLine>PO Box 42475</addressLine>\r\n  <locality>Houston</locality>\r\n  <region>Texas</region>\r\n  <postalCode>TX 77002</postalCode>\r\n  <country>US</country>\r\n</example2>\r\n```"}}
{"actor":{"display_login":"wrygiel"}}