java.net: Wiki

DateTimeCalendarTimeZoneClasses - how time zone should be integrated with calendar classes - chosen option 1
DateTimeCalendarInternalStorage - how should the data be stored for calendars - chosen option 1
DateTimeCalendarFieldNames - names for calendar fields - chosen option 1

Added:

>
>

DateTimeFields - duration and calendar fields - chosen option 2
DateTimeCalendarPrimitives - primitives vs objects from calendar classes - chosen option 2

Precision must support at least nanoseconds

The following choices have avoided via other decisions:

<<O>> Difference Topic DateTimeChoices (7 - 19 Nov 2007 - Main.scolebourne)

Line: 1 to 1

META TOPICPARENT	name="DateTimeScope"

JSR 310 Date and Time - Choices

Changed:

<
<

The following requires decisions:

>
>

The following topics require decisions:

DateTimeFields - duration and calendar fields

Changed:

<
<

DateTimeCalendarFieldNames - names for calendar fields
DateTimeDurationPrecision - how precisely do we want to store numbers

>
>

DateTimeCalendarPrimitives - primitives vs objects from calendar classes

The following decisions have been taken:

Line: 14 to 13

DateTimeCalendarClassNames - how should the calendar classes be named - chosen option 7
DateTimeCalendarTimeZoneClasses - how time zone should be integrated with calendar classes - chosen option 1
DateTimeCalendarInternalStorage - how should the data be stored for calendars - chosen option 1

Added:

>
>

DateTimeCalendarFieldNames - names for calendar fields - chosen option 1

Precision must support at least nanoseconds

Added:

>
>

The following choices have avoided via other decisions:

DateTimeDurationPrecision - how precisely do we want to store numbers

\ No newline at end of file

<<O>> Difference Topic DateTimeChoices (6 - 12 Nov 2007 - Main.scolebourne)

Line: 1 to 1

META TOPICPARENT	name="DateTimeScope"

JSR 310 Date and Time - Choices

Line: 6 to 6

DateTimeFields - duration and calendar fields
DateTimeCalendarFieldNames - names for calendar fields

Deleted:

<
<

DateTimeCalendarClasses - what calendar classes should be provided
DateTimeCalendarClassNames - how should the calendar classes be named
DateTimeCalendarTimeZoneClasses - how time zone should be integrated with calendar classes

DateTimeDurationPrecision - how precisely do we want to store numbers

Deleted:

<
<

DateTimeCalendarInternalStorage - how should the data be stored for calendars

The following decisions have been taken:

Added:

>
>

DateTimeCalendarClasses - what calendar classes should be provided - chosen option 6
DateTimeCalendarClassNames - how should the calendar classes be named - chosen option 7
DateTimeCalendarTimeZoneClasses - how time zone should be integrated with calendar classes - chosen option 1
DateTimeCalendarInternalStorage - how should the data be stored for calendars - chosen option 1

Precision must support at least nanoseconds

\ No newline at end of file

<<O>> Difference Topic DateTimeChoices (5 - 31 Oct 2007 - Main.scolebourne)

Line: 1 to 1

META TOPICPARENT	name="DateTimeScope"

JSR 310 Date and Time - Choices

Line: 7 to 7

DateTimeFields - duration and calendar fields
DateTimeCalendarFieldNames - names for calendar fields
DateTimeCalendarClasses - what calendar classes should be provided

Added:

>
>

DateTimeCalendarClassNames - how should the calendar classes be named

DateTimeCalendarTimeZoneClasses - how time zone should be integrated with calendar classes
DateTimeDurationPrecision - how precisely do we want to store numbers
DateTimeCalendarInternalStorage - how should the data be stored for calendars

<<O>> Difference Topic DateTimeChoices (4 - 08 Oct 2007 - Main.scolebourne)

Line: 1 to 1

META TOPICPARENT	name="DateTimeScope"

JSR 310 Date and Time - Choices

Line: 9 to 9

DateTimeCalendarClasses - what calendar classes should be provided
DateTimeCalendarTimeZoneClasses - how time zone should be integrated with calendar classes
DateTimeDurationPrecision - how precisely do we want to store numbers

Added:

>
>

DateTimeCalendarInternalStorage - how should the data be stored for calendars

The following decisions have been taken:

<<O>> Difference Topic DateTimeChoices (3 - 05 Oct 2007 - Main.scolebourne)

Line: 1 to 1

META TOPICPARENT	name="DateTimeScope"

JSR 310 Date and Time - Choices

Line: 8 to 8

DateTimeCalendarFieldNames - names for calendar fields
DateTimeCalendarClasses - what calendar classes should be provided
DateTimeCalendarTimeZoneClasses - how time zone should be integrated with calendar classes

Added:

>
>

DateTimeDurationPrecision - how precisely do we want to store numbers

The following decisions have been taken:

<<O>> Difference Topic DateTimeChoices (2 - 28 Sep 2007 - Main.scolebourne)

Line: 1 to 1

META TOPICPARENT	name="DateTimeScope"

JSR 310 Date and Time - Choices

Line: 7 to 7

DateTimeFields - duration and calendar fields
DateTimeCalendarFieldNames - names for calendar fields
DateTimeCalendarClasses - what calendar classes should be provided

Added:

>
>

DateTimeCalendarTimeZoneClasses - how time zone should be integrated with calendar classes

The following decisions have been taken:

<<O>> Difference Topic DateTimeChoices (1 - 28 Sep 2007 - Main.scolebourne)

Line: 1 to 1

Added:

>
>

META TOPICPARENT	name="DateTimeScope"

JSR 310 Date and Time - Choices

The following requires decisions:

DateTimeFields - duration and calendar fields
DateTimeCalendarFieldNames - names for calendar fields
DateTimeCalendarClasses - what calendar classes should be provided

The following decisions have been taken:

Precision must support at least nanoseconds

Topic DateTimeChoices . { View | Diffs r8 < r7 < r6 < r5 | More }

java.net RSS