Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to International chat echo - member...  <--  <--- Return to Home Page
   Networked Database  International chat echo - member...   [465 / 900] RSS
 From   To   Subject   Date/Time 
Message   mark lewis    Ozz Nixon   Re TZUTC   March 9, 2019
 7:37 AM *  

 On 2019 Mar 09 03:09:28, you wrote to Eric Pareja:

 EP>> I just looked up FTS-4008.002 and it appears that the + shouldn't be
 EP>> there.

 EP>> I'll file an issue on the WWIV tracker.

 ON> Sorry for a late response, been on the road all week...

 ON> Actually that would be incorrect. For ISO standards on UTC,

there's the problem, though... fidonet is not using ISO standards... fidonet
uses fidonet standards... some people just cannot seem to wrap their heads
around this fact...

 ON> the use of + is only required due to the fact it is appended directly
 ON> to the end of the seconds. Otherwise a 0500 appended to 11:30:22 would
 ON> make a mess of parsers "guessing"... for example 11:30:22500 and
 ON> 11:30:220500 are invalid. 11:30:22+0500 is correct.

while this is true, fidonet uses the TZUTC control line to store the UTC offset
 so there is no confusion like you describe... numbers without a sign are
positive and the only sign used is the '-' which easily indicates a negative...

 ON> However, you also cannot use "+" should be there because another
 ON> platform uses it. I spent 20+ years making a living developing to RFC
 ON> standards, and thus my interest in FTSC... to try and help. FTSC is
 ON> much easier to read, the challenge is conflicting specifications...
 ON> even in the current documents.

reading this, i thing we're saying the same thing...

 ON> FYI: ISO 8601 did not state the "+" as required in section 3.4.2 prior
 ON> to the 2004 edition of the standard. And FTSC-4008 was written prior
 ON> to 2004 also, and for our platform (FTSC) it's rules govern our
 ON> platform not vise versa.

exactly! thank you!

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... If you're on thin ice, you might as well dance. - Anon
---
 * Origin:  (1:3634/12.73)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to International chat echo - member...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0961 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_1e7numc0ut6km3imreov6b2t72, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_1e7numc0ut6km3imreov6b2t72, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_1e7numc0ut6km3imreov6b2t72, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0