THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

All pages with prefix

Jump to: navigation, search
All pages
   
Technical Team/SPDX RDF Vocabularies and Terms/1.1Technical Team/SPDX RDF Vocabularies and Terms/1.1/TermsTechnical Team/SPDX RDF Vocabularies and Terms/1.1/Vocabulary
Technical Team/SPDX RDF Vocabularies and Terms/1.2Technical Team/SPDX RDF Vocabularies and Terms/1.2/TermsTechnical Team/SPDX RDF Vocabularies and Terms/1.2/Vocabulary
Technical Team/SPDX RDF Vocabularies and Terms/2.0Technical Team/SPDX RDF Vocabularies and Terms/2.1Technical Team/SPDX RDF Vocabularies and Terms/DRAFT/2.0
Technical Team/SPDX RDF Vocabularies and Terms/DRAFT/2.0/TermsTechnical Team/SPDX RDF Vocabularies and Terms/DRAFT/2.0/VocabularyTechnical Team/SPDX Specification Versions
Technical Team/SPDX Upcoming MeetingsTechnical Team/Spec Release ProcessTechnical Team/Spreadsheet Template
Technical Team/Use Cases/2.0Technical Team/Use Cases/2.0/Aggregators aggregating other aggregations for redistributionTechnical Team/Use Cases/2.0/Application which ships with a contrib libraries
Technical Team/Use Cases/2.0/Application which ships with development toolsTechnical Team/Use Cases/2.0/Application which ships with documentation and media and softwareTechnical Team/Use Cases/2.0/Backtrack from binary to source files
Technical Team/Use Cases/2.0/Build System YoctoTechnical Team/Use Cases/2.0/Check to see if the SPDX data provided matches the files provided and is trustworthy and most current for packageTechnical Team/Use Cases/2.0/Collecting enough information to allow auditor to make recommendations to remove or not a component
Technical Team/Use Cases/2.0/Committer annotates source files with SPDX dataTechnical Team/Use Cases/2.0/Committers provides SPDX data for a code being committedTechnical Team/Use Cases/2.0/Communicate data beyond what is described in spec
Technical Team/Use Cases/2.0/Consuming code snippetsTechnical Team/Use Cases/2.0/Contracts with multiple parties requiring signoff by allTechnical Team/Use Cases/2.0/Contributor makes commit subject to existing SPDX data of project
Technical Team/Use Cases/2.0/Debian has an interest in only building things that are linking license compatibleTechnical Team/Use Cases/2.0/Decorating an already produces and signed SPDX dataset with extension dataTechnical Team/Use Cases/2.0/Downstream consumers contributing patches to provide SPDX data to an upstream that doesnt have it
Technical Team/Use Cases/2.0/Downstream consumers contributing patches to provide corrections to SPDX data for an upstream that does have itTechnical Team/Use Cases/2.0/Embedded Images (e.g. router images, switch images)Technical Team/Use Cases/2.0/Graveyard
Technical Team/Use Cases/2.0/Intermediate packager adds patches to upstream source that does not provide SPDX dataTechnical Team/Use Cases/2.0/Intermediate packager adds patches to upstream source that provides SPDX dataTechnical Team/Use Cases/2.0/Intermediate packager adds someone elses patches to upstream source that does not provide SPDX data
Technical Team/Use Cases/2.0/Intermediate packager adds someone elses patches to upstream source that provides SPDX dataTechnical Team/Use Cases/2.0/Intermediate packager builds binary package from upstream source that does not provides SPDX dataTechnical Team/Use Cases/2.0/Intermediate packager builds binary package from upstream source that provides SPDX data
Technical Team/Use Cases/2.0/Intermediate packager builds source package from upstream source that does not provide SPDX dataTechnical Team/Use Cases/2.0/Intermediate packager builds source package from upstream source that provides SPDX dataTechnical Team/Use Cases/2.0/Intermediate packager subsetting upstream source that does not provide SPDX data
Technical Team/Use Cases/2.0/Intermediate packager subsetting upstream source that provides SPDX dataTechnical Team/Use Cases/2.0/License list extensionTechnical Team/Use Cases/2.0/Linux Distros
Technical Team/Use Cases/2.0/Low cost SPDX fileTechnical Team/Use Cases/2.0/Patch provider provides SPDX data for the patchTechnical Team/Use Cases/2.0/Patch provider provides SPDX data for the patch indicating it is licensed however the hell its applied
Technical Team/Use Cases/2.0/Patch provider provides patch subject to existing SPDX data of projectTechnical Team/Use Cases/2.0/Producing valid SPDX files in the face of missing dataTechnical Team/Use Cases/2.0/Project maintainer incorporates another project by including binary
Technical Team/Use Cases/2.0/Project maintainer incorporates another project by including sourceTechnical Team/Use Cases/2.0/Project maintainer pulling individual files out of another project (subsetting)Technical Team/Use Cases/2.0/Provide sufficient data to allow consumer to comply with licenses on redistribution
Technical Team/Use Cases/2.0/Reference ImplementationsTechnical Team/Use Cases/2.0/SPDX data indicating subset of the source that made it into a particular binary or binary packageTechnical Team/Use Cases/2.0/Subsetting out only the shippable bits of stuff coming from an SDK
Technical Team/Use Cases/2.0/Third party produces bill of materials for software packageTechnical Team/Use Cases/2.0/Upstream maintainer preparing release artifacts (including SPDX data)Technical Team/Use Cases/2.0/Upstream maintainer providing SPDX data
Technical Team/Use Cases/2.0/Upstream maintainer providing SPDX data at a URLTechnical Team/Use Cases/2.0/Upstream maintainer providing SPDX data in SCMTechnical Team/Use Cases/2.0/Upstream maintainer providing SPDX data in source archive
Retrieved from "https://wiki.spdx.org/view/Special:PrefixIndex"