Skip to content
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.

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

how to discover API labels #1

Open
dret opened this issue Nov 29, 2019 · 6 comments
Open

how to discover API labels #1

dret opened this issue Nov 29, 2019 · 6 comments

Comments

@dret
Copy link
Collaborator

dret commented Nov 29, 2019

how do we want to make API label documents discoverable? here are two options:

  • define a labels link relation type to be specifically defined for associating labels (could be used for other labeling schemes as well).

  • recommend the use of the existing link relation type describedby to be used for linking to an API labels document.

dret added a commit that referenced this issue Nov 29, 2019
@dret
Copy link
Collaborator Author

dret commented Nov 29, 2019

it may also be worth to talk about discovery from formats that are relevant but have no built-in way to use typed links. OpenAPI comes to mind...

@dret
Copy link
Collaborator Author

dret commented Dec 10, 2019

wondering whether while you're working of the landscape viewer and the set of labels it is using, @u1i, there is some input for this issue just from the implementation point of view?

@dret
Copy link
Collaborator Author

dret commented Dec 10, 2019

for now (i.e., the API days paris presentation), http://dret.net/lectures/api-days-paris-2019/#api-to-labels is saying that we're going the describedby route.

dret added a commit that referenced this issue Dec 11, 2019
@ioggstream
Copy link
Contributor

Integrating API labels and OAS could be interesting.

Related to OAI/OpenAPI-Specification#1973

@dret
Copy link
Collaborator Author

dret commented Jan 16, 2020 via email

@ioggstream
Copy link
Contributor

ioggstream commented Jan 16, 2020

this is a simplistic approach, though it's something. Clearly those are not expected to overlap with other info attributes.

info:
  ....
  x-draft-labels:
    labels:
       maturity: stable
       "https://foo.it#bar": baz
 

Let me know if you have another proposal. We aim at populating api catalogs based just on OAS spec and that's one of the missing links to achieve the goal.

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

No branches or pull requests

2 participants