ga4gh-discovery/ga4gh-service-info

Issues

• Add optional GEOJson object to `organization`

  #73 opened a year ago by mbaudis
  2

• Clarify best practices for service-info path

  #72 opened 2 years ago by mcupak
  0

• Specification version bump for service info breaking changes

  #71 opened 3 years ago by tcezard
  2

• Service-info per version of API or per server that implements APIs?

  #70 opened 3 years ago by denis-yuen
  2

• Add support for usage stats?

  #69 opened 4 years ago by uniqueg
  0

• Include authorization information in service-info response

  #67 opened 4 years ago by jb-adams
  0

• Update Date Clarification

  #65 opened 4 years ago by garyluu
  0

• Describe the product on the Discovery website

  #15 opened 5 years ago by mcupak
  5

• Tagged release

  #61 opened 5 years ago by denis-yuen
  2

• Broken build

  #63 opened 5 years ago by mcupak
  0

• PRC and Plenary feedback tasks

  #55 opened 5 years ago by andrewyatz
  2

• Extract type schema

  #59 opened 5 years ago by mcupak
  2

• Document or specify how a service could implement a health check

  #58 opened 5 years ago by susheel
  3

• Clarify how the spec will support the DURI (AAI & Passport) spec

  #57 opened 5 years ago by susheel
  1

• Backwards pointing feature

  #60 opened 5 years ago by rishidev
  1

• Incorporate feedback from GA4GH Plenary Meeting 2019 XWS session

  #54 opened 5 years ago by mcupak
  0

• Clarify the use of organization and name

  #53 opened 5 years ago by mcupak
  0

• schemaUrl to document the API schema used by the service

  #26 opened 6 years ago by susheel
  0

• Cosmetic cleanup

  #51 opened 5 years ago by mcupak
  0

• Explain how to extend the specification by other specifications

  #35 opened 5 years ago by mcupak
  13

• Provide compliance verification tool

  #36 opened 5 years ago by mcupak
  4

• Consider organization field

  #21 opened 5 years ago by mcupak
  8

• Add field for service maturity

  #33 opened 5 years ago by mcupak
  3

• Make examples consistent

  #47 opened 5 years ago by mcupak
  0

• Support for authentication and authorization based on OIDC and OAUTH 2

  #30 opened 5 years ago by mcupak
  1

• Elaborate on error responses

  #25 opened 5 years ago by mcupak
  4

• Decide how the information exposed should be extended

  #10 opened 5 years ago by mcupak
  5

• Add API version

  #29 opened 5 years ago by mcupak
  2

• Flaky CI builds

  #38 opened 5 years ago by mcupak
  1

• Type as URN with version

  #39 opened 5 years ago by mpanik
  0

• Improve general info

  #31 opened 5 years ago by mcupak
  0

• Figure out a way to align with ELIXIR Beacon's Beacon Network proposal

  #5 opened 5 years ago by mcupak
  1

• Add URL to organization logo

  #34 opened 5 years ago by mcupak
  0

• Provide more info in README.md

  #16 opened 6 years ago by mcupak
  1

• Add service types

  #2 opened 6 years ago by andrewyatz
  5

• Fix links to the repository in README.md

  #24 opened 6 years ago by mcupak
  0

• Service info for implementations which support multiple APIs

  #22 opened 6 years ago by andrewyatz
  3

• Expanding meta payload

  #1 opened 6 years ago by andrewyatz
  3

• Name or type

  #3 opened 6 years ago by andrewyatz
  3

• Error-prone Travis setup

  #6 opened 6 years ago by mcupak
  0

• Add service type

  #8 opened 6 years ago by mcupak
  1

• Add description

  #9 opened 6 years ago by mcupak
  1

• Consider adding contactURL field

  #11 opened 6 years ago by mcupak
  1

• Consider adding documentationURL field

  #12 opened 6 years ago by mcupak
  1

• Consider adding ID field

  #14 opened 6 years ago by mcupak
  2

• One or many versions supported by a single endpoint

  #4 opened 6 years ago by andrewyatz
  2

• Review camelcase vs. snake_case

  #13 opened 6 years ago by mcupak
  1