Re: [Cbor] Invalid Tag Values

Carsten Bormann <cabo@tzi.org> Thu, 24 June 2021 20:15 UTC

Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <9bec699fcdc78de53f13e591ec139ff8@mothers-arms.co.uk>
Date: Thu, 24 Jun 2021 22:15:45 +0200
Cc: cbor@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <34EA7F4F-FC62-4175-A0C0-95AD37A85CCB@tzi.org>
References: <f5650d87a36b10f6b75d2a1123f84bb5@mothers-arms.co.uk> <C4A51BCF-D1C1-41D4-BF1B-47CB75EEFAFA@tzi.org> <9bec699fcdc78de53f13e591ec139ff8@mothers-arms.co.uk>
To: Kio Smallwood <kio@mothers-arms.co.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/AW3doB5jaBhnFbyGomRyqdfjmv4>
Subject: Re: [Cbor] Invalid Tag Values
Precedence: list

On 2021-06-24, at 22:11, Kio Smallwood <kio@mothers-arms.co.uk> wrote:
> 
> So if I follow the logic correctly, if my decoder encounters 0("1900-01-00T00:00;00") instead of raising an exception it could return
> 
> 65535({
>     "value": "1900-01-00T00:00;00", 
>     "_error":"invalid datetime string: '1900-01-00T00:00;00'",
>     "original_tag": 0
> })
> 
> to the application? We could then have a tag handler or schema verifier raise the error or just log it, but in this case the full CBOR stream would be decoded.

If you don’t have a way to funnel up an error indication completely separate from the tag system, this strikes me as the second best way to do it.

Grüße, Carsten

[Cbor] Invalid Tag Values Kio Smallwood
Re: [Cbor] Invalid Tag Values Laurence Lundblade
Re: [Cbor] Invalid Tag Values Carsten Bormann
Re: [Cbor] Invalid Tag Values Kio Smallwood
Re: [Cbor] Invalid Tag Values Carsten Bormann