eyereasoner/koreografeye

A web choreography service using eye

koreografeye's Issues

Create a more human friendly DemoPlugin for demonstration purposes

Rename the current DemoPlugin to DebugPlugin

Policy extractor code loops for every policy parameter

https://github.com/eyereasoner/Koreografeye/blob/main/src/policy/Extractor.ts#L46

Take policy:

    ex:MySendNotificationDemo pol:policy [
        a fno:Execution ;
        fno:executes ex:sendNotification ;
        ex:to <http://patrickhochstenbach.net/inbox/> ;
        ex:notification [
                a as:Accept ;
                as:inReplyTo ?id ;
                as:actor     <http://patrickhochstenbach.net/profile/card#me> ;
                as:origin    <http://patrickhochstenbach.net/orchestrator/profile/card#me> ;
                as:target    ?actor;
                as:object    ?id
        ]
    ] .

The ex:sendNotification as two parameters ex:to and ex:notification this means that block L46 is executed two times. Refactor this into one loop.

Replace the bash scripts bin/orch bin/pol bin/watch by javascript versions

This will make it much easier to run the Koreografeye scripts with npx and support non-linux installations.

Policy IPolicyType arguments can only be one RDF Term

Koreografeye/src/policy/PolicyPlugin.ts

Lines 14 to 16 in 3fa0ed8

	args: { // Name/Value pairs of policy arguments
	[key : string]: RDF.Term | undefined
	}

Due to the IPolicyType type having for the arguments only the possibility to have an RDF.Term with cardinality one, the extractPolicies algorithm will pick a random RDF.Term for the arguments where in the conclusion of an N3 rule where this cardinality was N.

My proposal is to fix this by introducing a breaking change that will fix this problem:

export type IPolicyType = {
    node: N3.NamedNode | N3.BlankNode;
    path: string;
    policy: string;
    target: string;
    mainSubject: string;
    origin: string;
    order: number;
    args: {
        [key: string]: RDF.Term[];
    };
};

For this, extractPolicies must also be changed to make it possible to add a list of RDF.Term[].

Furthermore, there will be no undefined anymore since it can now have the empty list.

Refactor out the ComponentsManager?

Aparently the building and registration of the ComponentsManager has some overhead. It could be a future refactor step to move this to a higher level. When we eventually need a Koreagrafeye that need to have multiple runs of the reasoner this could remove some of this overhead.

https://github.com/eyereasoner/Koreografeye/blob/main/src/orchestrator/Reason.ts#L19

These lines:

const manager = await ComponentsManager.build({
    mainModulePath: path.join(__dirname, '../..') , // Path to your npm package's root
 });

 await manager.configRegistry.register(componentsPath);

Blogic examples stop to work from eye version 2.12.0 onwards

Need to check with eye dev.

Create a digital signature plugin for a notification.

https://www.npmjs.com/package/rdfjs-c14n

Use Jesse Wright's pretty-turtle to serialize quads back to input for eye

See also : https://github.com/jeswr/pretty-turtle

import { write } from '@jeswr/pretty-turtle';
write(quads, { format: 'text/n3', prefixes: {} })