this is a pretty good summary of where docker is at the moment, and I think we need to fix it - ``docker tag`` and ``docker build -t`` are the biggest part of the problem.

Given @shykes intention to merge many image and container operations before 1.0, perhaps now is the time to start this discussion.

in my opinion (at the moment) we should think about changing ``docker build -t`` and ``docker tag`` to ``docker build -name`` (or ``docker build -n``) and replace ``docker tag`` with ``docker name (IMAGE|CONTAINER) NAME``

that then stops the confusion with the ``[REGISTRYHOST/][USERNAME/]NAME[:TAG]`` :TAG portion of the IMAGENAME, brings the command and option name inline with how users use it, and stops us from writing confusing documentation were we claim a tag is a name, except when its a tag.

``Fully Qualified Name`` for both image and container is IMO going to be needed - When I have a fleet of Docker servers booted, I will want to setup a transparent ambassador between a container on host1 and another on host2 - so I can move them when needed...

OH GOSH - and we also need to remember that an image may have more than one ``hostname:port`` - when docker servers push and pull peers (which will aid in transparent container migration).