eyeling 1.27.5 → 1.27.7

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -181,7 +181,7 @@ Instead of “printing during reasoning”, the program emits facts like:
181
181
 
182
182
  - `log:outputString "..."`
183
183
 
184
- Then Eyeling’s `--strings` / `-r` mode collects and sorts them deterministically. ([Handbook Inside Eyeling][5])
184
+ Then Eyeling’s `--strings` / `-r` mode collects and sorts them deterministically. ([README guide inside Eyeling][5])
185
185
 
186
186
  To force ranking, it uses an **inverse score key**:
187
187
 
@@ -248,4 +248,4 @@ This file is a compact demo of:
248
248
  [2]: https://www.w3.org/TR/odrl-vocab/ 'ODRL Vocabulary & Expression 2.2'
249
249
  [3]: https://dev.dpvcg.org/dpv/modules/risk 'Risk and Impact Assessment'
250
250
  [4]: https://w3c.github.io/N3/spec/ 'Notation3 Language'
251
- [5]: https://eyereasoner.github.io/eyeling/HANDBOOK 'Handbook Inside Eyeling'
251
+ [5]: https://eyereasoner.github.io/eyeling/ 'README guide inside Eyeling'
@@ -1,6 +1,6 @@
1
1
  # RDF Message Cold Chain Recall
2
2
 
3
- This deck follows a cold-chain stream where the cost of a wrong conclusion is concrete: either release a shipment or quarantine it. The [rules](../rdf-message-cold-chain-recall.n3) replay the LDES [message log input](../input/rdf-message-cold-chain-recall.trig), the [golden output](../output/rdf-message-cold-chain-recall.md) records the repaired decision, and the [handbook section](https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r) explains how `-r` exposes RDF Message boundaries to the rules.
3
+ This deck follows a cold-chain stream where the cost of a wrong conclusion is concrete: either release a shipment or quarantine it. The [rules](../rdf-message-cold-chain-recall.n3) replay the LDES [message log input](../input/rdf-message-cold-chain-recall.trig), the [golden output](../output/rdf-message-cold-chain-recall.md) records the repaired decision, and the [README section](https://eyereasoner.github.io/eyeling/#rdf-message-logs) explains how `-r` exposes RDF Message boundaries to the rules.
4
4
 
5
5
  ## Why this example exists
6
6
 
@@ -1,6 +1,6 @@
1
1
  # RDF Message Logs in Eyeling — from stream to reasoning
2
2
 
3
- This deck reads alongside the [rules](../rdf-message-flow.n3) and the replayed [message log input](../input/rdf-message-flow.trig): the [golden output](../output/rdf-message-flow.md) shows what Eyeling derives once `-r` has exposed the RDF Message envelopes and payload graphs. The [handbook section](https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r) explains that replay step in more detail.
3
+ This deck reads alongside the [rules](../rdf-message-flow.n3) and the replayed [message log input](../input/rdf-message-flow.trig): the [golden output](../output/rdf-message-flow.md) shows what Eyeling derives once `-r` has exposed the RDF Message envelopes and payload graphs. The [README section](https://eyereasoner.github.io/eyeling/#rdf-message-logs) explains that replay step in more detail.
4
4
 
5
5
  The goal is to show, in plain language, how Eyeling can now read an RDF Message Log directly instead of asking the example data to describe its own message envelopes by hand.
6
6
 
@@ -1,6 +1,6 @@
1
1
  # RDF Message LDES Incremental Repair
2
2
 
3
- This deck walks through a stream that is large enough to make full recomputation unattractive. The [rules](../rdf-message-ldes-incremental.n3) consume the replayed LDES [message log input](../input/rdf-message-ldes-incremental.trig), the [golden output](../output/rdf-message-ldes-incremental.md) shows the incremental repair result, and the [handbook section](https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r) explains how `-r` turns RDF Message boundaries into facts for the rules.
3
+ This deck walks through a stream that is large enough to make full recomputation unattractive. The [rules](../rdf-message-ldes-incremental.n3) consume the replayed LDES [message log input](../input/rdf-message-ldes-incremental.trig), the [golden output](../output/rdf-message-ldes-incremental.md) shows the incremental repair result, and the [README section](https://eyereasoner.github.io/eyeling/#rdf-message-logs) explains how `-r` turns RDF Message boundaries into facts for the rules.
4
4
 
5
5
  ## Why this example exists
6
6
 
@@ -45,7 +45,7 @@ MESSAGE
45
45
 
46
46
  Eyeling's `-r` mode preserves those message boundaries as `eymsg:` envelopes and payload graphs. The rules inspect payloads with `log:includes`, so each member remains scoped to the message that emitted it.
47
47
 
48
- Handbook: <https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r>
48
+ README: <https://eyereasoner.github.io/eyeling/#rdf-message-logs>
49
49
 
50
50
  ## Why LDES helps
51
51
 
@@ -1,6 +1,6 @@
1
1
  # RDF Message window repair — fixing an open/closed door conflict
2
2
 
3
- This deck follows a small RDF Message window where one door is reported both open and closed. The [rules](../rdf-message-window-repair.n3) inspect the replayed [message log input](../input/rdf-message-window-repair.trig), the [golden output](../output/rdf-message-window-repair.md) shows the repaired conclusion, and the [handbook section](https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r) explains how `-r` exposes message payloads without silently merging them.
3
+ This deck follows a small RDF Message window where one door is reported both open and closed. The [rules](../rdf-message-window-repair.n3) inspect the replayed [message log input](../input/rdf-message-window-repair.trig), the [golden output](../output/rdf-message-window-repair.md) shows the repaired conclusion, and the [README section](https://eyereasoner.github.io/eyeling/#rdf-message-logs) explains how `-r` exposes message payloads without silently merging them.
4
4
 
5
5
  The goal is to show how Eyeling can reason over a replayed RDF Message Log, keep message boundaries visible, detect an inconsistency in a sliding window, and materialize a repaired conclusion instead of blindly merging contradictory facts.
6
6
 
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-cold-chain-recall.n3 examples/input/rdf-message-cold-chain-recall.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # It serializes one LDES configuration message followed by forty-eight telemetry
13
13
  # member messages. A consumer checkpoint at sequence 42 lets the N3 rules skip
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-flow.n3 examples/input/rdf-message-flow.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # It is a parser-level RDF Message Log using the RDF 1.2 Messages draft syntax:
13
13
  # VERSION "1.2-messages" selects message-log parsing and MESSAGE delimiters
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-ldes-incremental.n3 examples/input/rdf-message-ldes-incremental.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # It serializes one LDES configuration message followed by forty append-only
13
13
  # LDES member messages. A consumer checkpoint at sequence 34 lets the N3 rules
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-microgrid.n3 examples/input/rdf-message-microgrid.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # The scene is a clinic operating as an islanded microgrid after a storm. The
13
13
  # data arrives as a true RDF Message Log: life-safety loads, power status,
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-window-repair.n3 examples/input/rdf-message-window-repair.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # The log models a fire-door monitoring ABox stream. Message 1 is stable
13
13
  # configuration/TBox-like policy. Messages 2-5 are ordered ABox assertions. The
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-messages.n3 examples/input/rdf-messages.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # It is a true RDF Message Log. VERSION "1.2-messages" tells Eyeling to parse
13
13
  # MESSAGE delimiters as message boundaries before ordinary N3 reasoning starts.
@@ -32,7 +32,7 @@
32
32
  # Notes
33
33
  # -----
34
34
  # - This is a direct, concrete 2x2 example, not a general matrix library.
35
- # - The structure follows the Eyeling handbook style:
35
+ # - The structure follows the Eyeling README style:
36
36
  # Facts -> Logic -> Presentation -> Checks
37
37
  # - The output is organized in ARC form:
38
38
  # Answer -> Reason Why -> Check
@@ -38,7 +38,7 @@
38
38
  # - This is an illustrative example, not legal advice or a compliance checklist.
39
39
  #
40
40
  # References
41
- # - Eyeling handbook: https://eyereasoner.github.io/eyeling/HANDBOOK
41
+ # - Eyeling README: https://eyereasoner.github.io/eyeling/
42
42
  # - ODRL vocab: https://www.w3.org/TR/odrl-vocab/
43
43
  # - DPV core: https://w3id.org/dpv
44
44
  # - DPV-PD: https://w3id.org/dpv/pd
@@ -23,7 +23,7 @@
23
23
  #
24
24
  # References
25
25
  # - N3 spec: https://w3c.github.io/N3/spec/
26
- # - Eyeling builtins: https://eyereasoner.github.io/eyeling/HANDBOOK#ch11
26
+ # - Eyeling builtins: https://eyereasoner.github.io/eyeling/#built-ins
27
27
  # - ODRL vocab: https://www.w3.org/TR/odrl-vocab/
28
28
  # - DPV risk module: https://dev.dpvcg.org/dpv/modules/risk
29
29
  # - DPV-RISK: https://w3id.org/dpv/risk
@@ -35,7 +35,7 @@
35
35
  #
36
36
  # References
37
37
  # - N3 specification: https://w3c.github.io/N3/spec/
38
- # - Eyeling builtins handbook: https://eyereasoner.github.io/eyeling/HANDBOOK#ch11
38
+ # - Eyeling built-ins README: https://eyereasoner.github.io/eyeling/#built-ins
39
39
  # - ODRL model/vocabulary: https://www.w3.org/TR/odrl-model/
40
40
  # =====================================================================================
41
41
 
@@ -32,7 +32,7 @@
32
32
  #
33
33
  # References
34
34
  # - N3 specification: https://w3c.github.io/N3/spec/
35
- # - Eyeling builtins handbook: https://eyereasoner.github.io/eyeling/HANDBOOK#ch11
35
+ # - Eyeling built-ins README: https://eyereasoner.github.io/eyeling/#built-ins
36
36
  # - ODRL model/vocabulary: https://www.w3.org/TR/odrl-model/
37
37
  # =======================================================================================
38
38
 
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-cold-chain-recall.n3 examples/input/rdf-message-cold-chain-recall.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # This example is meant to be operationally obvious: a cold-chain shipment has
13
13
  # many historical telemetry messages, a checkpoint says which prefix was already
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-flow.n3 examples/input/rdf-message-flow.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # Motivation
13
13
  # ----------
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-ldes-incremental.n3 examples/input/rdf-message-ldes-incremental.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # This example combines two streaming ideas:
13
13
  #
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-microgrid.n3 examples/input/rdf-message-microgrid.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # A clinic is running as an islanded microgrid after a storm. Several small
13
13
  # systems send RDF data: one message describes life-safety loads, another
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-message-window-repair.n3 examples/input/rdf-message-window-repair.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # This example is inspired by incremental, inconsistency-resilient reasoning over
13
13
  # sliding ABox streams. The input is a true RDF Message Log: each MESSAGE
@@ -6,8 +6,8 @@
6
6
  #
7
7
  # eyeling -r examples/rdf-messages.n3 examples/input/rdf-messages.trig
8
8
  #
9
- # See the handbook section on RDF Message Log replay under -r:
10
- # https://eyereasoner.github.io/eyeling/HANDBOOK#rdf-message-log-replay-under--r
9
+ # See the README section on RDF Message Log replay under -r:
10
+ # https://eyereasoner.github.io/eyeling/#rdf-message-logs
11
11
  #
12
12
  # Motivation
13
13
  # ----------
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "eyeling",
3
- "version": "1.27.5",
3
+ "version": "1.27.7",
4
4
  "description": "A minimal Notation3 (N3) reasoner in JavaScript.",
5
5
  "main": "./index.js",
6
6
  "keywords": [
@@ -21,7 +21,6 @@
21
21
  "files": [
22
22
  "LICENSE.md",
23
23
  "README.md",
24
- "HANDBOOK.md",
25
24
  "eyeling-builtins.ttl",
26
25
  "eyeling.js",
27
26
  "index.js",
@@ -48,7 +47,7 @@
48
47
  "test:playground": "node test/playground.test.js",
49
48
  "test:package": "node test/package.test.js",
50
49
  "pretest": "npm run build && npm run test:packlist",
51
- "test": "npm run test:api && npm run test:builtins && npm run test:examples && npm run test:examples:proof && npm run test:manifest && npm run test:playground",
50
+ "test": "npm run test:api && npm run test:builtins && npm run test:examples && npm run test:examples:proof && npm run test:manifest && npm run rdf12 && npm run test:playground",
52
51
  "posttest": "npm run test:package",
53
52
  "preversion": "npm test",
54
53
  "postversion": "git push origin HEAD --follow-tags",