On 24/02/15 12:04, Stian Soiland-Reyes wrote:
Any reason why we can't suggest this addition upstream into xerces?
No reason. But what difference does that make?
It would not help Jena until Xerces2-next is released and that would get
tied up with other XSD Schema 1.1 things that are irrelevant to Jena.
See http://xerces.apache.org/#xerces2-j
The ideal would be to create a RDF-centric datatype library independent
of the XML world once and for all. Only a subset of the machinery is
needed for RDF. Leave the XML->Java (the value stuff) to
javax.xml.datatype.
As many system come back to Xerces, cutting out that part as a
self-contained library makes some sense but it's not trivial to do, with
a real cost in support for the next X years.
There is/was xsdlib now at:
https://java.net/projects/msv/sources/svn/show/trunk/xsdlib
Andy
(BTW the JENA-886 proposal is maybe ~20 lines of code)
On 24 February 2015 at 10:44, Andy Seaborne (JIRA) <[email protected]> wrote:
Andy Seaborne created JENA-886:
----------------------------------
Summary: Add xsd datatype
Key: JENA-886
URL: https://issues.apache.org/jira/browse/JENA-886
Project: Apache Jena
Issue Type: Improvement
Components: Datatypes
Affects Versions: Jena 2.12.1
Reporter: Andy Seaborne
Assignee: Andy Seaborne
Priority: Minor
There are some new XSD datatypes not covered by Jena's datatype system.
* xsd:dateTimeStamp
* xsd:yearMonthDuration
* xsd:dayTimeDuration
They are all derived types. While Xerces does not directly support them (they
are in XSD 1.1 final, Xerces 2.11.0 only goes as far as drafts of 1.1), they
can be supported easily by inherining from the base type and fixing the URI and
the parsing. Their value is one of the existing value types and they can be
treated via syntactic restrictions on the lexical form.
ARQ already handles these types as values to a limited extent. Putting them
into Jena core datatypes woul dunify the handling.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
