Skip to content

[FIRST ROUND]Review Discussion #3

@vongosling

Description

@vongosling
  • Spec descriptions should follow the rules: one-paragraph overview, parameter description, and use case.

  • Lack of the content negotiation in content types(application/json should be supported), we could provide multiple, weighted preferences:

Accept: application/vnd.openschema.v1+json; q=0.8, application/json; q=0.5

  • Error code should be defined. Or say, do we need to follow the RFC[1] ? In this way, we could provide the error validator template.

[1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussVery constructive and to be made wider open

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions