Re: Use of same name with different case considered harmful

Hear,hear, Chris.
The US Post Office** has so far been silent on #3, but the effect you mention is causing a lot of pain ... most recently last Saturday in Hawaii.
This was a State-Wide alert, broadcast by cell-phones which took 38 terrifying minutes to claw back.
1)  Would it have been better limited to County-Wide ? [County Equivalents also fold into 5 or more digits (0+dd-ddd)].2)  Would it have been better 5 Digit Zip Code-Wide ? [Zip Codes fold with different grouping... (0+ddd-dd)]
3)  Would it have been better if Siri, Alexa, Echo, etc. been involved ? (Web of Things)

nb. ISO and GENC two letter codes likewise fold (0+dd-ddd) with the the first two digits coming from the first letter of the entity short name.

The answer has to be a resounding NO since the terror quickly went Nation, State, Territory, Federal Government, Federal Agency, etc. Wide.
--Gannon




      From: "Little, Chris" <chris.little@metoffice.gov.uk>
 To: "Simon.Cox@csiro.au" <Simon.Cox@csiro.au>; "melvincarvalho@gmail.com" <melvincarvalho@gmail.com> 
Cc: "public-locadd@w3.org" <public-locadd@w3.org>
 Sent: Tuesday, January 16, 2018 1:41 PM
 Subject: RE: Use of same name with different case considered harmful
   
#yiv5802585162 #yiv5802585162 -- _filtered #yiv5802585162 {font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;} _filtered #yiv5802585162 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv5802585162 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv5802585162 {}#yiv5802585162 #yiv5802585162 p.yiv5802585162MsoNormal, #yiv5802585162 li.yiv5802585162MsoNormal, #yiv5802585162 div.yiv5802585162MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;}#yiv5802585162 a:link, #yiv5802585162 span.yiv5802585162MsoHyperlink {color:blue;text-decoration:underline;}#yiv5802585162 a:visited, #yiv5802585162 span.yiv5802585162MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv5802585162 p.yiv5802585162MsoListParagraph, #yiv5802585162 li.yiv5802585162MsoListParagraph, #yiv5802585162 div.yiv5802585162MsoListParagraph {margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt;font-size:12.0pt;}#yiv5802585162 p.yiv5802585162msonormal0, #yiv5802585162 li.yiv5802585162msonormal0, #yiv5802585162 div.yiv5802585162msonormal0 {margin-right:0cm;margin-left:0cm;font-size:12.0pt;}#yiv5802585162 span.yiv5802585162EmailStyle18 {color:#1F497D;}#yiv5802585162 span.yiv5802585162EmailStyle19 {color:#1F497D;}#yiv5802585162 .yiv5802585162MsoChpDefault {font-size:10.0pt;} _filtered #yiv5802585162 {margin:72.0pt 72.0pt 72.0pt 72.0pt;}#yiv5802585162 div.yiv5802585162WordSection1 {}#yiv5802585162 _filtered #yiv5802585162 {} _filtered #yiv5802585162 {} _filtered #yiv5802585162 {} _filtered #yiv5802585162 {} _filtered #yiv5802585162 {} _filtered #yiv5802585162 {} _filtered #yiv5802585162 {} _filtered #yiv5802585162 {} _filtered #yiv5802585162 {} _filtered #yiv5802585162 {}#yiv5802585162 ol {margin-bottom:0cm;}#yiv5802585162 ul {margin-bottom:0cm;}#yiv5802585162 I would like to support Simon in this.    1.      I spend a lot of time reading documents and trying to figure out whether CamelCase differences are meaningful. 2.      Presumably, some URIs may have non-ASCII characters, and many writing systems have not distinguished case at all. E.g. Cyrillic. 3.      Some parts of the world still have legacy telecoms, where text may be folded into 5 bits, though presumably, they are not using the Web; 4.      Many manual input systems automatically capitalise the initial letter, unnoticed by the operator.    Most humans do need some ‘redundancy’ in a message to make it stick.    Chris    From: Simon.Cox@csiro.au [mailto:Simon.Cox@csiro.au]
Sent: Monday, January 08, 2018 9:44 PM
To: melvincarvalho@gmail.com
Cc: public-locadd@w3.org
Subject: RE: Use of same name with different case considered harmful    RDF uses URIs as identifiers, and URIs are strictly case sensitive so it shouldn’t matter. But  some systems (particularly Windows based) ignore case in filenames that are often mapped to URIs … It’s not a rule, and could be argued to be pandering, but another view is that it is merely an avoidable risk. Is also likely to trip people up from time to time in documentation.       From: Melvin Carvalho [mailto:melvincarvalho@gmail.com]
Sent: Monday, 8 January, 2018 18:20
To: Cox, Simon (L&W, Clayton) <Simon.Cox@csiro.au>
Cc: Public LOCADD list <public-locadd@w3.org>
Subject: Re: Use of same name with different case considered harmful          On 8 January 2018 at 07:39, <Simon.Cox@csiro.au> wrote: 
The LOCN vocabulary includes a number of terms in which an RDF property has the same name as an RDF Class, differing only in case [1], e.g. locn:geometry vs. locn:Geometry locn:address vs locn:Address   While strictly OK, this is generally considered risky, since some processing environments fail to distinguish between tokens on the basis of case alone. Modifying the vocabulary to avoid this might be a helpful revision, e.g.   locn:geometry à locn:hasGeometry locn:address à locn:hasAddress 
   Just a lurker here, but this post got my interest We use this pattern sometimes (in other contexts) I thought RDF was case sensitive, is there some tooling that you are aware of, that is not?   
    [1]https://www.w3.org/ns/locn#glance     Simon J D Cox Research Scientist Environmental Informatics CSIRO Land and Water   Esimon.cox@csiro.auT+61 3 9545 2365 M+61 403 302 672   Mail: Private Bag 10, Clayton South, Vic 3169    Visit:Central Reception,Research Way, Clayton, Vic 3168    Deliver:Gate 3, Normanby Road, Clayton, Vic 3168 people.csiro.au/Simon-Cox orcid.org/0000-0002-3884-3420 researchgate.net/profile/Simon_Cox3 github.com/dr-shorthair lov.okfn.org/dataset/lov/agents/Simon%20Cox @dr_shorthair https://xkcd.com/1810/   PLEASE NOTE The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.   Please consider the environment before printing this email.