Proposed Network Standard Data Pathname syntax (RFC0615)
Original Publication Date: 1974-Mar-01
Included in the Prior Art Database: 2000-Sep-13
Internet Society Requests For Comment (RFCs)
There seems to be an increasing call for a Network Standard Data Pathname (NSDP); that is, a standardized means of referring to a specific location for/of a collection of bits somewhere on the Network.
Network Working Group D. Crocker (UCLA-NMC)
Request for Comments: 615 MAR 74
Standard Data Pathname Syntax
There seems to be an increasing call for a Network Standard Data Pathname
(NSDP); that is, a standardized means of referring to a specific location
for/of a collection of bits somewhere on the Network.
The reasons for a standard or virtual anything have been discussed, at
length, elsewhere and will not be elaborated upon here. Rather than
attack the entire issue of virtual pathnames, I wish only to propose a
standardized SYNTAX for specifying pathnames. Such a standard will be
useful for 1) users who are unfamiliar with a site or who use several
different sites and do not want to have to remember each site's
idiosynchracies, 2) programs accessing data at several other sites, and
The syntax allows the user to specify the necessary network, host,
peripheral device, directory, file, type, and site-specific fields.
Adding other fields, as needed, is expected to be quite simple.
First the BNF:
FILE / TYPE / SITEPARM / N / H / P / D / F /
T / S
acceptable to the object site: For visual
aesthetics and to facilitate human parsing,
character (<, [, (, _),
the complementary right-bracket character
(>, ], ), |).
object site. This is the actual data field
with the file, directory, device (or
2) if the
left-bracket character (<, [, (, _) then its
complementary right-bracket (>, ], ), |).
And some elaboration:
The syntax allows
Case is irrelevant to the syntax, though some sites will care about case
refer to: The single-character keys are abbreviat...