Difference between revisions of "Developer Guides"

From OneM2M
Jump to: navigation, search
(Created page with "<div style="font-size:200%"> <center>'''Welcome to the Open Source MANO WIKI!'''</center> </div> ----- Welcome to OSM, an ETSI-hosted open source management and orchestration...")
 
Line 1: Line 1:
 
<div style="font-size:200%">
 
<div style="font-size:200%">
<center>'''Welcome to the Open Source MANO WIKI!'''</center>
+
<center>'''oneM2M Developer Guides'''</center>
 
</div>
 
</div>
 
-----
 
-----
Welcome to OSM, an ETSI-hosted open source management and orchestration (MANO) community project to jointly innovate, create and deliver a MANO stack that is closely aligned with ETSI NFV. This portal page aims to provide you with a starting point in your engagement with the OSM community, our software releases and collaborative development processes.
+
oneM2M has worked on a series of developer guides, propsing a guideline for application developers who want to use functionalities offered by an oneM2M service platform.
 
+
When implementing a standard, it is frequently requested from software developer community to get some tutorials describing for basic use cases, some procedures and scenarios, including diagrams, message flows, message traces samples, resource description samples, etc.. … Such document would be helpful in software development to provide overal understanding of the main functions offered by the oneM2M architecture, before going more deeply into the analysis of the oneM2M standards.
<blockquote>'''Our Vision & Mission'''
 
 
 
OSM is delivering an open source Management and Orchestration (MANO) stack aligned with ETSI NFV Information Models. As an operator-led community, OSM is delivering a production-quality open source MANO stack that meets the requirements of commercial NFV networks.  
 
  
 
</blockquote>
 
</blockquote>

Revision as of 14:33, 13 September 2016

oneM2M Developer Guides

oneM2M has worked on a series of developer guides, propsing a guideline for application developers who want to use functionalities offered by an oneM2M service platform. When implementing a standard, it is frequently requested from software developer community to get some tutorials describing for basic use cases, some procedures and scenarios, including diagrams, message flows, message traces samples, resource description samples, etc.. … Such document would be helpful in software development to provide overal understanding of the main functions offered by the oneM2M architecture, before going more deeply into the analysis of the oneM2M standards.



Template:Feedback