Minutes: JDO TCK Conference Call Friday November 9, 9 am Pacific Time
Attendees: Michael Bouschen, Michelle Caisse, Craig Russell Agenda: 1. News on JDO-717 copyjdorijars does not cleanup target directory https://issues.apache.org/jira/browse/JDO-717? no change. 2. News on spec update? Michael is working through the Chapter 14 changes; test cases need to be updated where the assertion numbers are incorrect. 3. Need to check the specification for assertions for new test cases that were added. We should review all resolved issues and make sure that new tests have assertions that match the specification. Michelle has made a text file with all of the assertions to make it easier for us to add new assertions. Michael has found a directory tck/assertions that contains a file with assertion comments. It is out of date and should be removed. 4. Other issues Action Items from weeks past: [Nov 02 2012] AI Craig JDO-678 needs a test case. [Aug 24 2012] AI Craig update the JIRAs JDO-689 JDO-690 and JDO-692 about JDOHelper methods. [Aug 17 2012] AI Craig comment on JIRA JDO-589 Autocommit or nontransactional action [Jul 20 2012] AI Michelle: take a look into adding JDO social links to db.apache.org/jdo. [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck. -- Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
Use of brackets in documents
On the telecon this morning, we discussed how square brackets are used in the spec, other than in the hidden assertion markers. In some cases, the spec uses brackets around an internal cross reference, as in [see Chapter 5]. I checked several on-line style guides for information about the use of brackets in writing. http://www.apastyle.org/learn/faqs/use-brackets.aspx http://data.grammarbook.com/blog/brackets/changing-a-quote-using-brackets/ The most similar case presented in these sources is the use of brackets for references, but that is strictly for a reference that provides a key to bibliographic entries that are listed elsewhere in the document. IMHO, it would be more in accord with standard usage to use parentheses instead of square brackets for internal cross references in the spec. This would alleviate potential confusion with the brackets in assertion markers when using a script to extract assertions. -- Michelle
