Skip to content

docs(api): clarify graphic data validation (Issue #75) #79

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

Open
Richardpwe wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(api): clarify graphic data validation (Issue #75) #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions v1/specification/docs/Specification_Server_API.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,11 @@ For example, if the base URL is `https://example.com/my/prefix/ograf/v1`, the Op

The `/ograf/v1` path prefix used in examples is allowed, but not required.

### Graphic data validation (optional)

* The Server MAY validate `params.data` sent to `load()` or `updateAction()` against the Graphic Manifest's `schema` field.
* Handling data that does not conform to the schema is implementation-specific. The specification does not require a hard failure or prescribe an HTTP status code or response body.

### Security (optional)

* The current version of the Server API doesn't specify any security measures.
Expand Down