Anthony G. Atkielski wrote:
Michael Mealling writes:
As the result of a service lookup they only need something that
identifies the class and subclass of the service the URI is an
identifier for...
What's wrong with "http" at the front, and/or a port number at the
back?
Those are network concepts. The "service" I'm talking about has to do
with the task the user is actually attempting to accomplish.
http://foo.com:1235/bla.php
Tells me nothing about whether I can use that for the "I want the
current weather report" service or if its a DAV entry point for doing
collaborative document management....
That's my last one on this thread. I'm not in this business anymore....
-MM
--
Michael Mealling Masten Space Systems, Inc.
VP Business Development 473 Sapena Ct.
Office: +1-678-581-9656 Suite 23
Cell: +1-678-640-6884 Santa Clara, CA 95054
http://masten-space.com/
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf