I'm working on implementing nodepaths that select arcs. This is essentially just allowing node()/resource() as well as node()/resource()/node(). I've completed that change and now face the bigger challenge of implementing processing support.

The current spec describes a processing model whereby a context node is selected from the graph and all operations act on that context node. However, I want to be able to act on nodes and arcs so that definition has to change. One small dilemma I have is what to call it - 'context node or arc’ is a bit of a mouthful and 'context resource’ while technically correct implies that literals cannot be the context which, of course, they can. I'm probably just going to just use the term 'context’ and leave it at that.

Comments

No comments yet.

Leave a comment

Sorry, the comment form is closed at this time.