= Сообщение: 2488 из 3030 =================================== GANJANET.LOCAL = От : Mithgol the Webmaster 2:5063/88 14 Oct 07 00:32:30 Кому : All 14 Oct 07 00:32:30 Тема : [6/11] FidoURL.txt FGHI : area://GANJANET.LOCAL?msgid=2:5063/88+47112bdf На : area://GANJANET.LOCAL?msgid=2:5063/88+47112b7f = Кодировка сообщения определена как: CP866 ================================== ============================================================================== * изначально написано в эхоконференцию FTSC_Public * также было отослано в эхоконференцию GanjaNet.Local * также было отослано в эхоконференцию Ru.Fido.WWW * также было отослано в эхоконференцию Ru.FTN.Develop * также было отослано в эхоконференцию SU.FidoTech * также было отослано в эхоконференцию Titanic.Best
textsection 6 of 11 of file FidoURL.txt textbegin.section
Any of the six values (year, month, day, hour, minute and/or second) MAY be empty in this form of the filter; it means that the corresponding part of the DateTime of the message is not checked. The adjacent separators ("/", "T", ":") MAY also be skipped; however, to maintain some difference between the appearance of two-digit values of <Month>, <Day>, <Hour>, <Minute> and <Second>, the following rules are established.
Each of the separators between the two non-empty adjacent values MUST be present. (It's obvious, but still worth mentioning anyway.)
If the <Second> value is not empty, the preceding colons (":") MUST be present.
The number of digits and the meaning of the six values are the same as for the single moment (see section 7.2.1.2.1).
A message from the initial message set appears in the filtered set (defined by the given upper limit) if and only if the message's date and time value is not greater than the date and time value given by the filter. All the six values of message's date and time (year, month, day, hour, minute and second) are checked in the following order:
1) Message's year is compared with filter's year. If message's year is greater than filter's year, the message MUST NOT appear in the filtered set. If message's year is lesser than filter's year, the message MUST appear in the filtered set. If message's year is equal to the filter's year, proceed to the next step.
2) Message's month is compared with filter's month. If message's month is greater than filter's month, the message MUST NOT appear in the filtered set. If message's month is lesser than filter's month, the message MUST appear in the filtered set. If message's month is equal to the filter's month, proceed to the next step.
3) Message's day is compared with filter's day. If message's day is greater than filter's day, the message MUST NOT appear in the filtered set. If message's day is lesser than filter's day, the message MUST appear in the filtered set. If message's day is equal to the filter's day, proceed to the next step.
4) Message's hour is compared with filter's hour. If message's hour is greater than filter's hour, the message MUST NOT appear in the filtered set. If message's hour is lesser than filter's hour, the message MUST appear in the filtered set. If message's hour is equal to the filter's hour, proceed to the next step.
5) Message's minute is compared with filter's minute. If message's minute is greater than filter's minute, the message MUST NOT appear in the filtered set. If message's minute is lesser than filter's minute, the message MUST appear in the filtered set. If message's minute is equal to the filter's minute, proceed to the next step.
6) Message's second is compared with filter's second. If message's second is greater than filter's second, the message MUST NOT appear in the filtered set. If message's second is lesser or equal to the filter's second, the message MUST appear in the filtered set.
The first step of the check, as well as several next steps, MAY be skipped if the corresponding leftmost values are empty (see the next subsection).
Unlike in the single moment form, the values of the upper limit form of a "time" filter MAY NOT be empty in arbitrary order; however, the leftmost values MAY be emptied from left to right, and the rightmost values MAY be emptied from right to left.
The <Year> value MAY be empty, and in that case the first step of the above checking MUST be skipped, as if message's year and filter's year were equal.
If the <Year> value is empty, the <Month> value MAY also be empty, and in that case the second step of the above checking MUST also be skipped, as if message's month and filter's month were equal.
If the <Year> and <Month> values are empty, the <Day> value MAY also be empty, and in that case the third step of the above checking MUST also be skipped, as if message's day and filter's day were equal.
If the <Year> and <Month> and <Day> values are empty, the <Hour> value MAY also be empty, and in that case the fourth step of the above checking MUST also be skipped, as if message's hour and filter's hour were equal.
If the <Year> and <Month> and <Day> and <Hour> values are empty, the <Minute> value MAY also be empty, and in that case the fifth step of the above checking MUST also be skipped, as if message's minute and filter's minute were equal.
To find out whether a separator ("/", or "T", or ":") MAY be skipped, consult the subsection 7.2.1.2.1.1: the rules on that matter are the same here.
This URL designates the messages that were written (in Ru.FTN.Develop echomail area) either before the 18th day of any month in any year, or not after 15:56:54 of the 18th day.
The <Second> value MAY be empty, and in that case the <Second> value is assumed to be 60.
If the <Second> value is empty, the <Minute> value MAY also be empty, and in that case the <Minute>:<Second> value is assumed to be 59:60.
If the <Second> and <Minute> values are empty, the <Hour> value MAY also be empty, and in that case the <Hour>:<Minute>:<Second> value is assumed to be 23:59:60.
If the <Second> and <Minute> and <Hour> values are empty, the <Day> value MAY also be empty, and in that case the <Day>T<Hour>:<Minute>:<Second> value is assumed to be 31T23:59:60.
If the <Second> and <Minute> and <Hour> and <Day> values are empty, the <Month> value MAY also be empty, and in that case the <Month>/<Day>T<Hour>:<Minute>:<Second> value is assumed to be 12/31T23:59:60.
None of the above assumed values fail the corresponding steps of the checking described above; the corresponding steps SHOULD be just skipped if the rightmost values are empty: if such a step is reached after the previous steps, then the tested message MUST appear is the filtered set.
The leftmost values and the rightmost values MAY be empty simultaneously; however, some non-empty values (just one, or more) MUST appear in this form of the filter.
To find out whether a separator ("/", or "T", or ":") MAY be skipped, consult the subsection 7.2.1.2.1.1: the rules on that matter are the same here.
This URL designates the messages that were written (in Ru.FTN.Develop echomail area) before the summer in any year. It is equivalent to the following form:
The number of digits and the meaning of the six values are the same as for the single moment (see section 7.2.1.2.1).
A message from the initial message set appears in the filtered set (defined by the given lower limit) if and only if the message's date and time value is not lesser than the date and time value given by the filter. All the six values of message's date and time (year, month, day, hour, minute and second) are checked in the following order:
1) Message's year is compared with filter's year. If message's year is greater than filter's year, the message MUST appear in the filtered set. If message's year is lesser than filter's year, the message MUST NOT appear in the filtered set. If message's year is equal to the filter's year, proceed to the next step.
2) Message's month is compared with filter's month. If message's month is greater than filter's month, the message MUST appear in the filtered set. If message's month is lesser than filter's month, the message MUST NOT appear in the filtered set. If message's month is equal to the filter's month, proceed to the next step.
3) Message's day is compared with filter's day. If message's day is greater than filter's day, the message MUST appear in the filtered set. If message's day is lesser than filter's day, the message MUST NOT appear in the filtered set. If message's day is equal to the filter's day, proceed to the next step.
4) Message's hour is compared with filter's hour. If message's hour is greater than filter's hour, the message MUST appear in the filtered set. If message's hour is lesser than filter's hour, the message MUST NOT appear in the filtered set. If message's hour is equal to the filter's hour, proceed to the next step.
5) Message's minute is compared with filter's minute. If message's minute is greater than filter's minute, the message MUST appear in the filtered set. If message's minute is lesser than filter's minute, the message MUST NOT appear in the filtered set. If message's minute is equal to the filter's minute, proceed to the next step.
6) Message's second is compared with filter's second. If message's second is lesser than filter's second, the message MUST NOT appear in the filtered set. If message's second is greater or equal to the filter's second, the message MUST appear in the filtered set.
The first step of the check, as well as several next steps, MAY be skipped if the corresponding leftmost values are empty (see the next subsection).
Unlike in the single moment form, the values of the lower limit form of a "time" filter MAY NOT be empty in arbitrary order; however, the leftmost values MAY be emptied from left to right, and the rightmost values MAY be emptied from right to left.
textend.section
With best Fidonet 2.0 regards, Mithgol the Webmaster. [Real nodelisted name: Sergey Sokoloff]
... 2. My ventilation ducts will be too small to crawl through. --- Come with me in the twilight of a summer night for a while... .hack//SIGN * Origin: Be careful, the paranoid ones are always wathing you!.. (2:5063/88)
