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

Project Scope / Filtering #40

Closed
kinlane opened this Issue Jul 12, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@kinlane
Contributor

kinlane commented Jul 12, 2017

Introducing a fourth dimension of the scope / filtering conversation -- project level. How do parts of the schema and API definition get grouped, and evolved separately from other projects.

How is this separation described in API definition(s) - OpenAPI + APIs.json, which can then be reflected in documentation, SDKs, and other tooling.

This also needs to be thought about as it impacts the definition for a "HSDA compliant API or schema" - what % compliant is an API. Few will ever be 100% compliant, but providers can pick and choose which project areas they support or don't support.

@kinlane kinlane added the road map label Jul 12, 2017

@NeilMcKechnie

This comment has been minimized.

Show comment
Hide comment
@NeilMcKechnie

NeilMcKechnie Aug 10, 2017

@kinlane a simple way to start slicing this would be by CRUD activity. I suspect most of us will start with Reads first. Updates would make sense to add next if going sequentially. Then Create and Delete last of all. So one could claim (and be validated against that claim) to support one or more of those operations.

NeilMcKechnie commented Aug 10, 2017

@kinlane a simple way to start slicing this would be by CRUD activity. I suspect most of us will start with Reads first. Updates would make sense to add next if going sequentially. Then Create and Delete last of all. So one could claim (and be validated against that claim) to support one or more of those operations.

@kinlane

This comment has been minimized.

Show comment
Hide comment
@kinlane

kinlane Aug 31, 2017

Contributor

I'm breaking things down into:

  • HSDA
  • HSDA Search
  • HSDA Bulk
  • HSDA Meta
  • HSDA Taxonomy
  • HSDA Management
  • HSDA Orchestration
  • HSDA Utility
  • HSDA Aggregation

Which I will just reflect in practice through tagging, no need for issue.

Contributor

kinlane commented Aug 31, 2017

I'm breaking things down into:

  • HSDA
  • HSDA Search
  • HSDA Bulk
  • HSDA Meta
  • HSDA Taxonomy
  • HSDA Management
  • HSDA Orchestration
  • HSDA Utility
  • HSDA Aggregation

Which I will just reflect in practice through tagging, no need for issue.

@kinlane kinlane closed this Aug 31, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment