Cart
[Home] [By Thread] [By Date] [Recent Entries]
On Fri, 2025-05-02 at 12:07 +0000, Michael B Allen ioplex@xxxxxxxxx wrote:
On 02/05/2025 18:33, Liam R. E. Quin liam@xxxxxxxxxxxxxxxx wrote: A good rule of thumb for document-oriented information in XML is <rant> By that rule, it should be <address number="123" street="Main Street" city="Townville" state="PA"/> :-) IMNSHO never use abbreviations like St, Rd, Ave, etc because of the risk of misinterpretation in international contexts, eg St Margaret's St Rd Randall Rd The general rule is that an address can just be an unmarked string. You MAY try to enfield it for your own convenience, but you have to be prepared to fail: most of the world does NOT have "street/city/zip" format. Those of you over a certain age :-) may recognise the "townland/locality/postal town/county" rural format common in the UK and Ireland pre-postcode, (and possibly the USA pre-zip) eg Ceann Mha\xED, Barley Cove, Goleen, County Cork If the current ultra-smart, AI-backed, geolocational, field-based form cannot handle addresses outside the "street/city/zip" format, then it's basically useless. </rant> On 14/05/2025 11:49, Tony Graham tgraham@xxxxxxxxxxxxx wrote: Let's suppose you have a town on the border between Germany and Poland, and you need to give both names for it in the address, marking each with its language using xml:lang. You cannot do that with attributes. I think TEI provides for multiple parallel addresses for this reason. I once lived at '103 White Village, 2-20-6 Kasugachou' and 'C#BBC#BB/C#BB$C#BBC#BB C#BB,C#BBC#BB8103 C&BB%C&BB%C'BB:2-20-6' (and 'C&BB%C&BB%C'BB:2-20-6-103'), IIRC. Amen Peter
|
