RE: What's a Number? Was: TJSON

Just to be clear, I think there are two separate issues.

Anders wrote:
> Yes, there seems to be many ways mapping unsupported/missing data types
> as an alternative to explicitly tagging data.


1)  >mapping< of types to instance values can be done in many ways (inline, in code, in schema, etc.)
2)  Construction and Definition of types appropriate to the application is what in the details of XSD 1.1 part 2.

Anders addresses #1.

I don't see any way that a solution to one of these issues affects the other one, so they may be decided independently.

Best regards,
David

> -----Original Message-----
> From: Anders Rundgren [mailto:anders.rundgren.net@gmail.com]
> Sent: Saturday, November 05, 2016 3:41 AM
> To: Shane McCarron
> Cc: David Ezell; Tony Arcieri; Interledger Community Group
> Subject: Re: What's a Number? Was: TJSON
> 
> On 2016-11-04 18:39, Shane McCarron wrote:
> > I couldn't agree more strongly with what David said.  The XSD work is
>  > seminal and more than sufficient for anything we might need as far as I
> know.
> > We have done some really interesting things with JSON Schema and JSON-
> LD.
>  > In both cases we just rely on XSD types for the underlying explicit meaning.
> 
> Yes, there seems to be many ways mapping unsupported/missing data types
> as an alternative to explicitly tagging data.
> 
> - JSON Schema
> 
> - The "old-school" programmatic way: writer.setBigDecimal("amount",
> bigdecimalvalue)
> 
> - Annotations:
>     https://golang.org/pkg/encoding/json/#example_Marshal

>     Int64String int64 `json:",string"
> 
> Providing an explicit mapping table can also be useful:
> https://cyberphone.github.io/doc/security/jcs.html#Data_Types

> 
> Anders
>

Received on Monday, 7 November 2016 14:38:05 UTC