Cwm release of 2003-04-08 - Datatypes and math: and time:

This release can be identified as:

$ cwm --revision

cwm= $Revision: 1.7 $ llyn= $Revision: 1.7 $  

In this note the following prefixes are assumed.

@prefix math: <http://www.w3.org/2000/10/swap/math#>.
@prefix maths: <http://www.w3.org/2000/10/swap/maths#>.
@prefix time: <http://www.w3.org/2000/10/swap/time#>.
@prefix times: <http://www.w3.org/2000/10/swap/times#>.

This release has significant changes which may affect back-compatability.

Datatypes have been introduced. Datatypes are based on the XML Schema datatypes.

• The generic syntax for arbitrary datatypes in RDF/XML, N3 and NTriples is parsed in input and generated in output;
• In N3 alone, a specific syntax for integer and floating point literals (2 or 3.14e0 rather than "2", "3.14e0" etc) is both parsed and output when possible.
• (Note floats MUST have decimal points and MUST have an "e'. The format "3.2" is a formally a rational which, pending python rational development, is converted to a float on input. The format eg "4." with a trailing period is illegal.
• For math: and time: builtins, there is coersion of strings to numbers on input (before only strings were used)
• For string functions, coersion of numbers to string form in input.
• For math: builtins, new literals are generated on output

The last pont is the only one which SHOULD cause any problems with existing rule files. You may find that the calculations are correct, but that the output format is not what you expected.

If this is a problem in your system, then you can use a special string-oriented versions of these two functional libraries, using the maths: and times: (note the traiuling 's'). These libraries deliberately generate string versions of their output.

Note the previous release had partial integration of datatypes. They were parsed but not (officially) implemented in the built-in functions. Unfortunately, from some bug reports it seems there was some accidental generation of new integer types, which then caused errors. So a solution is to upgrade to 1.129 and let me know of any incompatabilities.

Let me know of any other problems

timbl+n3bugs at w3 dot org