cmader/qSKOS — Issue #6: Distinction basic statistics / quality metrics + proposed command line usage
Author: behas
Created: 2012-03-06 14:22:40+00:00
State: open

Basic statistics (e.g., all concepts) are now in the list of quality criteria. Does this make sense? Wouldn't it be better to distinguish between simple statistical and quality measures at least on the command line?

Internally you can implement them as you want, probably analogous to the quality measures, because they also compute something and produce a report, like the quality measures.

But on the command line I recommend to make a distinction. Here is a proposal for usage guidelines:

# Usage

Print qSKOS usage instructions:

java -jar qSKOS-0.0.1.one.jar

Get a basic statistical summary for a given SKOS vocabulary:

java -jar qSKOS-0.0.1.one.jar vocabulary.rdf (later we can use the non-option case for interactive usage)
java -jar qSKOS-0.0.1.one.jar -s vocabulary.rdf

Get a list of available SKOS quality measures:

java -jar qSKOS-0.0.1.one.jar -l vocabulary.rdf

Compute a certain quality measure by passing its ID:

java -jar qSKOS-0-0.1.one.jar -m lc vocabulary.rdf

Compute a sequence of quality measures by passing their IDs as whitespace-separated list:

java -jar qSKOS-0-0.1.one.jar -m lc wcc vocabulary.rdf

Generate a statistical summary and compute all available quality measures for a given SKOS vocabulary:

java -jar qSKOS-0-0.1.one.jar -a vocabulary.rdf