> -----Original Message-----
> From: Juergen Schoenwaelder <[email protected]>
> Sent: 08 July 2020 18:32
> To: Rob Wilton (rwilton) <[email protected]>
> Cc: Christian Hopps <[email protected]>; NetMod WG <[email protected]>
> Subject: Re: [netmod] Justification for decimal64 over string for floating
> point values in geo location data?
>
> On Wed, Jul 08, 2020 at 04:53:52PM +0000, Rob Wilton (rwilton) wrote:
> >
> >
> > > -----Original Message-----
> > > From: Juergen Schoenwaelder <[email protected]>
> > > Sent: 08 July 2020 17:44
> > > To: Rob Wilton (rwilton) <[email protected]>
> > > Cc: Christian Hopps <[email protected]>; NetMod WG <[email protected]>
> > > Subject: Re: [netmod] Justification for decimal64 over string for
> floating
> > > point values in geo location data?
> > >
> > > unknown precision != arbitrary precision
> > [RW]
> >
> > I agree. But don't follow the point that you are making. Please can
> you clarify.
> >
>
> To me
>
> type string;
> pattern "[0-9]+(\.[0-9]+)?";
>
> means unknown precision - everybody implements what seems convenient.
[RW]
Ah, Okay. Yes, I agree. I think that there are already too many types that
get encoded as a string in YANG.
My suggestion was to consider for the next version of YANG to potentially add
two new native YANG types:
- Binary float and binary double native YANG types, possibly restricted to
operational values only.
- A new arbitrary-precision-decimal native YANG type.
Regards,
Rob
>
> /js
>
> --
> Juergen Schoenwaelder Jacobs University Bremen gGmbH
> Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany
> Fax: +49 421 200 3103 <https://www.jacobs-university.de/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
