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...   [482 / 900] RSS
 From   To   Subject   Date/Time 
Message   Maurice Kinal    Ozz Nixon   Re TZUTC   March 12, 2019
 8:44 PM *  

Hey Ozz!

 ON> See we can not say that, as the ISO standard also had "+" as
 ON> optional, until it was revised in 2004.

References please.  I've never seen any mention of the + as an option in any
official documentation of utc offsets and in fact have seen the opposite
including that UTC (+0000) is to include a + sign despite it not being behind
or ahead of UTC (ISO 8601).  Another reference worthy of mention is
https://en.wikipedia.org/wiki/List_of_UTC_tim... which is worth comparing
 to the list in fts-4008.002.  The only reference to 2004 I see as far as ISO
8601 is concerned is as follows (and I quote);

  The section dictating sign usage (section 3.4.2 in the 2004 edition
  of the standard) states that a plus sign must be used for a
  positive or zero value, and a minus sign for a negative value.
  Contrary to this rule, RFC 3339, which is otherwise a profile of
  ISO 8601, permits the use of "-00", with the same denotation as
  "+00" but a differing connotation.

If you could please provide further evidence of an ISO, or RFC, prior to 2004
that states the + character is optional I'd appreciate it.  However I doubt it
will change anything given the current state of well used modern dating
applications that insist on displaying the + character when and where it is
applicable.  As for the above quote, and if my ageed memory serves me correct,
the "differing connotation" is a - character can be used in UTC when it is
converted from a different timezone other than UTC itself.

  date --iso-8601=seconds = 2019-03-12T21:35:03+00:00
  date --rfc-3339=seconds = 2019-03-12 21:36:50+00:00

From the above it looks to me that both standards are in sync wrt the display
of utc with a + character.  Also worthy of note is the : character to delimit
hours from minutes in the offset.  To make that work it has to use the %:z
specifier, or even %::z to include seconds, as shown below;

  date +%:z = +00:00
  date +%::z = +00:00:00

Put *THAT* in your corrupted fts-4008.002 standard and rotate! :::evil grin:::

Life is good,
Maurice

... Don't cry for me I have vi.
--- GNU bash, version 5.0.2(1)-release (x86_64-pc-linux-gnu)
 * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)
  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.0813 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_2t02vlnfuu7388eq2db1ebogh0, 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_2t02vlnfuu7388eq2db1ebogh0, 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_2t02vlnfuu7388eq2db1ebogh0, 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