Draft: LwM2M Device Object model.

[dnav]

First version with some details to sort out:

• the propery Error_Code is an integer between 0 and 32 with choices and reserved values.
• the thing ExtDevInfo has no defined reference has this is dependant on the implementation

[akeranen]

Suggested change

	"#/sdfObject/Device/sdfAction/",
	"#/sdfObject/Device/sdfAction/Reboot",

This seems to be missing the affordance name

[dnav]

Indeed.

It seems there is bug in the LwM2M to SDF converter at http://wishi.nomadiclab.com/sdf-converter/. If you try the following XML definition, the sdfRequired contains "#/sdfObject/Test/sdfAction/" instead of "#/sdfObject/Test/sdfAction/MandatoryAction".

<?xml version="1.0" encoding="UTF-8"?>

<LWM2M xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.openmobilealliance.org/tech/profiles/LWM2M.xsd">
  <Object ObjectType="MODefinition">
        <Name>Test</Name>
        <Description1><![CDATA[Test.]]></Description1>
        <ObjectID>777</ObjectID>
        <ObjectURN>urn:oma:lwm2m:oma:777</ObjectURN>
        <LWM2MVersion>1.0</LWM2MVersion>
        <ObjectVersion>1.0</ObjectVersion>
        <MultipleInstances>Single</MultipleInstances>
        <Mandatory>Optional</Mandatory>
        <Resources>
            <Item ID="0">
                <Name>MandatoryProp</Name>
                <Operations>R</Operations>
                <MultipleInstances>Single</MultipleInstances>
                <Mandatory>Mandatory</Mandatory>
                <Type>String</Type>
                <RangeEnumeration></RangeEnumeration>
                <Units></Units>
                <Description><![CDATA[]]></Description>
            </Item>
            <Item ID="1">
                <Name>OptionalProp</Name>
                <Operations>R</Operations>
                <MultipleInstances>Single</MultipleInstances>
                <Mandatory>Optional</Mandatory>
                <Type>String</Type>
                <RangeEnumeration></RangeEnumeration>
                <Units></Units>
                <Description><![CDATA[]]></Description>
            </Item>
            <Item ID="2">
                <Name>MandatoryAction</Name>
                <Operations>E</Operations>
                <MultipleInstances>Single</MultipleInstances>
                <Mandatory>Mandatory</Mandatory>
                <Type></Type>
                <RangeEnumeration></RangeEnumeration>
                <Units></Units>
                <Description><![CDATA[]]></Description>
            </Item>
            <Item ID="3">
                <Name>OptionalAction</Name>
                <Operations>E</Operations>
                <MultipleInstances>Single</MultipleInstances>
                <Mandatory>Optional</Mandatory>
                <Type></Type>
                <RangeEnumeration></RangeEnumeration>
                <Units></Units>
                <Description><![CDATA[]]></Description>
            </Item>
        </Resources>
        <Description2></Description2>
    </Object>
</LWM2M>

[akeranen]

Good catch! Fixed now in the ipso-odm toolkit. Unfortunately updating the web tool takes a bit more effort and will have to wait for later.

[dnav]

Thanks

[plaari]

I updated the web tool today, so it should work now.

[akeranen]

As discussed, here "sdfType" : "link" is probably the best option, but probably needs some thinking.

[dnav]

Updated according to my understanding of https://www.ietf.org/archive/id/draft-bormann-asdf-sdftype-link-00.html

[akeranen]

Looks good! To enable using properties quality, just add also quality
"type" : "object"
(Yes, we need to update the schema to catch that. Thanks!)

[dnav]

Fixed