@finbheara/domain 0.34.0 → 0.35.0

package/README.md

@@ -133,15 +133,21 @@ geocode("Prague", { near: "RCCEA", declared: true }).isPlace();
                                  // no namesake town is read
 geocode("Fife").isPlace();       // false: a town of Washington, and a council area
                                  // of Scotland
+geocode("Prague").isPlace();     // false: a town of Oklahoma, and the capital of
+                                 // Czechia
+geocode("Prague, Oklahoma").pl3; // "USA-OK/prague"
 ```
 
 The layer reads a bare town by its name alone, so it reads one only where nothing contradicts
 it. A context (a `country` or `near`, read by the store, never as a town of the layer) that
 reads to ONE place which neither holds the town nor shares its country stops the layer: `Prague`
 near `RCCEA` and `Whitecross` under `Ireland` and `Ulster` read nothing. A context the store
-reads nothing for, or reads as several places, stops nothing, so with no context
-`geocode("Prague")` is still Prague, Oklahoma. A town named like a GeoNames admin2 area of those
-six countries that does not hold it (`Fife`) reads only where a context places it. A print with a
+reads nothing for, or reads as several places, stops nothing. A town named like a GeoNames admin2
+area of those six countries that does not hold it (`Fife`) reads only where a qualifier or a
+context places it. So does a town named like a capital or a major city elsewhere (a `cities500`
+place outside the six countries that is a capital or holds a million people, and is more populous
+than the town): bare `Prague` and `Copenhagen` read nothing, where they would read the towns of
+Oklahoma and New York, and `Prague` in a USA context is the Oklahoma town. A print with a
 qualifier (`Yonkers, NY`) is never stopped: the context never overrules the print.
 
 A `Place` is one of four arms: `resolved`, `plural` (a print naming more than one place),