PUCK payload External PUCK

4 Copyright © 2012 Open Geospatial Consortium.

3.15 Embedded PUCK

PUCK protocol embedded within an instrument’s firmware contrast with external PUCK. 4 Document conventions

4.1 Typographical conventions

The following are conventions that are used through out this document. PUCK inputoutput is displayed in the courier font, for example GBCR 19200CRPUCKRDYCR The notation CR and LF are used to denote carriage return and linefeed respectively The notation [0,255] is used to denote a parameter range e.g. 0 ฀ parameter ฀ 255 Normative requirements are indicated in this document by the word REQ in bold font, followed by an identifying URI, e.g. REQ reqcoredatasheet Some requirements are declared within table cells, while others are prepended to clauses within the document text.

4.2 Symbols and abbreviated terms

Some frequently used abbreviated terms: ISO International Organization for Standardization OGC Open Geospatial Consortium SOSC Smart Ocean Sensors Consortium SWE Sensor Web Enablement TEDS Transducer Electronic Data Sheet UUID Universally Unique Identifier XML eXtended Markup Language Copyright © 2012 Open Geospatial Consortium. 5

4.3 Namespace convention

The URL http:www.opengis.netspecPUCKv1.4 is assumed throughout this document as the namespace prefix for PUCK requirement and conformance test URIs. 5 Core PUCK Requirements Core PUCK requirements are applicable to all PUCK implementations RS232 PUCK and IP PUCK. Table 1: PUCK core requirement classes Requirement name Description Instrument datasheet class REQ class reqcoredatasheet PUCK SHALL provide a PUCK instrument datasheet in memory as specified in Sections Error Reference source not found. and 9.1 Core commands class REQ class reqcorecmds The PUCK-enabled device SHALL implement those commands in Section 8 that are designated as belonging to this class. PUCK payload class REQ class reqcorepayload-tags Information stored to PUCK payload memory SHALL be structured as specified in Section 10. 6 RS232 PUCK Requirements This section describes requirements for PUCK-over-RS232 RS232 PUCK implementations. RS232 PUCK presumes that PUCK is carried out over the PUCK- enabled devices EIA232-compliant physicalelectrical interface, with that interface configured for eight data bits, no parity, and one stop bit.