********************************************************************** FGHI FIDONET GLOBAL HYPERTEXT INTERCHANGE ********************************************************************** Status: draft Revision: 0.2 Title: FGHI URL, the set of Uniform Resource Locators for Fidonet objects and services Author: Mithgol the Webmaster (Sergey Sokoloff, 2:5063/88) Special thanks to: Shannar (Boris Kassal, 2:463/587) Trooper (Alexey Bezugly, 2:5030/1520.9) Revision Date: 06 Nov 2006 -+-------------------------------------------------------------------- Contents: 1. Status of this document 2. Introduction 3. Key words to indicate requirement levels 4. Reserved section 5. General Fidonet URL syntax 5.1. The main parts of URLs 5.1.1. Conformance note 5.1.2. Delimiter guidelines 5.2. URL character encoding 5.2.1. Encoding of original characters 5.2.2. Encoding of octets 5.2.2.1. No corresponding graphic 7-bit character 5.2.2.2. Unsafe characters 5.2.2.3. Reserved characters 5.2.2.4. The plus ("+") and the encoding of white spaces 5.2.2.4.1. Specificity note 5.2.2.4.2. Internet practice note 5.3. Parsing the scheme-specific part of URL 5.3.1. Dealing with inappropriate reserved characters 6. Fidonet URL schemes designating actions 6.1. "netmail:" scheme 6.1.1. Optional parameter "to" 6.1.2. Optional parameter "subject" 6.1.3. Optional parameter "subj" 6.1.4. Optional parameter "from" 6.1.5. Optional parameter "body" 6.2. "areafix:" scheme 6.2.1. Optional parameter "uplink" 6.2.2. Optional parameters "unsubscribe" and "leave" 6.2.3. Future optional parameters 6.2.4. Relative "areafix:" URLs 6.3. "echomail:" scheme 6.3.1. Optional parameter "to" 6.3.2. Optional parameter "subject" 6.3.3. Optional parameter "subj" 6.3.4. Optional parameter "from" 6.3.5. Optional parameter "body" 7. Fidonet URL schemes designating objects 7.1. The <object-path> part of URL. Possible forms of the path 7.1.1. The leading slash and the trailing slash 7.1.2. Dealing with unknown containers 7.2. "area://" scheme 7.2.1. Message-identifying optional parameters 7.2.1.1. Optional parameter "msgid" 7.2.1.2. Optional parameter "mid" 7.2.1.3. Future message-identifying optional parameters 7.2.2. Encoded objects within echomail messages 7.2.2.1. Names of encoded objects 7.2.2.2. How the designated object is determined 7.2.2.2.1. Possible applications 7.3. "faqserv://" scheme 7.3.1. Optional parameter "bot" 7.3.2. Future optional parameters 7.4. "fecho://" scheme 7.5. "freq://" scheme 7.5.1. Future optional parameters -+--------------------------------------------------------------------
1. Status of this document -+------------------------
This document is a draft of a Fidonet Standards Proposal (FSP).
This document specifies an optional Fidonet standard that can be used both in the Fidonet community and in the Web, and requests discussion and suggestions for improvements.
Implementation of the protocols defined in this document is not mandatory, but all implementations of these protocols are expected to adhere to this standard.
Distribution of this document is unlimited, provided that its text is not altered without notice.
2. Introduction -+-------------
This document specifies some Fidonet schemes of Uniform Resource Locators (URL), providing both syntax and semantics of formalized information for location and access of resources and services via Fidonet.
It is designed to conform with the specifications of RFC 1738, so hyperlinks specified according to this document could be used both in Fidonet (echomail, netmail) and in the traditional HTML hypertext environment of the Web and Internet e-mail.
Besides its independent significance, this document will serve as the first and the most basic part of FGHI (pronounced 'fig-high', stands for 'Fidonet Global Hypertext Interchange') -- that is future hypertext automation of some currently manual Fidonet operations, delivery and browsing of HTML-alike illustrated hypermedia over the traditional set of echomail and netmail plain-text connections, and probably some other elements of hypertext-over-Fido networking.
3. Key words to indicate requirement levels -+-----------------------------------------
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in FTA-1006 (based on RFC 2119).
4. Reserved section -+-----------------
This section of the document is reserved for future use.
5. General Fidonet URL syntax -+---------------------------
Just as there are many different types of Fido objects and services, there are several URL schemes for describing the location of such resources.
The generic syntax for URLs provides a framework for new schemes to be established using protocols other than those defined in this document.
URLs are used to 'locate' resources, by providing an abstract identification of the resource location. Having located a resource, a Fidonet system may perform a variety of operations on the resource (as might be characterized by such words as 'access', 'subscribe', 'unsubscribe', 'send', 'rescan', 'find attributes').
5.1. The main parts of URLs -+-------------------------
In general, Fidonet URLs are written as follows:
<scheme>:<scheme-specific-part>
Any URL contains the name of the scheme being used (<scheme>) followed by a colon and then a string (the <scheme-specific-part>) whose interpretation depends on the scheme.
Scheme names consist of a sequence of characters. The lower case
Пока!
--- Расслабься, pазум отвоpи, чуй Фидонет тебя внутpи от Магадана до Твеpи... * Origin: ── А остальное?... ── А остальное карбиды вольфрама!!.. (2:5063/88)
