Re: XSLT Date (was: Re: [xsl] keys and idrefs - XSLT2 request?)

Subject: Re: XSLT Date (was: Re: [xsl] keys and idrefs - XSLT2 request?)
From: "cutlass" <cutlass@xxxxxxxxxxx>
Date: Tue, 16 Oct 2001 18:24:41 +0100
ya,

when we were doing the EXSLT effort, we ran into the same scary stuff, in
the end Chris Bayes takes it on with the clientside stuff, and JT had some
xslt templates; it illustrated exactly the kind of effort one would
definately 'not' want to do using native xslt ( or clever taylor
algorithims ).

hehe, i understand the full implications of the requirement of scoping the
word 'date', and would be happy to supply the XSLT effort with our EXSLT
functional definitions of date-time.

chow, jim fuller

----- Original Message -----
From: "Joerg Pietschmann" <joerg.pietschmann@xxxxxx>
To: "XSL List" <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, October 16, 2001 6:09 PM
Subject: XSLT Date (was: Re: [xsl] keys and idrefs - XSLT2 request?)


> "cutlass" <cutlass@xxxxxxxxxxx> wrote:
> > and the incomplete list is ;
> ...
> > Dates
>
> This is often mentioned, but what does it mean?
> Some random thoughts:
> - Having a datetype available for sorting
> - Localized formats: Reformat a date into a localized
>   representation (without actually changing the calendar).
> - Localized parsing: Recognize a localized form of a date as
>   such and unambiguously determine which date it is for
>   further use in expressions. (i think this is dangerous and
>   should *not* be implemented)
> - Date comparision
> - Date arithmetic: increment a date by N days or months,
>   get the number of days between two dates and so on
> - Date functions: get the weekday, day of year, week of
>   year, check whether a date is in a leap year and so on
>   (ISO definitions)
> - Easy validated date construction (day/month/year).
> - Non-standard date construction: construct a date from
>   year + week-of-year + weekday and so on.
> - Validating: Check whether a tentatively constructed date
>   would be a valid date, or correct for various failure modes
>   (e.g. roll over). Check for valid month, day-in-month and
>   so on.
> - Localized date functions: use localized definitions for week
>   of year and so on instead of ISO definitions.
> - Calendars: convert a date into a representation used by a
>   non-gregorian calendar.
> - Calendar dependent date construction and validating functions.
> - Calendar dependent localized date parsing.
> - Historical localized calendars: deal with the various
>   calendar reforms (geeks only :-)
> - Built-in localized month and weekday names and abbreviations
>   (gregorian calendar)
> - Built-in localized calendar dependent names and abbreviations
>   for other calendars.
> - Functions related to certain holidays, like easter. (I was
>   about to add a smiley, but PHP has it).
>
> Furthermore, should the time of the day be incorporated?
> If so, you'll have suddenly to deal with time zones, DST,
> leap seconds, accuracy issues and a host of other problems
> i don't dare to mention.
>
> Look at the calendar FAQ and shudder. Look at the EMACS
> calendar module and shudder even more.
>
> Regards
> J.Pietschmann
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Current Thread