Dave Raggett

I've now documented the simple API exposed by my [JavaScript library for Chunks](https://www.w3.org/Data/demos/chunks/chunks.js), which includes the rule engine, see: * https://www.w3.org/Data/demos/chunks/chunks.html#api This library is being used for the development of...

**Reasoning from multiple perspectives**: there is increasing recognition of the importance of being able to reason from multiple perspectives. In social contexts, there is a need to represent the beliefs...

@ is currently reserved for use within rules for terms that the rule engine needs to deal with specially. This is needed as the use of @ terms in goals...

In regards to Links, the short form is just a syntactic abbreviation for the longer form, and subject and object are conventions that can be utilised by rulesets and graph...

In regards to ISO8601 dates, the corresponding chunk would only be created when the chunk ID is dereferenced and doesn't already exist.

I introduce @ primarily for use within rule conditions and actions, but also for named contexts. There is a need to be able to distinguish properties that have special meaning...

Another perspective is for someone who doesn't speak English well and uses her own language for names. She understands and accepts that terms starting with @ are reserved and they...

Perhaps we can simply allow updates to specific @ properties such as @subject, @object and @context. See also the use of @ with map, see: https://www.w3.org/Data/demos/chunks/chunks.html#compilation That involves a means...

You can clear the module's buffer with "@do clear" or pop its queue with "@do pop". A further option is to undefine a property of the module's buffer with "@undefine...

> Re. automatically assigning an identifier, where would that info be exposed? Yes, the identifier is accessible via the scripting API after the chunk is added to the module's graph,...