Just for my understanding, is it theoretically possible to figure out where
all those points are by following the trail forward and backward, i.e. ,
looking for everything that points to or is pointed to by the institution
file - like following all the lines in the Entity Relationship Diagrams?
I am sure there is a way of correctly saying what I am trying to ask here ...
On Sunday 19 February 2006 22:32, Chris Richardson wrote:
Greg;
Thanks for the input, but this namespace and numberspace is for local
development and it is up to them to use and expand as they need. If they
can tie into existiing packages, all the better, especially if they work
with the interface agreements. But the first part is to make it possible
for people to do some of their own problem solving. This is a starting
point, a line in the sand. It is designed to be just a beginning. No body
said it was going to be easy, just possible.
If you know what function points and entry points are needed to be
modified, please identify them and we will see about getting them modified.
----- Original Message -----
From: "Gregory Woodhouse" <[EMAIL PROTECTED]>
To: <hardhats-members@lists.sourceforge.net>
Sent: Sunday, February 19, 2006 6:16 PM
Subject: Re: [Hardhats-members] local file numbers
> On Feb 19, 2006, at 5:51 PM, Chris Richardson wrote:
> > Just as I thought. Thanks, Cameron.
> >
> > Are there other issues that anyone might see about this arrangement?
> > Perhaps Rick can comment.
>
> Although, ZZ* is set aside as a local namespace, so far as I know,
> there is no such thing as a local (meaning unregistered) number
> space. Existing facilities can, of course, use their facility number
> to derive a private (but not unregistered) number space.
> Unfortunately, that is of no use to anyone without an assigned
> institution number. Worse, some packages (such as IFCAP) require an
> assigned station number, and you often cannot even get into the menu
> system without one. But there is no infrastructure to support
> federated management of station numbers, and anything that might be
> developed would almost surely conflict with the INSTITUTION file as
> implemented in VHA (which cannot be modified locally). This is but
> one example of a file that may appear to be something that can be
> modified and administered locally: consider the use of the ICN to
> identify patients or standardization of files like the ITEM MASTER
> (#441). This seems to me to be a rather serious problem, in many
> ways analogous to address exhaustion in IPv4. In the case of IP,
> Classless Interdomain Routing (CIDR) provided a "quick fix" allowing
> the number of bits set aside for addresses (vs. network numbers) to
> vary (that's what the the slash in routing table entries is all
> about). Maybe a CIDR like solution is possible, but it would only be
> a temporary expedient. Expanding the station number to include more
> digits (or noncanonic numbers, as has been suggested) would require a
> LOT of work. It's easy to underestimate the number of utilities,
> options, input transforms, fixed width messages, etc. that would be
> affected. It's a big problem.
>
> ===
> Gregory Woodhouse
> [EMAIL PROTECTED]
>
> "Good acts are like good poems. One may easily get their drift, but
> they are not rationally understood."
> --Albert Einstein
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
--
Nancy Anthracite
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
