- ...System
-
This material is based upon work supported by the U.S. Army Research Office
under grant number DAAH04-95-1-0595
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...octets.
- Although LIFNs were intended to
refer to files, it should also be possible to use LIFNs to refer to
replicated services that provide the same results at different
locations, but that change over time. Such an extension of LIFNs is
a subject for future work.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...domain.
- If this is a modification to the
existing URN, the publication tool also ensures that that particular
catalog server has a current copy of the description. This discipline
is followed any time a catalog server is updated, to ensure
single-copy serialization of resource descriptions.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...expired.
- Note that 8#8 for a LIFN to URL
binding is no indication of the expected lifetime of the resource
itself, and is only a lower bound of the expected time during which
the resource is expected to be available at that location.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.