The presence of paths: {} isn't intended to overload the meaning, it's because paths is a mandatory object in the OAS (2.0 and 3.0.x), although it can be empty.
x-fragment is a good idea to make that explicit.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why overload the the semantics of
pathand not simply add a"fragment: true"to theinfoobject? ("x-fragment"until it is adopted in the standard)Sure, it does not make much sense to have an API with no paths. But it will make it explicit that the specification is a fragment.
The presence of
paths: {}isn't intended to overload the meaning, it's becausepathsis a mandatory object in the OAS (2.0 and 3.0.x), although it can be empty.x-fragmentis a good idea to make that explicit.