SAMP — Simple Application Messag- ing Protocol Version 1.11 - IVOA

• ::= [ ] [ "e" | "E" [ ] ]A floating point value is encoded as a mantissa with an OPTIONALpreceding sign followed by an OPTIONAL exponent part introducedwith the character “e” or “E”. There is no guarantee about the largestor smallest values which can be represented or about the number ofdigits of precision which are significant, since these will depend on theprocessing environment at decode time.• ::= "0" | "1"A boolean value is represented as an integer: zero represents false, andany other value represents true. 1 is the RECOMMENDED value torepresent true.The numeric types are based on the syntax of the C programming language,since this syntax forms the basis for typed data syntax in many otherlanguages. There may be extensions to this list in future versions of thisstandard.Particular MType definitions may use these conventions or devise theirown as required. Where the conventions in this list are used, message documentationSHOULD make it clear using a form of words along the lines “thisparameter contains a SAMP int”.3.5 Registering with the HubA client registers with the hub to:1. establish communication with the hub2. advertise its presence to the hub and to other clients3. obtain registration informationThe registration information is in the form of a map containing data itemswhich the client may wish to use during the SAMP session. The hub MUSTfill in values for the following keys in the returned map:samp.hub-id — The client ID which is used by the hub when it sends messagesitself (rather than forwarding them from other senders). For instance,this ID will be used when the hub sends the samp.hub.event.shutdownmessage.samp.self-id — The client ID which identifies the registering client.These keys form part of an extensible vocabulary as explained in Section 2.6.In most cases a client will not require either of the above IDs for normal14