[dsdl-discuss] Re: Fw: DTLL 0.4

Jeni

I noted another problem while trawling through Appendix A on the train
yesterday:

The definition of PostiveInteger does not have a line declaring the value
variable.

I wasn't too happy with the definition of nonNegativeInteger either. Is it
really valid to negate a negative to map from integer to nonNegativeInteger,
rather than just discarding any negative value?

In the definition of double I couldn't work out how the decimal exponent was
being mapped to an integer. Is there some special magic in dt:default?

Leaving the timezone stuff in all the date formats is a real pain. I feel we
ought to issue a healthwarning re the need for them. This example highlights
the need for a more modular approach, whereby people can parse dates with or
without timezones by having an optional 'entity' that can be nulled out if
you don't want a timezoned date.

Do ISO and XSLT really require you to enter 55BC as -0055 rather than -55?
Your definition requires four or more digits in every year!

I was also confused by your definition of month, where I can have any two
digits in the value but when it comes to matching these we somehow magically
change a two digit string to a single digit number, so that what you check
for is $this.month = 1 not $this.month="01". I get wary of any "automated
casting" presumption. We need to spell out the rules here very, very
carefully.

I could also do with an explanation of what the <include
href="numbers.dtl"/> statement is doing.

Hope this helps

Martin

--
DSDL members discussion list
To unsubscribe, please send a message with the
command  "unsubscribe" to dsdl-discuss-request@dsdl.org
(mailto:dsdl-discuss-request@dsdl.org?Subject=unsubscribe)