eyeling 1.16.4 → 1.17.0

package/examples/ill-formed-literals.n3

@@ -0,0 +1,195 @@
+# ==========================
+# Ill-formed literal checker
+#
+# Datatypes covered
+# - xsd:boolean
+# - integer family
+# - xsd:decimal
+# - xsd:float / xsd:double
+# - xsd:date
+# - xsd:dateTime
+# - xsd:duration
+# ==========================
+
+@prefix :       <http://example.org/#>.
+@prefix list:   <http://www.w3.org/2000/10/swap/list#>.
+@prefix log:    <http://www.w3.org/2000/10/swap/log#>.
+@prefix math:   <http://www.w3.org/2000/10/swap/math#>.
+@prefix string: <http://www.w3.org/2000/10/swap/string#>.
+@prefix xsd:    <http://www.w3.org/2001/XMLSchema#>.
+
+# ---------
+# Demo data
+# ---------
+
+# well-formed examples
+:okInt       :p "42"^^xsd:integer.
+:okBool1     :p "true"^^xsd:boolean.
+:okBool2     :p "0"^^xsd:boolean.
+:okDecimal   :p "-12.50"^^xsd:decimal.
+:okDouble    :p "6.022e23"^^xsd:double.
+:okDate      :p "2025-01-31"^^xsd:date.
+:okDateTime  :p "2025-01-31T23:59:59Z"^^xsd:dateTime.
+:okDuration  :p "PT900S"^^xsd:duration.
+
+# ill-formed examples
+:badInt1      :p "abc"^^xsd:integer.
+:badInt2      :p "12.3"^^xsd:int.
+:badBool      :p "truish"^^xsd:boolean.
+:badDecimal   :p "12.3.4"^^xsd:decimal.
+:badDouble    :p "1e"^^xsd:double.
+:badDate      :p "yesterday"^^xsd:dateTime.
+:badDateTime  :p "not-a-datetime"^^xsd:dateTime.
+:badDuration  :p "not-a-duration"^^xsd:duration.
+
+# ---------------------------------
+# Rules: detect ill-formed literals
+# ---------------------------------
+
+# xsd:boolean
+{
+  ?s ?p ?lit.
+  ?lit log:rawType log:Literal.
+  (?lex xsd:boolean) log:dtlit ?lit.
+  ?lex string:notMatches "^(true|false|1|0)$".
+}
+=>
+{
+  (?s ?p ?lit)
+      :illFormedLiteral true;
+      :datatype xsd:boolean;
+      :lexicalForm ?lex;
+      :reason "invalid xsd:boolean lexical form".
+}.
+
+# integer family
+{
+  ?s ?p ?lit.
+  ?lit log:rawType log:Literal.
+  (?lex ?dt) log:dtlit ?lit.
+  ?dt list:in (
+      xsd:integer
+      xsd:long
+      xsd:int
+      xsd:short
+      xsd:byte
+      xsd:nonNegativeInteger
+      xsd:positiveInteger
+      xsd:nonPositiveInteger
+      xsd:negativeInteger
+      xsd:unsignedLong
+      xsd:unsignedInt
+      xsd:unsignedShort
+      xsd:unsignedByte
+  ).
+  ?lex string:notMatches "^[+-]?[0-9]+$".
+}
+=>
+{
+  (?s ?p ?lit)
+      :illFormedLiteral true;
+      :datatype ?dt;
+      :lexicalForm ?lex;
+      :reason "invalid integer-family lexical form".
+}.
+
+# xsd:decimal
+{
+  ?s ?p ?lit.
+  ?lit log:rawType log:Literal.
+  (?lex xsd:decimal) log:dtlit ?lit.
+  ?lex string:notMatches "^[+-]?(?:[0-9]+\\.[0-9]*|\\.[0-9]+|[0-9]+)$".
+}
+=>
+{
+  (?s ?p ?lit)
+      :illFormedLiteral true;
+      :datatype xsd:decimal;
+      :lexicalForm ?lex;
+      :reason "invalid xsd:decimal lexical form".
+}.
+
+# xsd:float / xsd:double
+{
+  ?s ?p ?lit.
+  ?lit log:rawType log:Literal.
+  (?lex ?dt) log:dtlit ?lit.
+  ?dt list:in ( xsd:float xsd:double ).
+  ?lex string:notMatches "^(?:NaN|INF|-INF|[+-]?(?:[0-9]+(?:\\.[0-9]*)?|\\.[0-9]+)(?:[eE][+-]?[0-9]+)?)$".
+}
+=>
+{
+  (?s ?p ?lit)
+      :illFormedLiteral true;
+      :datatype ?dt;
+      :lexicalForm ?lex;
+      :reason "invalid xsd:float/xsd:double lexical form".
+}.
+
+# xsd:date
+{
+  ?s ?p ?lit.
+  ?lit log:rawType log:Literal.
+  (?lex xsd:date) log:dtlit ?lit.
+  1 log:notIncludes { ?lit math:equalTo ?lit. }.
+}
+=>
+{
+  (?s ?p ?lit)
+      :illFormedLiteral true;
+      :datatype xsd:date;
+      :lexicalForm ?lex;
+      :reason "xsd:date literal is not parseable by the reasoner".
+}.
+
+# xsd:dateTime
+{
+  ?s ?p ?lit.
+  ?lit log:rawType log:Literal.
+  (?lex xsd:dateTime) log:dtlit ?lit.
+  1 log:notIncludes { ?lit math:equalTo ?lit. }.
+}
+=>
+{
+  (?s ?p ?lit)
+      :illFormedLiteral true;
+      :datatype xsd:dateTime;
+      :lexicalForm ?lex;
+      :reason "xsd:dateTime literal is not parseable by the reasoner".
+}.
+
+# xsd:duration
+{
+  ?s ?p ?lit.
+  ?lit log:rawType log:Literal.
+  (?lex xsd:duration) log:dtlit ?lit.
+  1 log:notIncludes { ?lit math:equalTo ?lit. }.
+}
+=>
+{
+  (?s ?p ?lit)
+      :illFormedLiteral true;
+      :datatype xsd:duration;
+      :lexicalForm ?lex;
+      :reason "xsd:duration literal is not parseable by the reasoner".
+}.
+
+# -----------------
+# Output projection
+# -----------------
+
+{
+  ?issue :illFormedLiteral true;
+         :datatype ?dt;
+         :lexicalForm ?lex;
+         :reason ?why.
+}
+log:query
+{
+  ?issue :datatype ?dt;
+         :lexicalForm ?lex;
+         :reason ?why.
+}.
+
+# Optional hard-fail mode:
+# { ?issue :illFormedLiteral true. } => false.

package/examples/output/auroracare.n3

@@ -0,0 +1,149 @@
+AuroraCare — Purpose-based Medical Data Exchange
+
+=== A – Primary care visit ===
+Clinician in the patient's care team accessing the patient summary for primary care management.
+
+Answer
+PERMIT
+
+Reason Why
+Permitted: clinician in the patient's care team, and the primary-care policy matched.
+
+Check
+C1 SKIPPED - not a prohibited purpose
+C2 OK - clinician
+C3 OK - care-team linked
+C4 SKIPPED
+C5 OK - operator=isAnyOf, allowed=["https://example.org/health#PATIENT_SUMMARY","https://example.org/health#LAB_RESULTS"], requested=["https://example.org/health#PATIENT_SUMMARY"]
+C6 SKIPPED - no prohibition matched
+C7 OK - trace shows matching permission
+C8 SKIPPED - no matched policy or no duties
+C9 SKIPPED - policy has no environment constraint
+C10 INFO - matched policy: urn:policy:primary-care-001
+
+=== B – Quality improvement (in scope) ===
+QI analyst using lab results + summary in a secure environment.
+
+Answer
+PERMIT
+
+Reason Why
+Permitted: ODRL/DPV policy matched for secondary use.
+
+Check
+C1 SKIPPED - not a prohibited purpose
+C2 SKIPPED
+C3 SKIPPED
+C4 OK - opt-in present and policy matched
+C5 OK - operator=isAllOf, allowed=["https://example.org/health#LAB_RESULTS","https://example.org/health#PATIENT_SUMMARY"], requested=["https://example.org/health#LAB_RESULTS","https://example.org/health#PATIENT_SUMMARY"]
+C6 SKIPPED - no prohibition matched
+C7 OK - trace shows matching permission
+C8 INFO - duties attached: duty:https://w3id.org/dpv/legal/eu/ehds#requireConsent, duty:https://w3id.org/dpv/legal/eu/ehds#noExfiltration
+C9 OK - operator=eq, allowed="secure_env", requested="secure_env"
+C10 INFO - matched policy: urn:policy:qi-2025-aurora
+
+=== C – Quality improvement (out of scope) ===
+QI analyst with only lab results; policy expects labs + summary.
+
+Answer
+DENY
+
+Reason Why
+Denied: no policy matched (purpose, environment, TOMs, or categories out of scope).
+
+Check
+C1 SKIPPED - not a prohibited purpose
+C2 SKIPPED
+C3 SKIPPED
+C4 OK - denied because opt-in missing or no policy match
+C5 SKIPPED
+C6 SKIPPED - no prohibition matched
+C7 SKIPPED
+C8 SKIPPED - no matched policy or no duties
+C9 SKIPPED
+C10 SKIPPED - no matched policy
+
+=== D – Insurance management ===
+Insurance bot attempting to use health data for insurance management (prohibited purpose).
+
+Answer
+DENY
+
+Reason Why
+Denied: the requested purpose (insurance management) is prohibited by policy.
+
+Check
+C1 OK - denied prohibited purpose
+C2 SKIPPED
+C3 SKIPPED
+C4 SKIPPED
+C5 SKIPPED
+C6 OK - denied due to prohibition
+C7 SKIPPED
+C8 SKIPPED - no matched policy or no duties
+C9 SKIPPED
+C10 SKIPPED - no matched policy
+
+=== E – GP checks labs ===
+GP for the same patient checking lab results via the API gateway.
+
+Answer
+PERMIT
+
+Reason Why
+Permitted: clinician in the patient's care team, and the primary-care policy matched.
+
+Check
+C1 SKIPPED - not a prohibited purpose
+C2 OK - clinician
+C3 OK - care-team linked
+C4 SKIPPED
+C5 OK - operator=isAnyOf, allowed=["https://example.org/health#PATIENT_SUMMARY","https://example.org/health#LAB_RESULTS"], requested=["https://example.org/health#LAB_RESULTS"]
+C6 SKIPPED - no prohibition matched
+C7 OK - trace shows matching permission
+C8 SKIPPED - no matched policy or no duties
+C9 SKIPPED - policy has no environment constraint
+C10 INFO - matched policy: urn:policy:primary-care-001
+
+=== F – Research on anonymised dataset ===
+Researcher using anonymised labs + summary in a secure environment, with opt-in.
+
+Answer
+PERMIT
+
+Reason Why
+Permitted: subject opted in and an ODRL/DPV policy matched (anonymised dataset in secure environment).
+
+Check
+C1 SKIPPED - not a prohibited purpose
+C2 SKIPPED
+C3 SKIPPED
+C4 OK - opt-in present and policy matched
+C5 OK - operator=isAnyOf, allowed=["https://example.org/health#LAB_RESULTS","https://example.org/health#PATIENT_SUMMARY","https://example.org/health#IMAGING_REPORT"], requested=["https://example.org/health#PATIENT_SUMMARY","https://example.org/health#LAB_RESULTS"]
+C6 SKIPPED - no prohibition matched
+C7 OK - trace shows matching permission
+C8 INFO - duties attached: duty:https://w3id.org/dpv/legal/eu/ehds#annualOutcomeReport, duty:https://w3id.org/dpv/legal/eu/ehds#noReidentification, duty:https://w3id.org/dpv/legal/eu/ehds#noExfiltration
+C9 OK - operator=eq, allowed="secure_env", requested="secure_env"
+C10 INFO - matched policy: urn:policy:research-aurora-diabetes
+
+=== G – AI training (opt-out) ===
+Data user wants to train AI, but the subject opted out of AI training.
+
+Answer
+DENY
+
+Reason Why
+Denied: you opted out of your data being used to train AI systems.
+
+Check
+C1 SKIPPED - not a prohibited purpose
+C2 SKIPPED
+C3 SKIPPED
+C4 OK - denied because opt-in missing or no policy match
+C5 SKIPPED
+C6 SKIPPED - no prohibition matched
+C7 SKIPPED
+C8 SKIPPED - no matched policy or no duties
+C9 SKIPPED
+C10 SKIPPED - no matched policy
+

package/examples/output/control-system.n3

@@ -1,5 +1,20 @@
-@prefix : <https://eyereasoner.github.io/eye/reasoning/cs#> .
-@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+Control System — ARC explanation of two control signals
 
-:actuator1 :control1 "39.27346198678276"^^xsd:decimal .
-:actuator2 :control1 "26.08"^^xsd:decimal .
+Answer
+Send both actuator commands now.
+Actuator 1 command: 39.27346198678276
+Actuator 2 command: 26.08
+
+Reason Why
+The first sensor pair is 6 and 11, so the reading is rising and the controller normalizes the gap 5 into 2.23606797749979. That normalized value creates a feedforward term of 43.82693235899588, while the known disturbance 35766 contributes a compensation term of 4.553470372213121. Subtracting that compensation gives actuator 1 the command 39.27346198678276. For actuator 2, the target is 5 units above the measured output, so the tracking error is positive. The observed state is -2 relative units below the measured output, so the differential correction is negative. That yields a proportional feedback part of 29, a nonlinear factor of 1.46, and a differential contribution of -2.92. Together they produce actuator 2 command 26.08.
+
+Check
+C1 OK - the first sensor pair is rising, so the normalization uses the rising-branch rule.
+C2 OK - the normalized measurement is positive and smaller than the raw gap, which is consistent with a square-root normalization.
+C3 OK - actuator 1 is lower than its proportional feedforward term because disturbance compensation is subtracted.
+C4 OK - the target is above the measured output, so the tracking error is positive.
+C5 OK - the observed state is below the measured output, so the differential error is negative.
+C6 OK - actuator 2 is lower than its pure proportional term because the differential part reduces it.
+C7 OK - actuator 1 matches an independently reconstructed feedforward calculation.
+C8 OK - actuator 2 matches an independently reconstructed feedback calculation.
+C9 OK - both actuator commands stay positive.

package/examples/output/delfour.n3

@@ -0,0 +1,30 @@
+=== Answer ===
+The scanner is allowed to use a neutral shopping insight and recommends Low-Sugar Tea Biscuits instead of Classic Tea Biscuits.
+case                 : delfour
+decision             : Allowed
+scanned product      : Classic Tea Biscuits
+suggested alternative: Low-Sugar Tea Biscuits
+
+=== Reason Why ===
+The phone desensitizes a diabetes-related household condition into a scoped low-sugar need, wraps it in an expiring Insight + Policy envelope, signs it, and the scanner consumes that envelope for shopping assistance.
+metric               : sugar_g_per_serving
+threshold            : 10.0
+scope                : self-scanner @ pick_up_scanner
+retailer             : Delfour
+signature alg        : HMAC-SHA256
+banner headline      : Track sugar per serving while you scan
+expires at           : 2025-10-05T22:33:48.907185+00:00
+reason.txt           : Household requires low-sugar guidance (diabetes in POD). A neutral Insight is scoped to device 'self-scanner', event 'pick_up_scanner', retailer 'Delfour', and expires soon; the policy confines use to shopping assistance.
+audit entries        : 1
+bus files written    : 6
+
+=== Check ===
+signature verifies              : yes
+payload hash matches            : yes
+minimization strips sensitive terms: yes
+scope complete                  : yes
+authorization allowed           : yes
+high-sugar banner               : yes
+alternative lowers sugar        : yes
+duty timing consistent          : yes
+marketing prohibited            : yes

package/examples/output/digital-product-passport.n3

@@ -1,10 +1 @@
-@prefix : <http://example.org/dpp#> .
-@prefix log: <http://www.w3.org/2000/10/swap/log#> .
-
-:ACME-X1000-SN123 :totalMassG 105 .
-:ACME-X1000-SN123 :recycledMassG 14 .
-:ACME-X1000-SN123 :recycledContentPct 13 .
-:ACME-X1000-SN123 :lifecycleFootprint_gCO2e 52500 .
-:ACME-X1000-SN123 :circularityHint :repairFriendly .
-:ACME-X1000-SN123 :containsCriticalRawMaterial true .
-:ACME-X1000-SN123 log:outputString "ACME X1000 SN123 | recycled=13% | lifecycle=52500 gCO2e | CRM=true | hint=http://example.org/dpp#repairFriendly\n" .
+ACME X1000 SN123 | recycled=13% | lifecycle=52500 gCO2e | CRM=true | hint=http://example.org/dpp#repairFriendly

package/examples/output/easter.n3

@@ -1,32 +1,150 @@
-@prefix : <http://www.agfa.com/w3c/euler/easterP#> .
-
-(4 4) :easterFor 2021 .
-(17 4) :easterFor 2022 .
-(9 4) :easterFor 2023 .
-(31 3) :easterFor 2024 .
-(20 4) :easterFor 2025 .
-(5 4) :easterFor 2026 .
-(28 3) :easterFor 2027 .
-(16 4) :easterFor 2028 .
-(1 4) :easterFor 2029 .
-(21 4) :easterFor 2030 .
-(13 4) :easterFor 2031 .
-(28 3) :easterFor 2032 .
-(17 4) :easterFor 2033 .
-(9 4) :easterFor 2034 .
-(25 3) :easterFor 2035 .
-(13 4) :easterFor 2036 .
-(5 4) :easterFor 2037 .
-(25 4) :easterFor 2038 .
-(10 4) :easterFor 2039 .
-(1 4) :easterFor 2040 .
-(21 4) :easterFor 2041 .
-(6 4) :easterFor 2042 .
-(29 3) :easterFor 2043 .
-(17 4) :easterFor 2044 .
-(9 4) :easterFor 2045 .
-(25 3) :easterFor 2046 .
-(14 4) :easterFor 2047 .
-(5 4) :easterFor 2048 .
-(18 4) :easterFor 2049 .
-(10 4) :easterFor 2050 .
+Easter — Gregorian computus
+
+=== 2026 ===
+Answer
+Easter Sunday falls on April 5.
+
+Reason Why
+For year 2026, the computus gives j=12, k=20, q=6, r=12, v=2, and final month/day numbers x=4, z=4. Because the day is z+1, the resulting Easter date is April 5.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2027 ===
+Answer
+Easter Sunday falls on March 28.
+
+Reason Why
+For year 2027, the computus gives j=13, k=20, q=6, r=1, v=5, and final month/day numbers x=3, z=27. Because the day is z+1, the resulting Easter date is March 28.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2028 ===
+Answer
+Easter Sunday falls on April 16.
+
+Reason Why
+For year 2028, the computus gives j=14, k=20, q=6, r=20, v=5, and final month/day numbers x=4, z=15. Because the day is z+1, the resulting Easter date is April 16.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2029 ===
+Answer
+Easter Sunday falls on April 1.
+
+Reason Why
+For year 2029, the computus gives j=15, k=20, q=6, r=9, v=1, and final month/day numbers x=4, z=0. Because the day is z+1, the resulting Easter date is April 1.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2030 ===
+Answer
+Easter Sunday falls on April 21.
+
+Reason Why
+For year 2030, the computus gives j=16, k=20, q=6, r=28, v=2, and final month/day numbers x=4, z=20. Because the day is z+1, the resulting Easter date is April 21.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2031 ===
+Answer
+Easter Sunday falls on April 13.
+
+Reason Why
+For year 2031, the computus gives j=17, k=20, q=6, r=17, v=5, and final month/day numbers x=4, z=12. Because the day is z+1, the resulting Easter date is April 13.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2032 ===
+Answer
+Easter Sunday falls on March 28.
+
+Reason Why
+For year 2032, the computus gives j=18, k=20, q=6, r=6, v=0, and final month/day numbers x=3, z=27. Because the day is z+1, the resulting Easter date is March 28.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2033 ===
+Answer
+Easter Sunday falls on April 17.
+
+Reason Why
+For year 2033, the computus gives j=0, k=20, q=6, r=24, v=2, and final month/day numbers x=4, z=16. Because the day is z+1, the resulting Easter date is April 17.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2034 ===
+Answer
+Easter Sunday falls on April 9.
+
+Reason Why
+For year 2034, the computus gives j=1, k=20, q=6, r=13, v=5, and final month/day numbers x=4, z=8. Because the day is z+1, the resulting Easter date is April 9.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.
+Easter — Gregorian computus
+
+=== 2035 ===
+Answer
+Easter Sunday falls on March 25.
+
+Reason Why
+For year 2035, the computus gives j=2, k=20, q=6, r=2, v=1, and final month/day numbers x=3, z=24. Because the day is z+1, the resulting Easter date is March 25.
+
+Check
+C1 OK - the Golden Number remainder j is inside the 0–18 cycle.
+C2 OK - the epact-style remainder r is inside the 0–29 cycle.
+C3 OK - the weekday adjustment v is inside the 0–6 cycle.
+C4 OK - the final month is a valid Easter month (March or April).
+C5 OK - the final date is inside the legal Gregorian Easter window.

package/examples/output/genetic-algorithm-knapsack.n3

@@ -1,3 +1 @@
-@prefix log: <http://www.w3.org/2000/10/swap/log#> .
-
-1 log:outputString "Knapsack GA best genome 101000000101 (feasible=true): weight=50 value=101 after 4 generations.\n" .
+Knapsack GA best genome 101000000101 (feasible=true): weight=50 value=101 after 4 generations.

package/examples/output/genetic-algorithm.n3

@@ -1,3 +1 @@
-@prefix log: <http://www.w3.org/2000/10/swap/log#> .
-
-1 log:outputString "GA evolved 11111101010 -> 2026 in 8 generations.\n" .
+GA evolved 11111101010 -> 2026 in 8 generations.

package/examples/output/gps.n3

@@ -1,6 +1,15 @@
-@prefix : <https://eyereasoner.github.io/eye/reasoning#> .
-@prefix gps: <https://eyereasoner.github.io/eye/reasoning/gps/gps-schema#> .
-@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+GPS — Goal driven route planning
 
-:i1 gps:path ((:drive_gent_brugge :drive_brugge_oostende) "2400"^^xsd:decimal "0.01"^^xsd:decimal "0.9408"^^xsd:decimal "0.99"^^xsd:decimal) .
-:i1 gps:path ((:drive_gent_kortrijk :drive_kortrijk_brugge :drive_brugge_oostende) "4100"^^xsd:decimal "0.018"^^xsd:decimal "0.903168"^^xsd:decimal "0.9801"^^xsd:decimal) .
+Answer
+Take the direct route via Brugge.
+Recommended route: Gent → Brugge → Oostende
+
+Reason Why
+From Gent to Oostende, the planner found two routes in this small map. The direct route (Gent → Brugge → Oostende) takes 2400 seconds at cost 0.01, with belief 0.9408 and comfort 0.99. The alternative (Gent → Kortrijk → Brugge → Oostende) takes 4100 seconds at cost 0.018, with belief 0.903168 and comfort 0.9801. So the direct route is faster, cheaper, more reliable, and slightly more comfortable.
+
+Check
+C1 OK - the direct Gent → Brugge → Oostende route was derived.
+C2 OK - the alternative Gent → Kortrijk → Brugge → Oostende route was derived.
+C3 OK - the recommended route is faster than the alternative.
+C4 OK - the recommended route is cheaper than the alternative.
+C5 OK - the recommended route has higher belief and comfort scores.

package/examples/output/ill-formed-literals.n3

@@ -0,0 +1,27 @@
+@prefix : <http://example.org/#> .
+@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
+
+(:badBool :p "truish"^^xsd:boolean) :datatype xsd:boolean .
+(:badBool :p "truish"^^xsd:boolean) :lexicalForm "truish" .
+(:badBool :p "truish"^^xsd:boolean) :reason "invalid xsd:boolean lexical form" .
+(:badDate :p "yesterday"^^xsd:dateTime) :datatype xsd:dateTime .
+(:badDate :p "yesterday"^^xsd:dateTime) :lexicalForm "yesterday" .
+(:badDate :p "yesterday"^^xsd:dateTime) :reason "xsd:dateTime literal is not parseable by the reasoner" .
+(:badDateTime :p "not-a-datetime"^^xsd:dateTime) :datatype xsd:dateTime .
+(:badDateTime :p "not-a-datetime"^^xsd:dateTime) :lexicalForm "not-a-datetime" .
+(:badDateTime :p "not-a-datetime"^^xsd:dateTime) :reason "xsd:dateTime literal is not parseable by the reasoner" .
+(:badDecimal :p "12.3.4"^^xsd:decimal) :datatype xsd:decimal .
+(:badDecimal :p "12.3.4"^^xsd:decimal) :lexicalForm "12.3.4" .
+(:badDecimal :p "12.3.4"^^xsd:decimal) :reason "invalid xsd:decimal lexical form" .
+(:badDouble :p "1e"^^xsd:double) :datatype xsd:double .
+(:badDouble :p "1e"^^xsd:double) :lexicalForm "1e" .
+(:badDouble :p "1e"^^xsd:double) :reason "invalid xsd:float/xsd:double lexical form" .
+(:badDuration :p "not-a-duration"^^xsd:duration) :datatype xsd:duration .
+(:badDuration :p "not-a-duration"^^xsd:duration) :lexicalForm "not-a-duration" .
+(:badDuration :p "not-a-duration"^^xsd:duration) :reason "xsd:duration literal is not parseable by the reasoner" .
+(:badInt1 :p "abc"^^xsd:integer) :datatype xsd:integer .
+(:badInt1 :p "abc"^^xsd:integer) :lexicalForm "abc" .
+(:badInt1 :p "abc"^^xsd:integer) :reason "invalid integer-family lexical form" .
+(:badInt2 :p "12.3"^^xsd:int) :datatype xsd:int .
+(:badInt2 :p "12.3"^^xsd:int) :lexicalForm "12.3" .
+(:badInt2 :p "12.3"^^xsd:int) :reason "invalid integer-family lexical form" .