Text 662, 145 rader
Skriven 2007-02-10 13:53:37 av Mithgol the Webmaster (2:5063/88)
Ärende: [7/11] FidoURL.txt
==========================
* written in FTSC_PUBLIC
* also sent to CU.TALK
* also sent to GANJANET.LOCAL
* also sent to RU.FIDO.WWW
* also sent to RU.FIDONET.TODAY
* also sent to RU.FTN.DEVELOP
* also sent to SU.FIDOTECH
* also sent to TITANIC.BEST

textsection 7 of 11 of file FidoURL.txt
textbegin.section

    7.1.1. The leading slash and the trailing slash
    -+---------------------------------------------

      The leading slash of <object-path> is a mere delimiter between
      <basic-required-part> and <object-path>. If the <object-path>
      part of a URL is empty, its leading slash MUST be ignored by the
      program interpreting the URL. If the <object-path> part of a URL
      is empty, its leading slash MAY be omitted by the author of that
      URL, thus the following URLs are equivalent:

         <scheme>://<basic-required-part>/?<optional-part>

         <scheme>://<basic-required-part>?<optional-part>

      However, the trailing slash of <object-path> has its own value,
      makes some real difference. For example, "example.zip" means
      the archive itself (a file that may be saved or sent, etc.),
      and "example.zip/" means the root directory of that archive
      (a container that may be browsed, updated, etc.)

      The trailing slash of <object-path> MUST NOT be ignored.

    7.1.2. Dealing with unknown containers
    -+------------------------------------

      Sometimes an <object-path> designates an object inside
      such a container that certain Fidonet browsers are not able
      to open by themselves. This MAY happen when the archive format
      is unknown (or is known, but is newer than the supported one).

      If the object is requested as a separate entity (for example,
      its URL is entered in the address line of a Fidonet browser,
      or the user follows a hyperlink specifying that URL),
      the browser MAY inform the user about the unknown container
      encountered, and suggest saving that container for possible
      manual analysis (after all, the user may have unpacker tools
      in his avail that are not yet integrated into a Fidonet browser,
      and may be willing to try them).

      If the requested object is not a separate entity (for example,
      if it is just one of images on a hypertext page), if many such
      objects are requested at the same time and for the same purpose,
      then it would not be wise to flood the user with information
      about each of such obstacles concurrently encountered, and so
      the browser SHOULD follow its standard procedures prescribed for
      the state of error (display a "broken image" icon, or use
      an alternate object or an alternate text where it is provided).

  7.2. "area://" scheme
  -+-------------------

    Echomail is an important and powerful force in Fidonet. Echomail
    is, by definition, a broadcast medium. See echomail specifications
    in FTS-0004.

    An echomail area is a shared base of messages that have common
    areatag (area identifier) and are distributed through Fidonet
    via hierarchical and/or p2p-alike connections between individual
    Fidonet systems (nodes and points).

    Due to the immanent modularity of Fidonet software packages,
    echomail composer and echomail browser can be different programs
    (for example, the latter does not require read/write access to the
    area message base and is able to work through a read-only gate).
    The "echomail:" scheme (defined above) is designed to designate
    an action of a Fidonet echomail composer; the "area://" scheme,
    defined is this section, designates a resource that is located
    in an area message base. These schemes can be handled by different
    software modules, even if they were manufactured independently.

    The area URLs take the form:

    area://<areatag>/<object-path>?<optional-part>

    The character "/" has its literal meaning in the <optional-part>
    of URLs of this scheme. The character "/" has its reserved meaning
    in the required part of URL (<areatag>/<object-path>), playing
    the role of delimiter between parts of the path. If an <areatag>
    contains the character "/" in its literal meaning, the character
    MUST be encoded.

    If an <areatag> corresponds to an echomail area which is not
    available on the system, the URL MAY be treated as equivalent
    to areafix:<areatag> and the user MAY be asked whether he wants
    to subscribe.

    If <object-path> is empty and <optional-part> does not contain
    message-identifying parameters, the area URL designates an area
    as a whole.

    Examples:

       area://Ru.FTN.Develop
       area://Ru.FTN.Winsoft/
       area://FTSC_Public?
       area://Ru.Fidonet.Today/?

    When such a link is used (clicked, followed), an echomail browser
    MAY open a sorted list of echomail messages present in the given
    area, or a threaded list of replies. This depends on user settings
    of the browser.

    If <areatag> is empty, the <object-path> MUST also be empty;
    such URL leads to the list of the available echomail areas,
    also known as the arealist.

    Examples:

       area://
       area:///
       area://?

    7.2.1. Message-identifying optional parameters
    -+--------------------------------------------

      If one of the message-identifying optional parameters is present
      in the <optional-part> of an area URL, then

         area://<areatag>?<optional-part>

      no longer designates the whole message base of the given area,
      but only the message(s) specified by the given value of the
      message-identifying optional parameter(s).

textend.section


With best Fidonet 2.0 regards,
Mithgol the Webmaster.                 [Real nodelisted name: Sergey Sokoloff]

... BETA: Bugs Exist, Try Again.                        (Bugzilla Quip System)
--- Just as the clouds have gone to sleep, Angels can be seen in heaven's keep
 * Origin: Be careful, the paranoid ones are always wathing you!.. (2:5063/88)