Ticket #61 (closed enhancement: wontfix)

Opened 4 years ago

Last modified 4 years ago

0016807: 1 [Core] dateTime waarden in formaat "YYYY-MM-DDThh:mm:ss" (Forum)

Reported by: admin Owned by: frans
Priority: major Milestone: MediaMosa 1.7
Component: Core Version: Irrelevant
Keywords: Cc:
MoSCoW: Estimated time after impact analysis:
Related to project: none Tested:
Accepted: yes Estimated Hours:

Description


0016807: 1 [Core] dateTime waarden in formaat "YYYY-MM-DDThh:mm:ss" (Forum)
 http://mantis.kennisnet.nl/view.php?id=16807

Momenteel worden de dateTime waarden in het formaat "YYYY-MM-DD hh:mm:ss" teruggegeven. Kan dit gewijzigd worden naar "YYYY-MM-DDThh:mm:ss", dus met een 'T' als separator tussen het datum en tijd gedeelte. Dit is namelijk het formaat volgens de XML Schema specificatie. Als je voor de XML van VP-Core een XSD zou opstellen moet je datum velden aangeven met het type xs:dateTime. Daaruit volgt automatisch de consequentie dit "YYYY-MM-DDThh:mm:ss" formaat te gebruiken.
Ikzelf en volgens mij de PA loopt tegen dit probleem aan bij het parsen van XML naar (Java/C#) classes.

Change History

Changed 4 years ago by MC-arjen

  • accepted set to 0
  • component set to Core
  • milestone changed from MediaMosa 1.6 to MediaMosa 1.7

This appears to be a major issue. Yes we have versioning in the rest calls, but format date functions are used at many places in the code. For now postponed to the next version (1.7?)

Changed 4 years ago by admin

  • accepted changed from 0 to no

Changed 4 years ago by marek

  • owner set to frans
  • status changed from new to assigned

According to ISO 8601 standard. It is valid to place a space between the date and time. For more information please see this wikipedia page:  http://en.wikipedia.org/wiki/ISO_8601

To modify this thoughout VP-core with backward compatibilty this would require a lot of efforts.

Opinion?

Changed 4 years ago by admin

  • status changed from assigned to closed
  • resolution set to fixed
  • related_to set to none

We apply to ISO standards, and an upgrade has impact for existing users. So will close for now unless somebody has a good argument to do otherwise...

Changed 4 years ago by Frans

Resolution: unchanged
Status: nor closed nor fixed.

Will settle for the status as is for now.

Combined date and time representations
<date>T<time> 	<date>T<time>Z

Combining date and time representations to represent a single point in time (time point) is quite simple. It is in the format of <date>T<time> where the time designator [T] is used to show the start of the time component of the representation. Both the date and time components of the time point are any proper representations of date and time specified by the standard. For example, "2007-04-05T14:30" uses the extended formats for date and time [YYYY]-[MM]-[DD]T[hh]:[mm], while "20090621T0545Z" uses the basic formats [YYYY][MM][DD]T[hh][mm]Z.

A combined date and time representation can be used to mark any type of event time such as an e-mail delivery, a financial transaction, the start of a medical treatment, or even a natural occurrence (like the summer solstice of 2009 shown above). Combined date and time representations are also used in conjunction with time intervals as discussed later in this article.

The date and time representations may appear in proximity to each other, often separated by a space or sometimes by other characters. In these cases they occupy two separate fields in a data system, rather than a single combined representation. This is usually done for human readability. '''Unlike the previous examples, "2007-04-05 14:30" is considered two separate, but acceptable, representations—one for date and the other for time. It is then left to the reader to interpret the two separate representations as meaning a single time point based on the context.'''

Changed 4 years ago by Frans

  • status changed from closed to reopened
  • version set to Irrelevant
  • resolution fixed deleted

Changed 4 years ago by Frans

  • status changed from reopened to closed
  • accepted changed from no to yes
  • resolution set to wontfix
Note: See TracTickets for help on using tickets.