Indicates a rule that is invoked with the current query result as predefined variable bindings. The result returned is the result of the rule invocation.
This property is used with minim:ExistsTest to indicate a further query that is used to test for the existence of required metadata related to the results so far retrieved.
Supplies a minim:Checklist to be associated with some target resource. The subject of this property may be a target resource to which the checklist may be applied, or some arbitrary resource used as a collection of checklists, in which case the checklist itself should include a minim:forTargetTemplate property that is used in the selection of a checklist for some evaluation.
indicates a requirement is optional for a checklist to be satisfied. Failure to satisfy a MAY requirement is not considered to be indicative of any problem.
indicates a requirement that MUST be satisfied for a checklist to be satisfied
Place holder for minim:hasMustRequirement, minim:hasShouldRequirement or minim:hasMayRequirement
indicates a requirement is not mandatory for a checklist to be satisfied, but which is strongly recommended. Failure to satisfy a SHOULD requirement could be indicative of a problem.
Indicates a rule that, when its test evaluates to True, indicates that a requirement is satisfied.
Used with minim:QueryTestRule to create an additional variable binding that is a list of values from every match of the probe query. The list is available to report templates, but not in any sub-rules that may be invoked.
Like minim:list, but collects values from probe queries for which the corresponding query result test is failed.
Like minim:list, but collects values from probe queries for which the corresponding query result test is passed.
Indicates a rule that is invoked with the current query result as predefined variable bindings. The result returned is success if the rule invocation fails, otherwise failure if the rule succeeds.
This property indicates a query used to extract information from an RDF graph for requirement testing. In the current design, the only form of query defined is a SPARQL query, but other forms may be introduced later.
Indicates a minim:Model to be used to perform checklist evaluation for the indicated target resource to be suitable for the indicated purpose.
This property is used to specify a URI template (cf. http://tools.ietf.org/html/rfc6570) that is in turn used to construct the URI of resource that is tested for inclusion in the current RO aggregation. The test makes sense only for evaluations performed in the context provided by a Research Object.
When collecting a list of query value results, indicates a variable that is bound to the list of collected values.
When collecting a list of query value results, indicates a variable whose various bindings are collected.
This property indicates a command to be issued to test the software environment
Supplies a string which describes a purpose for which checklist evaluation of the target resource is to be performed. Note that a purpose is implicit in a checklist object itself, so the purpose is not treated as a separate resource, or given a separate URI. Rather, this string serves as a label or keyword that can be used in a user interface.
Supplies a URI template that is expanded using predefined variable {targetro} to refer to the Research Object resource targeted by a checklist evaluation (typically, the URI template used is '{+targetro}'). Future implementations may provide alternative variables that may be used in a URI template to construct the URI of a resource to be targeted.
This property indicates a graph to be queried, by way of a URI template that is expanded using any currently result variable bindings. This is the mechanism whereby metadata from an RO may be compared with metadata from external resources.
This property is used to specify a URI template (cf. http://tools.ietf.org/html/rfc6570) that is in turn used to construct the URI of resource to be tested for accessibility (liveness).
This property is used with minim:CardinalityTest to indicate maximum number of distinct results that are required for a cardinality test to be satisfied. Note that minim:min and minim:max can be used together to define an exact cardinality or cardinality range test.
This property is used with minim:CardinalityTest to indicate minimum number of distinct results that are required for a cardinality test to be satisfied. Note that minim:min and minim:max can be used together to define an exact cardinality or cardinality range test.
This property indicates a regular expression that is required to be matched by the output from the command used to test the software environment.
This property is used with minim:SparqlQuery to indicate a result modifier (e.g. ORDER BY, GROUP BY, etc.) that is applied to the results results obtained to matching the query pattern. Using result modifiers can make it easier to produce consistent diagnostic information.
A value that is used to order the requirements in a checklist for reporting purpose. It has no effect on the overall outcome of a checklist evaluation.
A template string that is used to report the evaluation of a rule. It has no effect on the overall outcome of a checklist evaluation. Query results and other values are nterpolated into the resulting report string by embedded codes of the form '%(varname)s' (Python format string style).
A template string that is used to report the failure of a rule, overriding any minim:show value that may be present. It has no effect on the overall outcome of a checklist evaluation. Query results and other values are interpolated into the resulting report string by embedded codes of the form '%(varname)s' (Python format string style).
A template string that is used to report a query rule whose probe query matches no values. In such circumstances, it overrides any minim:show value that may be present Previous query results and other values are nterpolated into the resulting report string by embedded codes of the form '%(varname)s' (i.e. Python format string style).
A template string that is used to report the success of a rule, overriding any minim:show value that may be present. It has no effect on the overall outcome of a checklist evaluation. Query results and other values are interpolated into the resulting report string by embedded codes of the form '%(varname)s' (Python format string style).
This property indicates a SPARQL query pattern (such as would appear in a SPARQL WHERE clause) that is used to query the content of an RDF graph.
Test if a specified resource is accessible (live). The resource URI is constructed by using the corresponding query result to provide values for variables in an expansion of the supplied URI template (cf. http://tools.ietf.org/html/rfc6570)
Test if a specified resource is part of an RO aggregation. The resource URI is constructed by using the corresponding query result to provide values for variables in an expansion of the supplied URI template (cf. http://tools.ietf.org/html/rfc6570)
Tests the number of results returned by a query
A checklist object indicates a minim:Model to be satisfied if a target resource is to be considered suitable for some specific purpose. As such, it links a target resource and a purpose for which it might be used with a minim:Model that must be satisfied for the resource to be considered fit for that purpose. A Checklist may be associated directly with a target resource as the subject of a minim:hasChecklist statement, or may be associated indirectly via a URI template that is the object of an associated minim:forTargetTemplate statement. The latter form is is more flexible as it allows a given checklist to be more easily used with multiple resources.
Tests to see if a supplied query is satisfied by available metadata, matching the query results retrieved so far. This test is a short-cut for a minim:RuleTest that refers to a 'min 1' cardinality test. @@TBD: keep this or drop it as redundant?
A Minim model collects a number of requirements, and associates each with a MUST, SHOULD or MAY requirement level.
Query an RDF graph and return values that match the supplied pattern. The results returned are a set of results, where each is a set of query variable bindings corresponding to a single match of the pattern, and the entire result set contains all distinct matches achieved. Specific query forms are subclasses of this class. Possible subclass types might include patterns based on SPARQL, SPIN, OWL and maybe other data-matching patterns.
A test of a query result used in conjunction with a Query value to make a QueryTestRule. Any query tests should be declared as a subclass of this.
Generalized rule consisting of a query to extract information from an RDF graph, and a test that is applied to the results from applying that query. The query is assumed to return a set of results, each of which contains one ormore variable bindings. This currently available implementation uses a SPARQL query, but in principle other forms of query are possible, such as an OWL class expression. If a minim:graph value is supplied, it supplies a URI template used to identify the graph to be queried, otherwise the supplied RO annotation graph is queried.
A Minim requirement, whose satisfaction is determined by evaluation of the indicated rule. The minim:seq value is used to order the requirement results returned, to allow more consistent reporting of results.
This is a generic placeholder for any rule which is evaluated to determine whether or not a Minim requirement is satisfied. The various checklist item rules should be declared as subclasses of this rule.
Invokes a specified rule with the current result as predefined variable bindings. The result returned is success if the rule invocation fails, otherwise failure if the rule succeeds.
Invokes a specified rule with the current result as predefined variable bindings. The result returned is the result of the rule invocation. This recursive invocation of minim:Rule allows chains of tests to be assembled when a single test alone does not suffice.
A checklist requirement rule that tests the local software environment provides some specified capability or meets some specified requirement. The test works by issuing a command and testing to see if the response matches asupplied regular expression.
Query an RDF graph and returns results that match the supplied SPARQL query body. The results returned are a set of results, where each result is a set of query variable bindings corresponding to a single match of the query, and the entire result set contains all distinct matches achieved. The minim:result_mod value, if present, is added as a query result modifier, and may be used, among other things, to obtain results returned in a consistent oder for better diagnostics.
A node that references a pair of variable names used when assembling a list of matched values from a probe query.