documentable usage of specific domains

February 14, 2017

edited April 26, 2017

documentable usage of specific domains:

domain name is made up of a series of character strings (called "labels") separated by dots. The right-most label in a domain name is referred to as its "top-level domain" (TLD)

A 'Top level expansion^{^3}, follows a

unix philosophy name system. And, a

Plan 9 Mounting table (which is,):

one mount table per process group where each process is/? only has access to itself. And the operations of the parent and child are not visible and each process has its own private namespace, and does not inherit open files from the parent.

(I/O) input/output of a child process can be captured and share open files with the parent runnig the child in encapsulated server.-

Like CSS, domains have specificity (increasing moving left to right and decreasing reading from right to left).

DNS [RFC-1035, REC-1034]  The DNS system is a schema "of [Mnemonic]^{^3} labels (of at most 63 characters) separated by dots"^{^2}.  "... [A] hierarchical name space and pathnames with components separated by dots. Like [any] postal address, but unlike most computer-related naming hierarchies, DNS puts the highest level domain at the end..." (page 87)

Thus, the root of the DNS is an empty name so all tld designations end in dot (seen in DNS records)

Note: modifications in the DNS system creates a type of traffic: the global server distribution (described on page 87-88)

In JavaScript one property accessor is called dot notation; the syntax is object.property. I propose for this discussion - we use /refer to the 'last' or rightmost domain label (TLD) as a property value of the dot object.
So, for the domain person.computer person is the object, computer is the value of a property of person.

As JaveScript syntax governs, these property values can be changed:
get = object.property;
object.property = set;