URIs have been known by many names: WWW addresses, Universal Document Identifiers, Universal Resource Identifiers , and finally the combination of Uniform Resource Locators (URL) and Names (URN). As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify -- via name, location, or any other characteristic -- a resource.

When more than one remote path is specified, each directory in the remote path corresponds, one-for-one, with a local directory subordinate to the local path. Multiple remote paths can include the same or different domains and protocols.

For example, assuming the following remote tree structure:

   Baseball
     |
     *-- American
     |    |
     |    *-- Red Sox
     |    |    |
     |    |    *-- Pawtucket
     |    |    |
     |    |    *-- Trenton
     |    |
     |    *-- Yankees
     |         |
     |         *-- Columbus
     |         |
     |         *-- Norwich
     |
     *-- National
          |
          *-- Mets
          |    |
          |    *-- Norfolk
          |    |
          |    *-- Binghampton
          |
          *-- Dodgers
               |
               *-- Albuquerque
               |
               *-- San Antonio
   

Enterprise enabled versions of WebMaven could specify remote path values of Baseball/American/Red Sox  and Baseball/National/Dodgers.  and a local path of MLB  which would result in the following local tree structure on the local hard drive:

   MLB
    |
    *-- American
    |    |
    |    *-- Red Sox
    |         |
    |         *-- Pawtucket
    |         |
    |         *-- Trenton
    |
    *-- National
         |
         *-- Dodgers
              |
              *-- Albuquerque
              |
              *-- San Antonio