Re: [core] Designs to resolve streaming issues in SenML

[Christian Amsüss <[e-mail]>]

Again a short reply before going through the full mail:

On Mon, Jan 18, 2016 at 08:23:00AM -0800, Michael Koster wrote:
> {
> "bn":"/3300/1/",
> “i":[ {"n":"5700","v":"31.3"} ],
> "l":[
>   {"href":"","rel":"self","rt":"temperature core.s","u":"C"},
>   {"href":"5700","rt":"currentValue","u":"C"}
> ]
> }
> 
> Base name, links, and items all are easily mapped to property names
> using a simple JSON-LD context and can be understood and modeled 
> by higher level tools as-is. Removing the “i” or “l” tags gives the modeling 
> tool nothing to use to identify property instances (like base name, links, 
> and items). This is extensible by adding new property  classes (element 
> tags).

I'm curious: Is JSON-LD at all able to derive, from the above (I took
the liberty to abbreviate and add a second rt), statements like

<http://.../3300/1/> a core:s, some:temperature ;
    some:self <http://.../3300/1/>; core:unit "C" ;
<http://.../3300/1/5700> a some:currentValue ;
    core:grp <http://.../3300/1>;
    some:value "31.3"

? That would require matching the bn and n for URI concatenation and
whitespace-splitting the rt attribute.

If it is possible -- great, and it might serve as a criterion for a
bufferlessly parsable SenML that it can be transformed using JSON-LD.
But as far as I remember, it can't do that even for -01, and unless that
can be fixed, I don't see much of a point in using it as an example.

Best regards
Christian

-- 
Christian Amsüss                      | Energy Harvesting Solutions GmbH
founder, system architect             | headquarter:
mailto:[e-mail]  | Arbeitergasse 15, A-4400 Steyr
tel:[phone]                | http://www.energyharvesting.at/
                                      | ATU68476614