Rethinking Ruleset Registration in KRL
A ruleset registry has been part of KRL from the start. This proposal would deprecate ruleset registries in favor of simply using URLs.
Continue reading {Rethinking Ruleset Registration in KRL}
Conditional Expressions and Explicit Logging
This afternoon I released build 329 of Kynetx Network Services (KNS). This build includes two new features for the Kynetx Rule Language (KRL): explicit logging and conditional expressions. Explicit logging allows developers to place information in the ruleset log when a ruleset runs. For example, the following example would place a string with the value of a variable named query in the log if the rule fired: fired { log "query:"+query } Explicit logging is useful for recording information about the rule environment in the logs for later analysis. Conditional expressions allow expressions to take on different values depending
Continue reading {Conditional Expressions and Explicit Logging}
First-Class Namespaces in Programming Languages
Over the last few years, I've written plenty of programs--in various languages--that used a HTTP library to fetch an XML document pointed at by a URL and then used XPath to grab parts and pieces of that XML document. The problem with this is that I'm using two different namespaces (the URI and the XML) neither of which is directly supported by my programming language. Programs that use relational databases suffer similarly: a datastore with a namespace that is extralingual. One of the great selling points of JSON is that it reduces the cognitive load of
Continue reading {First-Class Namespaces in Programming Languages}





