OSIE-II telecon notes: 7/21/2009

Participants: Schleisiek, Cater, O'Reilly

Agenda:

1. Comments on plan to complete OSIE-2 PUCK project (see attached)
NOTE: Technical report must be complete and submitted by 7 November
Important to show integration with OGC and IEEE-1451 standards (Luis Bermudez)

2. Demonstration venues (see attached, see MarTech abstract)
a) Plans for MarTech demo
b) Other venues?

3. Plans for Axys participation - Cater, Philips
Neil: Axys wants to participate, but they are lagging. Reo says 1 week of work, done in September.

4. Standardized PUCK payload tags for observatory-interoperable payloads (see attached)
Perhaps European and MBARI teams could show observatory-interoperability, using RBR/Seabird with multiple PUCK payloads. One of those payloads should be IEEE-1451 TEDS. Could have RBR in Spain, Seabird in USA...

5. XML versus binary 1451 TEDS for PUCK payload
Binary is probably easier to process on small microprocessor. Perhaps PUCK payload could contain either or both, with appropriate tags.

6. Minimum payload size (Klaus):
PUCK payload tags - keep wordiness down.
Have length info on each tag.
Tag info: should it include checksum? Klaus thinks checksum is might be overdone. But O'Reilly notes that we use binary tags. Klaus likes simple tag approach, each tag has pointer to next tag.

Klaus:
XML is "best practice", but very wordy. But you can 'zip' it. Zip format is supported by several tools - Jar, tar, Zip. Is Zip standard?
O'Reilly to check on Zip format standard.

Klaus: could use OpenBoot for instrument driver - Forth-based bytecode - IEEE-1275
Very good for applications that deal with hardware

Neil: going to Oceans at Biloxi; thinks that RBR and Axys are going as well.
Will make presentation about interoperability.

O'Reilly - resend technical template

O'Reilly - send 1451.0 server details to Neil.

O'Reilly - ask Yves about participation in best practices workshop