RE: Use of same name with different case considered harmful

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<mailto:Simon.Cox@csiro.au>>
Cc: Public LOCADD list <public-locadd@w3.org<mailto: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<mailto: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<http://www.csiro.au/Research/LWF>

E simon.cox@csiro.au<mailto:simon.cox@csiro.au> T +61 3 9545 2365<tel:+61%203%209545%202365> M +61 403 302 672<tel:+61%20403%20302%20672>
   Mail: Private Bag 10, Clayton South, Vic 3169
   Visit: Central Reception, Research Way, Clayton, Vic 3168
   Deliver: Gate 3, Normanby Road, Clayton, Vic<https://maps.google.com/?q=3,+Normanby+Road,+Clayton,+Vic&entry=gmail&source=g> 3168
people.csiro.au/Simon-Cox<http://people.csiro.au/Simon-Cox>
orcid.org/0000-0002-3884-3420<http://orcid.org/0000-0002-3884-3420>
researchgate.net/profile/Simon_Cox3<https://www.researchgate.net/profile/Simon_Cox3>
github.com/dr-shorthair<https://github.com/dr-shorthair>
lov.okfn.org/dataset/lov/agents/Simon%20Cox<http://lov.okfn.org/dataset/lov/agents/Simon%20Cox>
@dr_shorthair<https://twitter.com/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.