Skip to content

Review names and purposes of each block #7

@karenmajewicz

Description

@karenmajewicz

I am reviewing https://gin.btaa.org/ld/api/responses/ and want to make sure I understand each type of block. In a typical endpoint, we might have:

  • links
  • data
  • meta
  • jsonapi

...and more.

It is a little hard to tell how some of these fit together and how they can be nested.

The name "meta" for one of the blocks feels a bit unintuitive. Is this standard terminology? With the "data" block containing metadata and the "meta" block containing various things like UI, it might be a little confusing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions