1.0.1

Zenodo added

v1.0.0 (PoC)

This release provides a ready-to-run Proof-of-Concept (PoC) translating the GQL Rules “Use Cases” examples into Cypher/APOC scripts for Neo4j 5.

Highlights

• End-to-end runnable workflow: DDL → seed data → rule scripts → views → verification queries
• Cypher/APOC implementations for Listings 2–7
• Practical support for dirty data diagnostics (Listing 4) via materialized :RuleDiag nodes
• “VIEW/EXPOSE” expressed as a canonical view query (Listing 6)

What’s Included

• 00_ddl/ — schema constraints in two variants:
  • Clean (production): scalar t.txId, uniqueness enforced
  • Dirty-demo: t.txId may be a list (for demonstrating diagnostics)
• 01_data/ — sample datasets for transfers, defaults, and genealogy
• 02_rules/ — rule implementations corresponding to the paper’s listings
• 03_views/ — view query scripts
• 04_verify/ — minimal verification queries to confirm expected outcomes

Implementation Notes

• ENRICH is implemented as add-only list enrichment with deduplication using apoc.coll.toSet(...)
• Recursive materialization (Listings 1 + 7) uses commit-friendly patterns suitable for Neo4j Browser / cypher-shell
• APOC procedures expected: apoc.periodic.commit, apoc.coll.toSet, apoc.meta.type

Requirements

• Neo4j 5.x
• APOC installed and enabled

Known Limitations

• This is a PoC focused on correctness and demonstrability rather than performance tuning
• Scripts assume a local single-instance Neo4j environment and do not cover clustering or advanced governance settings