Dave Raggett

> I'm more wondering whether an application can bind the automatically assigned identifier to a variable through @id and then re-use it later on. Yes that should indeed work as...

See https://www.w3.org/Data/demos/chunks/chunks.html#additional for an example, but note that that document is out date in still defining @distinct

Further consideration suggests that spreading activation should not be performed when adding a chunk to a graph. In respect to the group of items example, if spreading activation was done...

For memories that once were really active, but haven't been used for a long time, these may still be of value in the right context. The above approach relies on...

The current version of the JavaScript library uses `@ago` in place of `@age` as a better match to the idea that a chunk was last updated the given number of...

Rules are identified by having the type "rule" and being in the "rules" module. A chunk of type "rule" is expected to have both the @condition and @action properties. Note...

I am unconvinced about modules being created by default as that sounds like something for a scripting specification. For this specification, we just need to note that "goal" is the...

The scripting API allows applications to create as many modules as needed and to declare additional operations for each module, but it assumes that at least the "goal" and "rules"...

For now, I think it is safer to assume that rules are only in the "rules" module. The [mapping mechanism](https://www.w3.org/Data/demos/chunks/chunks.html#compilation) can be used to "compile" rules from other modules to...

> whether modules can be read-only That is an interesting idea and also relates to what metadata is needed to manage access when different clients have different restrictions on what...