From Kynetx Docs

[edit] Welcome to the main page!

Welcome to the Kynetx developer documentation. On these pages you will find documentation, policy and procedure.

Kynetx is a rule based programming language which allows developers to create apps that manipulate, take away or add to any endpoint. Some examples of endpoints are web browsers, smart phones, emails, and pretty much anything you can imagine (even sprinkler systems!). The Kynetx Rule Language is used to create content aware applications that work across multiple browsers, multiple domains, and multiple protocols at the same time.

Imagine walking into Borders and having your smart phone alert you to the fact that the book you put on your Amazon wish list this morning is available right now and on sale. As another example, think about an application that gathers relevant articles from your RSS and Twitter feeds based on searches you’ve performed or that are related to an email you received from a friend today. This is all possible with the power of Kynetx.

This documentation includes the following sections:
1) Getting Started: This includes tutorials and information on both the Kynetx Rules Language and the Kynetx IDE (a.k.a AppBuilder).
2) KRL: This section includes in-depth reference documentation for the Kynetx Rules Lanaguage
3) Cookbook: This section includes "recipes," or sample code, for creating apps using KRL.
4) KNS (Kynetx Network Services): This section includes instruction and documentation on the platform itself including the engine and architecture.
5) API: This section describes how to use the Kynetx API to create apps using other IDEs.
6) Appbuilder: This section walks you through using the Kynetx IDE called AppBuilder.

[edit] KRL

The Kynetx Rule Language (KRL) a programming language that is built for creating apps that are context-aware and cross-domain. KNS provides a cloud-­‐based platform for executing KRL programs.

The following lists specific benefits provided by KRL and KNS:

• User-­centric and user-­controlled—Apps built using KRL are intrinsically tied to users. The architecture of KNS is such that rulesets are always evaluated on behalf of an entity (user). Users control endpoints and thus the apps that they run and the events they raise.
• Event controlled—events provide a powerful, unifying abstraction for building reactive systems. Developers can easily write applications that respond to complex event scenarios.
• Cross domain—Kynetx apps can work across domains so that user purpose can be advanced regardless of online location. KRL is designed to cross the silos that have sprung up, as stand-­‐alone Web applications, so developers can create applications that mash-­‐up data from all across the Internet regardless of location or protocol.
• Cross protocol—Kynetx apps easily work across Internet protocols such as the Web, email, and so on. KNS is easily extensible by developers to support any protocol.
• Data and context driven—KRL and KNS are designed to easily and naturally work with the burgeoning array of data and APIs available online. Correlated data provides context about users. Using KRL and KNS, developers can create applications that respond to user context for a more compelling experience.
• Cloud based—because Kynetx apps are cloud based, they work consistently and ubiquitously. They can be accessed from multiple platforms while providing the same context, identity, and experience. Cloud-­‐based programming means that programs always work because they are updated without user interaction in response to changing conditions.
• Browser independent—Kynetx apps work in all the major browsers without modification. The browser has become a sort of universal application platform, but browser differences make programming on them difficult. KRL provides a unifying framework for easily working with all of the popular browsers.
• Internet app centric language and design—KRL provides a powerful notation for creating apps that run across the Internet. KNS provides the platform that makes that possible.
• Security and privacy are built-­in—the architecture of KNS is designed to limit nefarious activity structurally. In addition, operating in the cloud makes it easy to turn off apps that are misbehaving. User control provides the means to create privacy respecting apps.
• Late binding—Kynetx apps run at the exact moment that the user needs them. They bind to data and functionality that is appropriate for the user’s current context. In contrast, conventional Web applications exist at a single location and operate without the benefit of user context. * Multi endpoint—KNS provides application program endpoints that work with Web browsers, email servers, and other Internet systems. Kynetx plans to provide endpoints for popular and important Internet protocols and applications as part of its ongoing development roadmap. Developers can easily extend KNS to include endpoints for any Internet protocol.
• Developer-­friendly—KRL is designed to provide developers with a powerful and easy to use abstraction layer for apps. KRL provides a notation that lets programmers easily complete Internet programming tasks that previously took many lines of code. Event The Kynetx Rule Language 4 expressions, datasets, and data sources are just a few examples. Because Kynetx apps are hosted, developers are spared operational and maintenance headaches that come with servers.

[edit] Kynetx Rule Language

Getting Started - Tutorials and Walk-throughs

KRL documentation - What you're looking for is most likely here.

Cookbook - A selection of KRL examples

Actions - A list of actions

KNS - A brief overview on how the Kynetx System works

Why Rules? - Why is KRL a rules language instead of a traditional imperative or object language?

KRL Runtime Library - Documentation for the KRL runtime library