Skip to content

Conversation

handrews
Copy link
Contributor

@handrews handrews commented Nov 8, 2016

This addresses issue #97, where it was noted that "The only
interpretation that makes sense is it's providing an array
of instances, each can be described by the schema."

This makes the schema an array schema, and replaces the "self"
link with the more correct (or at least less confusing in this
context) "item" link.

Also fix a "the the" typo in the security considerations section,
and make "hyper-schema" consistent.

This addresses issue json-schema-org#97, where it was noted that "The only
interpretation that makes sense is it's providing an array
of instances, each can be described by the schema."

This makes the schema an array schema, and replaces the "self"
link with the more correct (or at least less confusing in this
context) "item" link.

Also fix a "the the" typo in the security considerations section,
and make "hyper-schema" consistent.
@Relequestual
Copy link
Member

Giving those who were involved in #97 a few days to object, but it seems pretty clear cut to me.

@Relequestual
Copy link
Member

Actually, I'm happy with this change, and don't think it requires further feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants