Looks fine.
This is the current Endpoint specification
https://workspace.openconnectivity.org/apps/org/workgroup/architecture_tg/email/archives/201608/msg00004.html
which ATG has just reviewed & is planned for 0.3 spec.
best regards
JinHyeock
On Mon, Aug 1, 2016 at 5:45 PM, ??? <bg.chun at samsung.com> wrote:
> Hi, All
>
> I will implement OCF Endpoint on iotivity.
>
>
>
> Endpoint is Information which indicate available messaging protocol about
> each resource on server.
>
> and resource can has one or multiple Endpoints.
>
>
>
> Below is example of "oic/res" with "eps" parameter which represented
> endpoint on resource.
>
> {
> "href": "/a/light",
> "rt": ["core.light", "core.brightlight"],
> "if": ["oic.if.baseline", "oic.if.ll"],
> "p" : {"bm" : "3", "sec" : "false",},
> "eps": [
> {"ep": "coap://[fe80::a4ca:5493:e96:3cea]:1111", "ttl": 86400,
> "pri": 2},
> {"ep": "coaps://[fe80::a4ca:5493:e96:3cea]:1112", "ttl": 86400,
> "pri": 1},
> {"ep": "coap+tcp://[2001:db8:a::123]:2222", "ttl": 86400, "pri":
> 3}
> ]
> }
>
>
>
>
>
> More detail in jira task(IOT-1207)
>
> https://jira.iotivity.org/browse/IOT-1207
>
>
>
> Plz see concept of endpoint on attached documents on jira, and feedback
> on jira or mai.
>
>
>
> thank you.
>
>
> _______________________________________________
> iotivity-dev mailing list
> iotivity-dev at lists.iotivity.org
> https://lists.iotivity.org/mailman/listinfo/iotivity-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160802/796055c8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 201602111742151_N3WZA6X7.png
Type: image/png
Size: 33527 bytes
Desc: not available
URL:
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160802/796055c8/attachment.png>
