…, which imply that UTC is the preferred reference point for the specified time. RFC2822 [IMAIL-UPDATE] describes a similar convention for email "3.4.1 Characters used in the representations - Introduction". Data elements and interchange formats — Information interchange - Represe…

… to the originating document, not to the address where comments should be sent. RFC2822 (originally RFC822 ratified schema.DCTERMS External Resource Not allowed Maps the prefix "DCTERMS" for use in other Dublin-Core related link relations (such as DCTERMS.creator) and meta keywor…

…, which imply that UTC is the preferred reference point for the specified time. RFC2822 [IMAIL-UPDATE] describes a similar convention for email ISO 8601:2004(E): Data elements and interchange formats — Information interchange — Representation of dates and times ISO . 2004-12-01. …

…, which imply that UTC is the preferred reference point for the specified time. RFC2822 [IMAIL-UPDATE] describes a similar convention for email "3.4.1 Characters used in the representations - Introduction". Data elements and interchange formats — Information interchange - Represe…

…ly it would be clear that it is significant; given the history of RFC733/RFC722/RFC2822 and the slow adoption of 2822, I'm not too worried that the error in our document will hurt real-world interoperability. from pending Errata ID: 4762 Status: Verified Type: Editorial Publicati…

…s recommended use of Resent- header fields in the way that is inconsistant with RFC2822(William Leibzon; 2005-08-29) Appeal - 2005-08-29 Response - 2005-12-08 2005-08-25 Appeal: Publication of draft-lyon-senderid-core-01 in conflict with referenced draft-schlitt-spf-classic-02 (J…

…, which imply that UTC is the preferred reference point for the specified time. RFC2822 [IMAIL-UPDATE] describes a similar convention for email "3.4.1 Characters used in the representations - Introduction". Data elements and interchange formats — Information interchange - Represe…

…ly it would be clear that it is significant; given the history of RFC733/RFC722/RFC2822 and the slow adoption of 2822, I'm not too worried that the error in our document will hurt real-world interoperability. from pending Errata ID: 4762 Status: Verified Type: Editorial Publicati…