Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Appendix on converting data types to strings (3.0.4) #3840

Merged
merged 5 commits into from
Jun 10, 2024
Merged

Appendix on converting data types to strings (3.0.4) #3840

merged 5 commits into from
Jun 10, 2024

Commits on Jun 10, 2024

  1. Appendix on converting data types to strings (3.0.4) 

    It's very unclear how numbers, booleans, and other non-UTF-8-string
values are converted to strings, particularly for the form media types.
This adds a brief appendix that acknowledges the lack of standardization,
and points to resources for the few cases that do have specifications.

It highlights concerns with relying on certain JSON Schema keywords
or values for serialization, and suggests defining schemas of
type string and requiring applications to perform the conversion
prior to schema validation as a way to control the results.

This also clarifies that schema validation occurs before serialization.
    @handrews
    handrews committed Jun 10, 2024
    Configuration menu
    Copy the full SHA
    deebfd0 View commit details
    Browse the repository at this point in the history

  2. Make Object names links (review feedback) 

    Co-authored-by: Ralf Handl <ralf.handl@sap.com>
    @handrews @ralfhandl
    handrews and ralfhandl committed Jun 10, 2024
    Configuration menu
    Copy the full SHA
    b6e7204 View commit details
    Browse the repository at this point in the history

  3. Grammatical typo (review feedback) 

    Co-authored-by: Ralf Handl <ralf.handl@sap.com>
    @handrews @ralfhandl
    handrews and ralfhandl committed Jun 10, 2024
    Configuration menu
    Copy the full SHA
    1b6c426 View commit details
    Browse the repository at this point in the history

  4. Use correct versions of JSON Schema and JSON specs 

    JSON Schema was accidentally the draft for 3.1, while this spec
uses the older 7159 for JSON instead of 8259, so I have matched
that rather than change it or cite both.
    @handrews
    handrews committed Jun 10, 2024
    Configuration menu
    Copy the full SHA
    1cf5b0b View commit details
    Browse the repository at this point in the history

  5. Add note about RFC6570 type conversions 

    The spec doesn't address it, but implementations often have
their own rules.
    @handrews
    handrews committed Jun 10, 2024
    Configuration menu
    Copy the full SHA
    aacbbc9 View commit details
    Browse the repository at this point in the history