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

Doc: Extensibility for indexing #7

Open
SteveLasker opened this issue Aug 10, 2022 · 2 comments
Open

Doc: Extensibility for indexing #7

SteveLasker opened this issue Aug 10, 2022 · 2 comments

Comments

@SteveLasker
Copy link
Collaborator

A SCITT instance will have a well known schema for submitting and querying claims, attestations and endorsements. Often, a claim will have some level of associated evidence.
The evidence may be opaque or may need to be indexed. For instance, a specific SCITT instance my know how to index a specific SBOM format. However, a SCITT instance shouldn't block persistence of unknown formats.

This doc will capture how a SCITT instance may opt into indexing a specific format, providing value over the content.

The most obvious scenario is searching for a package within an SBOM.

@OR13
Copy link
Collaborator

OR13 commented Aug 11, 2022

This seems like it could become very complicated.

I imagine indexing would happen outside the ledger, based on "content aware" policies.

@SteveLasker
Copy link
Collaborator Author

yup, i was thinking something along the sharepoint and windows indexing model. There would be extensibility points for plugins to hook push/post events to index content specific types.
Then, the query language needs a model for dipping into those indexes.

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