NOTE: For details of the properties see descriptions in the ontology.
return all data fields of a specific MOSH
- find or exclude MOSHs with specific
patentClass(multiple)
for MOSHs:
- search for keywords in
function(free text) - filter for specific
standardprojectStageattestation(boolean: is-empty)certificate(boolean: is-empty)
- Option 1: filter for specific
patentClass&/tsdcID - Option 2: filter for copyleft-categories of licenses by calling a sub-library with
spdxLicense
- find or exclude MOSHs with specific IETF language tag (
language) (multiple)
- return versions and forks of a MOSH
-
Option 1: compare
spdxLicenseof a specific MOSH with a list of OSHWA-compliant licenses calling a sub-library -
Option 2: check compatibility of licenses of specific MOSHs by calling a sub-library with
spdxLicense
- check whether or not full packaging would include entries for
okhvnamerepositoryversionlicensorspdxLicense- while checking for OSHWA-compliance
functiontsdcID- design files (hence a
sBoMis a prerequisiste)namequantity- for MOSHs included
sourceexport
- for POSHs included
sourceexport
- for STDs included
stdReference
- for BUYs included
buyReference
- returns a boolean ("probably complete", "probably uncomplete")
- add a report of what's missing in case one ore more of the mentioned data fields are empty
for MOSHs:
- Variant 1:
- return list of all
fileFormatused insource
- return list of all
- Variant 2:
- user input is a selection of software
- get list of supported file formats of selected software from sub-library
- check whether files linked as
sourcecontain afileFormatthat is not part of this list - return boolean
- add a list of POSHs/MOSHs including a unsupported
fileFormatindicating the corresponding file (tree-like list)
- add a list of POSHs/MOSHs including a unsupported
- options for both variants:
- Option 1: exclude the
sourceof submodules - Option 2: include the
sourceof submodules
- Option 1: exclude the
- get number of MOSHs that include a seleted component MOSH/POSH/STD/BUY in their
sBoM - Option 1: split number by
patentClassof the MOSHs using the selected component - Option 2: add a list (
name,versionand internal wikibase-link to the MOSHs using the selected component)
A package of a certain MOSH includes the following.
NOTE 1: The query may give the option to load submodules (other included MOSHs) or just link to them. In case of loading them, naturally the same requirements apply as for any other MOSH.
NOTE 2: Packages may be (most likely) incomplete. Empty fields are gaps in the resulting package.
- general information
- get version of metadata standard used
okhv
- identification
namerepositoryversionforkOflanguage
- legal
licensorspdxLicensealternativeLicense
- development stage
developmentStageattestationcertificate
- basic description
patentClasstsdcIDstandardfunctionreadmeimagefunctionalMetadataproductionMetadata
- get version of metadata standard used
- design files (=tree with links/references)
namequantity- additionally:
- MOSH (submodules)
repository&versionwhen just referencing submodules- full package when loading submodules
- POSH
sourceexport
- STD
stdReference
- BUY
buyReference
- MOSH (submodules)
= p01 full package without export fields
= p01 full package without source fields