Liking cljdoc? Tell your friends :D

spdx.expressions

SPDX license expression functionality. This functionality is bespoke (it does not use the parser in Spdx-Java-Library).

SPDX license expression functionality. This functionality is bespoke (it does
not use the parser in `Spdx-Java-Library`).
raw docstring

compound?clj

(compound? s)
(compound? s opts)

Is s (a String) a 'compound' SPDX license expression (i.e. one that contains at least one AND or OR operator)? Returns nil if s not a valid SPDX expression.

The optional opts map is as for parse.

Is `s` (a `String`) a 'compound' SPDX license expression (i.e. one that
contains at least one AND or OR operator)?  Returns `nil` if `s` not a valid
SPDX expression.

The optional `opts` map is as for `parse`.
sourceraw docstring

extract-idsclj

(extract-ids parse-result)
(extract-ids parse-result
             {:keys [include-or-later?] :or {include-or-later? false} :as opts})

Extract all SPDX ids (as a set of Strings) from parse-result.

The optional opts map has these keys:

  • :include-or-later? (boolean, default false) - controls whether the output includes the 'or later' indicator (+) after license ids that have that designation in the parse tree.
Extract all SPDX ids (as a set of `String`s) from `parse-result`.

The optional `opts` map has these keys:

* `:include-or-later?` (`boolean`, default `false`) - controls whether the output
  includes the 'or later' indicator (`+`) after license ids that have that
  designation in the parse tree.
sourceraw docstring

init!clj

(init!)

Initialises this namespace upon first call (and does nothing on subsequent calls), returning nil. Consumers of this namespace are not required to call this fn, as initialisation will occur implicitly anyway; it is provided to allow explicit control of the cost of initialisation to callers who need it.

Note: this method may have a substantial performance cost.

Initialises this namespace upon first call (and does nothing on subsequent
calls), returning `nil`. Consumers of this namespace are not required to call
this fn, as initialisation will occur implicitly anyway; it is provided to
allow explicit control of the cost of initialisation to callers who need it.

Note: this method may have a substantial performance cost.
sourceraw docstring

normaliseclj

(normalise s)
(normalise s opts)

Normalises an SPDX expression, by running it through parse then unparse. Returns nil if s is not a valid SPDX expression.

opts are as for parse

Normalises an SPDX expression, by running it through [[parse]] then
[[unparse]].  Returns `nil` if `s` is not a valid SPDX expression.

`opts` are as for [[parse]]
sourceraw docstring

parseclj

(parse s)
(parse s
       {:keys [normalise-gpl-ids? case-sensitive-operators?
               collapse-redundant-clauses?]
        :or {normalise-gpl-ids? true
             case-sensitive-operators? false
             collapse-redundant-clauses? true}
        :as opts})

Attempt to parse s (a String) as an SPDX license expression, returning a data structure representing the parse tree, or nil if it cannot be parsed.

The optional opts map has these keys:

  • :normalise-gpl-ids? (boolean, default true) - controls whether deprecated 'historical oddity' GPL family ids in the expression are normalised to their non-deprecated replacements as part of the parsing process.
  • :case-sensitive-operators? (boolean, default false) - controls whether operators in expressions (AND, OR, WITH) are case-sensitive (spec-compliant, but strict) or not (non-spec-compliant, lenient).
  • :collapse-redundant-clauses? (boolean, default true) - controls whether redundant clauses (e.g. "Apache-2.0 AND Apache-2.0") are collapsed during parsing.

Notes:

  • The parser always normalises SPDX ids to their canonical case e.g. aPAcHe-2.0 -> Apache-2.0
  • The parser always removes redundant grouping e.g. (((((Apache-2.0)))))) -> Apache-2.0
  • The parser synthesises grouping when needed to make SPDX license expressions' precedence rules explicit (see the relevant section within annex D of the SPDX specification for details).
  • The default opts result in parsing that is more lenient than the SPDX specification and is therefore not strictly spec compliant. You can enable strictly spec compliant parsing by setting normalise-gpl-ids? to false and case-sensitive-operators? to true.

Examples (assuming default options):

(parse "Apache-2.0")
{:license-id "Apache-2.0"}

(parse "apache-2.0+")
{:license-id "Apache-2.0" :or-later? true}  ; Note id case correction

(parse "GPL-2.0+")
{:license-id "GPL-2.0-or-later"}  ; Note GPL-family id normalisation

(parse "GPL-2.0 WITH Classpath-exception-2.0")
{:license-id "GPL-2.0-only"
 :license-exception-id "Classpath-exception-2.0"}

(parse "CDDL-1.1 or (GPL-2.0+ with Classpath-exception-2.0)")
[:or
 {:license-id "CDDL-1.1"}
 {:license-id "GPL-2.0-or-later"
  :license-exception-id "Classpath-exception-2.0"}]

(parse "DocumentRef-foo:LicenseRef-bar")
{:document-ref "foo"
 :license-ref "bar"}

(parse "Apache-2.0 with DocumentRef-foo:AdditionRef-bar")
{:license-id "Apache-2.0"
 :addition-document-ref "foo"
 :addition-ref "bar"}
Attempt to parse `s` (a `String`) as an [SPDX license expression](https://spdx.github.io/spdx-spec/v3.0/annexes/SPDX-license-expressions/),
returning a data structure representing the parse tree, or `nil` if it cannot
be parsed.

The optional `opts` map has these keys:

* `:normalise-gpl-ids?` (`boolean`, default `true`) - controls whether
  deprecated 'historical oddity' GPL family ids in the expression are
  normalised to their non-deprecated replacements as part of the parsing
  process.
* `:case-sensitive-operators?` (`boolean`, default `false`) - controls whether
  operators in expressions (`AND`, `OR`, `WITH`) are case-sensitive
  (spec-compliant, but strict) or not (non-spec-compliant, lenient).
* `:collapse-redundant-clauses?` (`boolean`, default `true`) - controls
  whether redundant clauses (e.g. "Apache-2.0 AND Apache-2.0") are
  collapsed during parsing.

Notes:

* The parser always normalises SPDX ids to their canonical case
  e.g. `aPAcHe-2.0` -> `Apache-2.0`
* The parser always removes redundant grouping
  e.g. `(((((Apache-2.0))))))` -> `Apache-2.0`
* The parser synthesises grouping when needed to make SPDX license
  expressions' precedence rules explicit (see [the relevant section within
  annex D of the SPDX specification](https://spdx.github.io/spdx-spec/v3.0/annexes/SPDX-license-expressions/#d45-order-of-precedence-and-parentheses)
  for details).
* The default `opts` result in parsing that is more lenient than the SPDX
  specification and is therefore not strictly spec compliant.  You can enable
  strictly spec compliant parsing by setting `normalise-gpl-ids?` to `false`
  and `case-sensitive-operators?` to `true`.

Examples (assuming default options):

```clojure
(parse "Apache-2.0")
{:license-id "Apache-2.0"}

(parse "apache-2.0+")
{:license-id "Apache-2.0" :or-later? true}  ; Note id case correction

(parse "GPL-2.0+")
{:license-id "GPL-2.0-or-later"}  ; Note GPL-family id normalisation

(parse "GPL-2.0 WITH Classpath-exception-2.0")
{:license-id "GPL-2.0-only"
 :license-exception-id "Classpath-exception-2.0"}

(parse "CDDL-1.1 or (GPL-2.0+ with Classpath-exception-2.0)")
[:or
 {:license-id "CDDL-1.1"}
 {:license-id "GPL-2.0-or-later"
  :license-exception-id "Classpath-exception-2.0"}]

(parse "DocumentRef-foo:LicenseRef-bar")
{:document-ref "foo"
 :license-ref "bar"}

(parse "Apache-2.0 with DocumentRef-foo:AdditionRef-bar")
{:license-id "Apache-2.0"
 :addition-document-ref "foo"
 :addition-ref "bar"}
```
sourceraw docstring

parse-with-infoclj

(parse-with-info s)
(parse-with-info s
                 {:keys [normalise-gpl-ids? case-sensitive-operators?
                         collapse-redundant-clauses?]
                  :or {normalise-gpl-ids? true
                       case-sensitive-operators? false
                       collapse-redundant-clauses? true}})

As for parse, but returns an instaparse parse error if parsing fails, instead of nil.

opts are as for parse

As for [[parse]], but returns an [instaparse parse error](https://github.com/Engelberg/instaparse#parse-errors)
if parsing fails, instead of `nil`.

`opts` are as for [[parse]]
sourceraw docstring

simple?clj

(simple? s)
(simple? s opts)

Is s (a String) a 'simple' SPDX license expression (i.e. one that contains no AND or OR operators, though it may contain a WITH operator)? Returns nil if s not a valid SPDX expression.

The optional opts map is as for parse.

Is `s` (a `String`) a 'simple' SPDX license expression (i.e. one that
contains no AND or OR operators, though it may contain a WITH operator)?
Returns `nil` if `s` not a valid SPDX expression.

The optional `opts` map is as for `parse`.
sourceraw docstring

unparseclj

(unparse parse-result)

Turns a valid parse-result (i.e. obtained from parse) back into an SPDX expression (a String), or nil if parse-result is nil. Results are undefined for invalid parse trees.

Turns a valid `parse-result` (i.e. obtained from [[parse]]) back into an
SPDX expression (a `String`), or `nil` if `parse-result` is `nil`.  Results
are undefined for invalid parse trees.
sourceraw docstring

valid?clj

(valid? s)
(valid? s
        {:keys [case-sensitive-operators?]
         :or {case-sensitive-operators? false}})

Is s (a String) a valid SPDX license expression?

Note: if you intend to parse s if it's valid, it's more efficient to call parse directly and check for a nil result instead of calling this method first (doing so avoids double parsing).

The optional opts map has these keys:

  • :case-sensitive-operators? (boolean, default false) - controls whether operators in expressions (AND, OR, WITH) are case-sensitive (spec-compliant, but strict) or not (non-spec-compliant, lenient).
Is `s` (a `String`) a valid SPDX license expression?

Note: if you intend to parse `s` if it's valid, it's more efficient to call
[[parse]] directly and check for a `nil` result instead of calling this method
first (doing so avoids double parsing).

The optional `opts` map has these keys:

* `:case-sensitive-operators?` (`boolean`, default `false`) - controls whether
  operators in expressions (`AND`, `OR`, `WITH`) are case-sensitive
  (spec-compliant, but strict) or not (non-spec-compliant, lenient).
sourceraw docstring

cljdoc is a website building & hosting documentation for Clojure/Script libraries

× close