Implementation Comments

[jpradocueva]

Mockup

• See mockup proposal inREADME file.

JSON Structure

Content to Publish

• This JSON file contains the latest content to publish, overview1.json
• Further changes are expected to the content but not to the json structure

Template

• The template file contains a single example with all the possible key pair values, template,json

Relevant KeyWords

id: it will point to the schema to validate the "overview1.json" file
ftp: the value of this keyword will be used to create the global URL of the files and resources.

• the value of this URL is "https://www.openmobilealliance.org/release/", it will be used as base to find files and resources
• Rules for url & ftp
  • url: if the value of this keyword starts with https then it implies that the value is a global URL
  • url: if the value of this keyword starts with e.g. "LightweightM2M" or any other expression that it is not: https or mailto, then we need to create the Global URL by prefixing the value of in url keyword with the URL value stored in the ftp

resourceType: these are the possible resource's type:

• Overview
  • It can be a text or pdf file or a power presentation
• API
  • to be used to link to the Service API search
• Registry
  • to be link with the corresponding OMNA registry
• Tool
  • to be used to link to MD2HTML, LwM2M Editor or other future tools
• Dependency
  • to be used to list dependencies to other Enablers. It is displayed under the parent enabler. See mockup

publications: at the moment we have only one possible document, README.txt

• the value of theurl needs to be constructed by adding ftp+url