Agenda Item 1:

1. Status on the CsvStore port to 0.9 dojo.data APIs
2. Status on XmlStore port to 0.9 dojo.data APIs
   • Still waiting on fate of dojo.dom in 0.9.  Critical for XmlStore port.
     • Jared is talking with Tom Trenka on the subject, may be working with another contributor on finalizing a dojo/dojox.dom set for 0.9 that will hopefully be usable
3. Status on updates to base read apis, such as loadItem
   • Updated to be async call.
4. Status on move of JOT content to the drupal site (New developer's guide).
   
5. Status on other items/changes made to the base apis and helpers.
   

Agenda Item 2:   To Be Determined

1. In the Read API, should we update the isItem() documentation to make it more clear about how discriminating each datastore implementation is expected to be? If an application is using two or more datastores at the same time (for example, reading from two CSV files), are we saying that store1.isItem(item2) will return true if and only if item2 came from store1, or are we saying that it is acceptable for isItem() to return true for any item, regardless of which datastore it came from? And if we say that the isItem() should be able to discriminate between datastores, then does the JsonItemStore code need to be fixed to support that
   1. Agreed that isItem should only accept items that are valid for that store instance.  This is necessary for stores that can load from urls where the data may vary.  Items from instance 1 may not be in instance 2, so instance2 isItem() should return false for instance 1 items.
      
2. In the Identity API, should the getItemByIdentity() documentation be made to correspond to the getIdentity() documentation, saying that the identity can be not just a string but any object that has a toString() function?
   1. Agreed this should be updated to clarify.  It should accept any aitem that can be toString()'ed
      
3. Discuss a bit more on the write api?  There were concerns about the name of the function (save(), which implies a write and close).
   • Brian and Jared seemed to like 'commit' and 'rollback' in lieu of save and revert.  Need more input from the community on what they feel makes the most sense.
4. More work on the path accessors?
5. The dojox.wires project (was data binding).