[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: PQI Changes
David This all looks good to me. I would appreciate your input on the COEL document – both generally and specifically on the formatting of the model json objects that needs to be added in Section 3. I can then review all of Matt’s additions
to this document as well. The other area that needs some attention is the review of the security analysis in section 4.3.2 of the RPE to reflect that changes that we have made. There are some of Paul’s input to incorporate here and the
resolution of issues COEL-24 & COEL-26. I think we also still need to resolve the style questions before we can start finalising the documents: ·
Standardising formats of sample code ·
Use of defined terms, Capitals and CAPITALS ·
Abbreviations (e.g. Behavioral Atoms / Atoms) - when to use? ·
Acronyms (e.gs IDA) - when to use? Regards Joss Important Information: The contents of this email are intended for the named addresses only and contain information which is confidential and which
may also be privileged. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy, use it, or disclose it to anyone else. If you received it in error, please notify us immediately at
enquiries@activinsights.co.uk and then destroy it. Further, whilst we make efforts to keep our network free from computer viruses, etc., you do need to check this email and any attachments to it for viruses
as we can take no responsibility for any viruses which might be transferred by way of this email.
Activinsights Limited, Unit 11, Harvard Industrial Estate, Kimbolton, Cambs, PE28 0NJ. A company registered in England & Wales. Registered number:
06576069 From: coel@lists.oasis-open.org [mailto:coel@lists.oasis-open.org]
On Behalf Of david.snelling@uk.fujitsu.com Folks, Paul suggested a few edits in the PQI document. Rather than processing them as issues, here's what I did. 1) Query not required, e.g. all atoms request. - I deleted 'required' 2) Is there some form of parenthesisation? E.g. (a>1 AND a <3) OR (a <1 and b=0) ? Not needed and 'filter' can be used recursively in the JSON format of the query. I just deleted the comment. 3) The conformance section is too detailed. This is because we wanted the minimal implementation to be really simple (just all atoms and atom count) while at the same time requiring more capable DEs to use the same query format. 4) Fixed the CoelitionID issue. 5) Created an issue for the question of special operations for all atoms and atom count. If there are problems with the above, simply raise an issue. -- Take care: Dr. David Snelling < David . Snelling . UK . Fujitsu . com > Senior Research Fellow Research Transformation and Innovation Fujitsu Laboratories of Europe Ltd. +44-7590-293439 (Mobile)
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]