iso8601

I have a year (2002) and I'm trying to get it into the following format: 2002-00-00T00:00:00 I tried various iterations, the last of which was this: $testdate = DateTime::createFromFormat(DateTime::ISO8601, date("c")) echo date_format($testdate, '2002'); But, even if I come close, it always seems to add +00:00 to the end of it... The 'c' format in PHP always appends the timezone offset. You can't avoid that. But you can build the date yourself from components: date('Y-m-d\TH:i:s', $testdate); date('Y-m-d\TH:i:s\Z', time() - date('Z')); Best way is to use constants (PHP 5 >= 5.5.0, PHP 7) date

There are many SO questions and answers regarding parsing of ISO8601 date/times in .NET and C#. However, there doesn't seem to be a 'definitive' answer anywhere, i.e. an answer that presents a formally correct ISO8601 parser that would correctly parse all of the possible format variants within ISO8601 and that would disallow non-ISO8601 variants. This SO answer is the closest match so far... How to create a .NET DateTime from ISO 8601 format Okay. Let's start with the limitations you are placing on ISO 8601 yourself: You want a DateTime, so all formats that only result in a time-of-day,

The following is the definition of IS0 8601:2004 standard. It says that the fraction of second can be represented with one to six digits. Can I use all the 6 digits for representing the fraction of a second? Are the following Representation correct, if I use 6 digits for representing fraction of a second? 1ms -- 001000 10ms -- 010000 100ms -- 100000 {Extended Time Format} (32 bytes) YYYY-MM-DDThh:mm:ss.sTZD YYYY = Year 0000 to 9999 MM = Month 01 to 12 DD = Day 01 to 31 T = special separator T hh = Hour 00 to 23 mm = Minute 00 to 59 ss = Second 00 to 59 s = one to six digits representing a

Closed . This question is opinion-based. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . From the ISO-8601:2004(E) Specification: 4.2.2.4 Representations with decimal fraction If necessary for a particular application a decimal fraction of hour, minute or second may be included. If a decimal fraction is included, lower order time elements (if any) shall be omitted and the decimal fraction shall be divided from the integer part by the decimal sign specified in ISO 31-0, i

I have a Web API application that returns JSON to consumers who may not be using Microsoft technologies. When my controller returns an object with DateTime properties as JSON, it serializes the date in this format: 2017-03-15T00:00:00-04:00 This is giving the consumer a bit of a headache as they're expect it to be in ISO 8601 format. Some research has told me that JSON.NET now uses ISO 8601 by default (I am using 9.0.1). When I run this code... Clipboard.Copy(JsonConvert.SerializeObject(DateTime.Now)); ...I get this: 2017-03-15T09:10:13.8105498-04:00 Wikipedia shows these as valid ISO 8601