Added proposal for a raw socket API based on Chrome Socket API.
Merge pull request #24 from ClaesNilsson/master

Raw Socket API
Merge pull request #23 from jungkees/master

System Application Runtime: Execution and Security Model (proposal from Samsung)
Move Intel's Contacts API proposal to a input_docs subfolder of the main Contacts proposal
replicating changes from J.M.Cantera's commit 2e4787dc65 to SMS API
Merge pull request #25 from otcshare/deprecate_contacts_intel

Move Intel's Contacts API proposal to a input_docs subfolder of the main proposal
editorial changes
removal of SMS.html superseeded by Messaging.html
Merge pull request #26 from efullea/sms

Removal of SMS.html superseeded by Messaging.html, plus editorials
Document error cases for AlarmManager methods and add examples regarding the crossing of timezone or DST boundaries
Moved Telephony_Intel proposal to Telephony
Moved Messaging_Intel to Messaging
Merge pull request #28 from otcshare/master

moved Telephony_Intel to Telephony and Messaging_Intel to Messaging
Merge pull request #27 from otcshare/alarm_initialFeedback

Document error cases for AlarmManager methods and add examples regarding...
• Removed  create() and instead defined a constructor for the RawSocket-object.
• Removed  disconnect() and destroy() and defined a method close().
• Added support for server with Listen() och Accept().
• In ”Dictionary CreateOptions” I added an attribute “useSecureTransport” for ssl/tls and changed ” addressReuse” to default False.
• Definied error handling with DOMError. Callback-functions has a nullable attribut ”error” of type DOMError. If success then error == null else if error a DOMError-string. In the Chrome Socket API return codes are undefined so I had to find out something here.
Merge pull request #29 from ClaesNilsson/master

New version of Raw Socket API
Messaging API updates
fixing MMS attachement attributes
Merge pull request #30 from efullea/sms

Messaging API updates
Runtime proposal: a merged document initial version