OASIS documents overview

Unfortunately, I think the RPE doc started from an earlier version that the submission – I have quite a few changes to make, can I update this before everyone else reviews?

For all documents

· How relevant is the date at the top of page 1 and in the footer?

· We should probably have ‘Additional Artifacts = none’ for every document except COEL

· We can probably now have a set list of related works for all docs

· We need to hyperlink all URI patterns on all docs and check they (most do not at the moment)

· Table of contents need to be updated on each revision

· We need to add normative references within the specification as we move down the hierarchy (& link correctly)

· We need to review the external normative references for each doc (& link correctly)

· Are there some standard non-normative references (e.g. Data to Life)?

· There are some style questions to harmonise (does OASIS have a standardised approach?):

o Use of defined terms, Capitals and CAPITALS

o Abbreviations (e.g. Behavioral Atoms / Atoms) - when to use?

o Acronyms (e.gs IDA) - when to use?

· The spelling of Activinsights is incorrect in the Acknowledgement sections of a few docs

· We should standardise our date formats in the revision section

· Should we be using track changes in Word?

PQI

· COEL-1 Do we want to include pub/sub specifications at this stage or at all?

· COEL-4 Audit of leavers. This is labelled as an MMI but I think it is more of a query. We don’t have to have this in the standard and it might be better as a Coelition commercial contract point.

· COEL-5 There is benefit for Service Providers being able to work in their own time zone. Can we include this now?

· COEL-9 It could very beneficial for all Service providers to be able to query against the segment data as well as the atom fields.

BAP

· 2.2.1 Should we explicitly link “queryURI” and “managementURI” either in or to the MMI and PQI documents?

· 2.2.1 & 2.2.2 We need to agree the standard format for example code

· 2.4 I have added a section for ‘exceptions’ to provide a way of managing issue COEL-6

· 3.7 I have added a link to the IDA in the ‘who’ section to sort out issue COEL-18

COEL

· I have suggested a document structure for the COEL high level specification

Joss Langford

Technical Director

Activinsights Ltd

Tel: 01480 862080

MBL 07712 886208

www.geneactiv.co.uk

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

coel message