Re: [core] Using Yang to describe LWM2M ... was Re: ? WG adoption of draft-veillette-core-yang-cbor-mapping-00

[Hannes Tschofenig <[e-mail]>]

Hi Juergen

thanks for your feedback.

What is considered 'open' seems to vary a bit. I was using the
definition of the OpenStand, see
https://open-stand.org/about-us/principles/

I will reach out to the OMA staff to find out why the current
boilerplate text exists.

Ciao
Hannes

On 04/27/2016 09:07 AM, Juergen Schoenwaelder wrote:
> On Mon, Apr 25, 2016 at 01:03:34PM +0200, Hannes Tschofenig wrote:
>> Hi Juergen,
>>
>> On 04/25/2016 12:33 PM, Juergen Schoenwaelder wrote:
>>> Hannes,
>>>
>>> whether this YANG fragment makes sense or not I simply do not know
>>> without knowing LWM2M and since there are no open specs there is
>>> little help you can expect. I have no clue about the interaction model
>>> of OMA LWM2M nor do I know what LWM2M_Device is etc.
>>
>> The specs are publically available for download at no cost.
>>
>> Here is the link:
>> http://technical.openmobilealliance.org/Technical/technical-information/release-program/current-releases/oma-lightweightm2m-v1-0
>>
>> You want to look at the 'Technical Specification'.
> 
> They are not open, I have to accept certain legal terms to get
> access. In particular:
> 
>   use all or any part of a Document as part of a specification or
>   standard not emanating from the Licensor without the prior written
>   consent of the Licensor
> 
> I might already need a written consent if I post an example here since
> everything posted to an IETF list may be considered a contribution.
>  
>> The registry for the objects are also public and available in a nicely
>> written page (similar to what IANA provides for the IETF):
>> http://technical.openmobilealliance.org/Technical/technical-information/omna/lightweight-m2m-lwm2m-object-registry
>>
> 
> Looking at examples to infer what the semantics of the schema are is
> not what I am going to spend my time on.
> 
>> There is no permission that needs to be obtained IMHO, if I understand
>> the OMA copyright policy correctly.
> 
> See above.
> 
> /js
>