Page Comparison

🔓 Public Page

Agenda

• Network/Welcome

• Antitrust Statement

  • This meeting is subject to the terms of our anti-trust statement shown here.  In addition, this meeting may be recorded. 

• Review Meeting Minutes

• Should we bail on schema bundling? Just provide unbundled schemas and the BAD and let consumers bundle if they want.

• Should we abandon investigation into @hyperjump bundling?

• Discuss slow adoption of our chosen version levels of json-schema draft/2020-12 and OpenAPI Specification 3.1.0. Did we jump the gun? Feedback/resistance about tools that support those versions is a constant refrain within our companies and now in our committee too.

• (How) are consumers going to use our schemas? And how should that affect our direction?

• Release numbering: We’re done with 0.0.1 and with breaking changes we must increment the major version to 1. https://semver.org/#spec-item-9 talks about pre-release numbering, which we will want to use the moment we increment to 1.0.0, but still plan on making changes (remember rule 1 is never to release any changes to a versioned document under the same version number)

• What are we planning for a next release? And when?

• Shall we document our conventions for property naming? We have a few rules in our JSON style guide, but we apply other rules (remember about Qty suffix, always abbreviating Nbr, *Ind for Boolean or indicator? Is this just an oral tradition?)

• What about “the Chris Poulos question” just what’re the property name going to be for a start

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Reviewed Accepted

• We have a Great Show for you tonight!

  • Should we bail on Schema Bundling?

    • What are benefits of bundling?

      • Bundling allows us to make endpoint schemas for endpoint be as small as possible, resolve all references.

      • Allows smaller package we can deliver to our members.

    • We can put bundling and hyperjump to the back burner and focus on the schema.

      • Step away from hyperjump until the tools catch up with it.

    • Add Action Item for Pros and Cons of bundling to next meeting agenda to move on from today.

  • Slow adoption

    • Folks saying we can’t use this because its not working with tools.

    • The JSON Ref parser has caused issues with our development, but bundling is important. What do we have to have for the starting part.

  • How will consumers use our products?

    • We are creating the standards to work with open API

    • We can use converters on our true source of truth to have other versions that work for the consumers.

      • Version 2009 is supported by pojo

        • Andy worked on our schema to json schema to pojo with 2012 version. There is limited success.

        • our schemas are very basic, they are big, but they are simple. No complex if than else logic, no new dialects, which makes it simple to convert.

  • 0.1 was first version, but if we make breaking changes it would be 1.0

    • We need prerelease versioning

    • There is no breaking anything yet since we only have 0.1 and its not a first release.

    • Sematic versioning looks good.

      • is 1.1 a pre release are should we go to 0.2, 1.0 is first release? Release 9 can be the first release?

      • What from the they said you should start at 010. For us, we can increment to 010 and then we will be following our new overlord.

👨‍💼 Great Work everyone

Up Next

• Network/Welcome

• Antitrust

• Review Meeting Minutes

• Review Work Changes

Action items

Decisions

Reference