Fix spec references & two examples

[decentralgabe]

examples were using formatMinimum instead of the specified minimum

[decentralgabe]

it appears the tests fail because minimum expects a number. I believe this is a problem with the test...

[JaceHensley]

minimum/maximum is only for numbers, https://github.com/ajv-validator/ajv-formats#keywords-to-compare-values-formatmaximum--formatminimum-and-formatexclusivemaximum--formatexclusiveminimum

[decentralgabe]

Ok...upon further investigation:

formatMaximum and formatMinimum are not defined in the Draft 7 specs:

• https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-02
• https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-validation-02
• https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-hyperschema-02

There is a specific JS library that supports these additional fields...but it's not in the spec. So neither my change, nor the spec are correct and we probably need non-normative language to support non-integer min/max validation.

Edit: opened https://github.com/decentralized-identity/presentation-exchange/issues/312

[decentralgabe]

@JaceHensley that library uses a non-normative json schema extension to define these properties...which isn't widely supported across json schema implementations

[JaceHensley]

yeah I noticed that this week, I could've sworn I saw formatMinimum on https://json-schema.org/ previously but when I went back to look at it again I couldn't find it.

[csuwildcat]

What is formatMinimum anyway?

[JaceHensley]

It's a minimum, but the the comparison is based on the JSON schema format (date, date-time, uri, uuid, ip, etc.)

[bumblefudge]

@decentralgabe plz re-work, examples fixed in separate PR merged just now on call!

[decentralgabe]

thanks @bumblefudge minor fixes - updated!