Project

General

Profile

Actions

Bug #1152

closed

datetime element does not use consistent naming

Added by Chad Berkley over 20 years ago. Updated over 15 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
eml - general bugs
Target version:
Start date:
09/23/2003
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
1152

Description

The datetime element in eml-attribute should be spelled dateTime to be
consistent with the other dateTime elements and types. we may not be able to
fix this in eml2 because it will break backwards compatibility.


Related issues

Blocked by EML - Bug #3508: create a stylesheet for EML2.0.x to EML 2.1.0NewMatt Jones10/06/2008

Actions
Actions #1

Updated by Matt Jones over 20 years ago

This is a relatively minor issue, and I think that it is not worth breaking
backwards compatibility to fix it. I'm retargeting this at the 2.1 milestone,
which is when we might break some backwards compatibility and so should consider
fixing it then. I'm not sure it is worth fixing it at all, because it will only
mean that people have to map the "datetime" element to "dateTime".

Actions #2

Updated by Matt Jones over 19 years ago

Changing QA contact to the list for all current EML bugs so that people can
track what is happening.

Actions #3

Updated by Margaret O'Brien over 15 years ago

targeting for 2.1.0, although may drop back to unspecified.

Actions #4

Updated by Margaret O'Brien over 15 years ago

declaration of datetime element in attribute.xsd is now dateTime:
<xs:element name="dateTime">
to be consistent with the other uses of this term in EML (dateTimeDomain, dateTimeFormat)

Actions #5

Updated by Redmine Admin almost 11 years ago

Original Bugzilla ID was 1152

Actions

Also available in: Atom PDF