W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > October 2010

ISSUE-57: TypedLiteralConverter Failures and Exceptions

From: RDFa Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Thu, 28 Oct 2010 01:38:05 +0000
To: public-rdfa-wg@w3.org
Message-Id: <E1PBHRN-0004QH-MO@otto.w3.org>

ISSUE-57: TypedLiteralConverter Failures and Exceptions

http://www.w3.org/2010/02/rdfa/track/issues/57

Raised by: Nathan Rixham
On product: 

The RDFa API document currently states:

"The return value upon conversion failure is being actively discussed in the RDFa WG. There are proposals to raise exceptions upon conversion failure, proposals to return tuples containing conversion success/failure and the converted value, as well as other mechanisms that would allow the signalling of a conversion failure from the method to calling code."

After implementing it is clear that Exceptions should not be thrown, and that TypedLiterals *must* always be created, valueOf() functionality is additional functionality provided by the API, however this is not a requirement of parsing RDFa Documents, a TypedLiteral can be created regardless of having TypedLiteral conversion.

Another proposal is that failures in conversion are handled the same as TypedLiterals which have no converter registered.

Which raises the issue that we have not defined what valueOf() should return when no appropriate TypedLiteralConverter is registered.
Received on Thursday, 28 October 2010 01:38:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:22 UTC