Difference between revisions of "OpenIGTLink/ProtocolV2/Index"
From NAMIC Wiki
| Line 8: | Line 8: | ||
Please add one proposal page per message type. The template for a proposal page is available [[OpenIGTLink/ProtocolV2/ProoposalTemplate| here]]. All proposal pages must be linked from the section [[OpenIGTLink/ProtocolV2/Proposals#Message Proposals|below in this page]]. | Please add one proposal page per message type. The template for a proposal page is available [[OpenIGTLink/ProtocolV2/ProoposalTemplate| here]]. All proposal pages must be linked from the section [[OpenIGTLink/ProtocolV2/Proposals#Message Proposals|below in this page]]. | ||
| − | = | + | =OpenIGTLink version 2 Summary= |
| − | *The header format will not be changed | + | *The header format will not be changed. |
*Simple querying mechanism is defined. See [[OpenIGTLink/ProtocolV2/Query| querying mechanism in version 2]]. | *Simple querying mechanism is defined. See [[OpenIGTLink/ProtocolV2/Query| querying mechanism in version 2]]. | ||
*The protocol version 2 continue to focus on message formats. Supporting tools (simulators and interfaces for specific applications e.g. 3D Slicer, Matlab) and transportation layer (use of UDP or other network communication middleware) should be discussed separately. | *The protocol version 2 continue to focus on message formats. Supporting tools (simulators and interfaces for specific applications e.g. 3D Slicer, Matlab) and transportation layer (use of UDP or other network communication middleware) should be discussed separately. | ||
*'''(TBD)'''Xenios proposed to introduce a "footer" field in addition to header and body in the OpenIGTLink message format. The idea is to use footer as an area, which can be used by the developers to put application-specific information. In most case, this "footer" approach does not violate the rules in version 1 protocol. | *'''(TBD)'''Xenios proposed to introduce a "footer" field in addition to header and body in the OpenIGTLink message format. The idea is to use footer as an area, which can be used by the developers to put application-specific information. In most case, this "footer" approach does not violate the rules in version 1 protocol. | ||
| + | |||
| + | =Architecture and Header= | ||
| + | *[[OpenIGTLink/ProtocolV2/Header| OpenIGTLink Header]] | ||
=Proposed Message Types= | =Proposed Message Types= | ||
Revision as of 14:31, 1 July 2010
Home < OpenIGTLink < ProtocolV2 < IndexContents
General Information
Version 2 Release Timeline
We are inviting proposals from the community for new and modified message formats, which are potentially included into OpenIGTLink version 2 protocol. The deadline of proposal is September 12 (One week before MICCAI 2010). Anyone, who has an account in NA-MIC wiki, can propose a new message. The proposed messages will be reviewed by the community during a period between MICCAI 2010 and NA-MIC All Hands Meeting 2011.
Inviting Message Type Proposal -- How to Propose
Please add one proposal page per message type. The template for a proposal page is available here. All proposal pages must be linked from the section below in this page.
OpenIGTLink version 2 Summary
- The header format will not be changed.
- Simple querying mechanism is defined. See querying mechanism in version 2.
- The protocol version 2 continue to focus on message formats. Supporting tools (simulators and interfaces for specific applications e.g. 3D Slicer, Matlab) and transportation layer (use of UDP or other network communication middleware) should be discussed separately.
- (TBD)Xenios proposed to introduce a "footer" field in addition to header and body in the OpenIGTLink message format. The idea is to use footer as an area, which can be used by the developers to put application-specific information. In most case, this "footer" approach does not violate the rules in version 1 protocol.
