Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции FTSC_PUBLIC
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции FTSC_PUBLIC с датами от 13 Sep 13 18:57:24 до 01 Apr 24 01:17:44, всего сообщений: 7124
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 2251 из 7124 ====================================== FTSC_PUBLIC =
От   : Nicholas Boel                    1:154/10           27 Jan 17 15:02:14
Кому : Wilfred van Velzen                                  27 Jan 17 15:02:14
Тема : FSP-1040.001 Draft #3
FGHI : area://FTSC_PUBLIC?msgid=1:154/10+588bb77e
На   : area://FTSC_PUBLIC?msgid=2:280/464+588babee
= Кодировка сообщения определена как: UTF-8 ==================================
==============================================================================
Hello Wilfred,

On Fri Jan 27 2017 21:08:34, Wilfred van Velzen wrote to Nicholas Boel:

Hit save too soon on the previous message. Apologies.

WV> I think the ABNF format is overly complex to specify such simple
WV> things. I don't see any RFC's mentioned in the bibliography only other
WV> ftsc documents. And FTS-0001 does it in a simple clear way:

WV>       HH         = "00" | .. | "23"
WV>       MM         = "00" | .. | "59"
WV>       SS         = "00" | .. | "59"

WV> Why not stick to that?

I can only guess he was following a more internet centric standard (when possible, of course), rather than using old Fidonet standards that are only useable here in Fidonet?

WV> Or if you want to be more specific, take as example rfc3339:

WV>    time-hour       = 2DIGIT  ; 00-23
WV>    time-minute     = 2DIGIT  ; 00-59
WV>    time-second     = 2DIGIT  ; 00-58, 00-59, 00-60 based on leap
WV> second
WV>                              ; rules

WV> And none specify that a minute can be 60 !

Also, with what I wrote in the previous message, take a look at the "dayOfMonth" which is allowing for 31 possibilities, whereas February only has 28 (and sometimes 29).

I don't think what Stephen wrote is saying you need to use all those numbers. It is merely allotting enough numbers to cover everything, even if it doesn't use all of them, as you can see (above) it does the same in RFC-3339, with a lot more room for error.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20161221
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.040391 секунды