You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/schemas/validation/README.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,22 @@
1
-
# OpenAPI Arazzo 1.0.x JSON Schema
1
+
# OpenAPI Arazzo 1.X.Y JSON Schema
2
2
3
-
Here you can find the JSON Schema for validating Arazzo Documents conforming to versions 1.0.x.
3
+
Here you can find the JSON Schema for validating Arazzo Documents conforming to versions 1.X.Y, which are published on [https://spec.openapis.org](https://spec.openapis.org).
4
4
5
-
As a reminder, the JSON Schema is not the source of truth for the Specification.
6
-
In cases of conflicts between the Specification itself and the JSON Schema, the
7
-
Specification wins. Also, some Specification constraints cannot be represented
8
-
with the JSON Schema so it's highly recommended to employ other methods to
9
-
ensure compliance.
5
+
Due to limitations of GitHub pages, the schemas on the spec site are served with `Content-Type: application/octet-stream`, but should be interpreted as `application/schema+json`.
6
+
7
+
The sources in this directory, which have `WORK-IN-PROGRESS` in their `$id`s, are _not intended for direct use_.
10
8
11
9
The iteration version of the JSON Schema can be found in the `$id` field.
12
10
For example, the value of `$id: https://spec.openapis.org/arazzo/1.0/schema/2024-10-17` means this iteration was created on October 17, 2024.
13
11
14
12
## Contributing
15
13
14
+
As a reminder, the JSON Schema is not the source of truth for the Specification.
15
+
In cases of conflicts between the Specification itself and the JSON Schema, the
16
+
Specification wins. Also, some Specification constraints cannot be represented
17
+
with the JSON Schema so it's highly recommended to employ other methods to
18
+
ensure compliance.
19
+
16
20
To submit improvements to the schema, modify the `schema.yaml` and add test cases for your changes.
17
21
18
22
The TSC will then:
@@ -22,7 +26,7 @@ The TSC will then:
22
26
23
27
## Tests
24
28
25
-
The [test suite](../../tests/v1.0) is part of this package.
29
+
The [test suite](../../tests/schema) is part of this package.
description: An object used to describe the type and version of an expression used within a Criterion Object or Selector Object. If the `version` is omitted, a default value is assumed based on the expression `type`
300
307
type: object
301
308
properties:
302
309
type:
303
-
description: The type of condition to be applied
310
+
description: The type of selector to use
304
311
enum:
305
312
- jsonpath
306
313
- xpath
314
+
- jsonpointer
307
315
version:
308
-
description: A short hand string representing the version of the expression type
316
+
description: >
317
+
A short hand string representing the version of the expression type.
318
+
If omitted, the default for the selected type will be used.
description: An object which enables fine-grained traversal and precise data selection from structured data
572
+
type: object
573
+
properties:
574
+
context:
575
+
description: A valid Runtime Expression which MUST evaluate to structured data (e.g., `$response.body`), and sets the context for the selector to be applied on
576
+
type: string
577
+
selector:
578
+
description: A selector expression (e.g., `$.items[0].id`, `/Envelope/Item`) in the form of JSONPath expression, XPath expression, or JSON Pointer expression
579
+
type: string
580
+
type:
581
+
description: The selector expression type to use (e.g., `jsonpath`, `xpath`, or `jsonpointer`) or an Expression Type Object for older version support
description: While the Arazzo Specification tries to accommodate most use cases, additional data can be added to extend the specification at certain points
0 commit comments