Qname and Vname

Food for thought

I am somewhat concerned about Qnames, and their relation 
to what I am now calling Vnames in MKR.  Initially, I
had thought that Qname and Vname would be the same.

For the meaning of Qname and Vname, see my comments at 
beginning of Qname.java. (I have not yet changed the program.)

    http://rhm.cdepot.net/java/Qname.java

I hope you can understand my somewhat cryptic notation.
In a nutshell: 
MKR allows blanks (names are phrases instead of single words),
doesn't allow "#" because it denotes a comment (but now I have 
CommentMode=cyc for CycL constants whose names begin with "#$"),
and MKR uses "\" to denote walking up the hierarchy; 
URIs don't allow blanks and "\", and URIs use "#" for fragments.

Example names 
(hierarchy root is "existent" alias "Resource" alias "Thing")

view name: philosopher
base name: man
root name: /entity/ANIMAL/man
class name: man\ANIMAL\entity\

view name: feminist
base name: man
root name: /entity/ANIMAL/person/man
class name: man\person\ANIMAL\entity\

view name: UNIX
base name: bin
root name: /usr/local/bin
class name bin\local\usr\

My basic philosophy for local names is 
(0) Local names are unambiguous (unique) within a context.
(1) Don't use view name qualifier within a context, 
unless you must reference an individual or concept from 
another context which has the same local name.
(2) Use base name as the local name wherever possible.
Use view name to disambiguate different English word 
senses, which naturally belong in different contexts.
(3) Use root name when necessary, as in UNIX/Windows 
file systems

If you start merging contexts and dropping your context
(view) name, then different English word senses move 
from case (2) to case (3).


Dick McCullough
knowledge := man do identify od existent done;
knowledge haspart proposition list;