Commits on May 16, 2024

1. Limit interoperable parsing expectations …

   As discovered through the OASComply project, certain referencing
   scenarios are ambiguous, with different authorities holding
   contradictory interpretations regarding whether and how they are
   to be supported.  As a result, it is impossible to define
   compliance, as all of the interpretations can be argued to be
   "correct" in some sense.
   
   This change excludes some particularly challenging scenarios from
   compliance testing by making their behavior explicitly
   implementation-defined.  This has several benefits:
   
   * No current implementation is rendered non-compliant
   * No currently usable OAD is rendered invalid
   * New implementers need not put effort into handling these scenarios
   * User expectations are set to _not_ expect consistent behavior
   * Linters can write a rule to match these expectations
   * Everyone is guided towards straightforwad best practices
   
   Includes substantially better wording from ralfhandl from
   review comments for the 3.1.1 version of this change.
   
   Co-authored-by: Ralf Handl <ralf.handl@sap.com>

   

   handrews and ralfhandl committed May 16, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 32c92aa
   • Browse repository at this point

   Copy the full SHA

   32c92aa View commit details

   Browse the repository at this point in the history

2. Schema Object does not have $ref in 3.0

   

   handrews committed May 16, 2024
   Configuration menu

   • View commit details
   • Copy full SHA for 5573dc6
   • Browse repository at this point

   Copy the full SHA

   5573dc6 View commit details

   Browse the repository at this point in the history