- OGC® Standards
- OGC Standards List
- Specification Profiles
- Abstract Specification
- OGC Reference Model
- OGC Schema Updates
- Public Engineering Reports
- TC Policy Directives
- GeoDRM Reference Model
- Best Practices
- Discussion Papers
- Deprecated Documents
- Retired Documents
- Requests (RFP's, RFQ's...)
- White Papers
- Change Requests
- Submit Change Request or Requirement
OGC Seeks Comments on Open GeoSMS Standard - Core
The Open Geospatial Consortium (OGC®) seeks public comment on the candidate OGC Open GeoSMS Standard - Core.
The candidate OGC Open GeoSMS Standard allows applications to location enable Short Message Service (SMS). SMS is the text communication service component of phone, web and mobile communication systems. SMS uses standardized communications protocols that allow the exchange of short text messages between fixed line or mobile phone devices.
Open GeoSMS enables developers to use extended Short Message Service (SMS) to facilitate communication of location content between different LBS (Location-Based Service) devices or applications. The encoding is extremely light weight and the standards document is quite short.
The Taiwan Industrial Technology Research Institute (ITRI) contributed this candidate standard to the OGC. Open GeoSMS is already in use in a number of deployed commercial applications in Taiwan as well as in a number of disaster response applications such as those provided by Sahana.
The candidate OGC Open GeoSMS Standard can be found below. The period for issuing comments expires on 24 April 2011.
Comments can be submitted to a dedicated email reflector for a thirty day period ending on the "Close request date" listed above, Comments received will be consolidated and reviewed by OGC members for incorporation into the document. Please submit your comments using the following link: requests [at] lists [dot] opengeospatial [dot] org (Click here to submit comments) The link provided above should include a standard template in the message body. If the preloaded message body does not work properly using your mail client, please refer to the following template for the message body: Comments Template