Comments (1)
I love it @micahhausler.
Regarding the format, one of the goals we want with OpenVEX is that once you discover one document, the format itself can provide links to the rest of the relevant statements using its linked data capabilities.
One of the features we're thinking of adding to OpenVEX is support for references to link to other documents. One of the use cases this will unlock is to have "empty" OpenVEX documents - that is docs without any VEX statements - that only reference other documents. For example (this is just an idea no proposal exists yet for this):
{
"@context": "https://openvex.dev/ns/v0.2.0",
"@id": "https://openvex.dev/docs/example/vex-9fb3463de1b57",
"links": [
{"ref": "https://myurl.com/index.openvex.json"},
]
}
Using that schema, you can reference another document with relevant statements, but also you could point to an OpenVEX API endpoint or a continuously appended document (like an index) with links to known documents. For example:
{
"@context": "https://openvex.dev/ns/v0.2.0",
"@id": "https://myurl.com/index.openvex.json",
"links": [
{"ref": "https://myurl.com/document1.openvex.json"},
{"ref": "https://myurl.com/document2.openvex.json"},
{"ref": "https://myurl.com/document3.openvex.json"},
]
}
It would be awesome to fast forward this, the .well-known
URL could respond with these documents.
from spec.
Related Issues (20)
- Clarify timestamps HOT 2
- `Products` not listed as required HOT 4
- VEX schema/spec version should be a field in the metadata HOT 4
- Product identifiers with CycloneDX HOT 4
- Add "impact_statement" to specification HOT 2
- Version ranges in product_id/subcomponent_id HOT 3
- PURL matching with qualifiers HOT 3
- Ability to refer back to an SBOM? HOT 4
- Update Spec to point out `@id` change HOT 1
- timestamp issue HOT 2
- Modify severity HOT 6
- Consider defining an OpenVEX mediaType HOT 2
- Use Cases HOT 1
- Diagram missing from ATTESTING.md
- README.md needs to be updated to reflect v0.2.0 spec changes HOT 1
- Make OpenVEX extensible ?
- Storing VEX files in a dedicated directory within Git repositories HOT 8
- clarifying product identification
- Clarification on Use of @id, PURL Identifier, and Impact Statements HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spec.