Hi all, I just added those definitions in the IoTivity WIKI site. Since, those are the commonly used keywords, it would be nice if develpers in the IoTivity community have a look at it. And please do propose/update the definition if it?s necessary. :)
Thank you. Jay. > 2015. 3. 26., ?? 4:07, ??????(Uze Choi) <uzchoi at samsung.com> ??: > > How about posting it into the IoTivity Site and let people update it. > BR, Uze Choi > From: iotivity-dev-bounces at lists.iotivity.org [mailto:iotivity-dev-bounces > at lists.iotivity.org] On Behalf Of ??? > Sent: Thursday, March 26, 2015 3:25 PM > To: iotivity-dev at lists.iotivity.org > Subject: [dev] Proposing Keyword Dictionary for the IoTivity Project > > Hello all, > > Currently, lots of keywords are used in the IoTivity open-source project in > order to > describe the the features of the stack, service or ideas. > However, it seems like undistinct keywords are being used without > clarlification. > To make the discussion in the opensource dev. community more efficient, > I'd like to create & propose a small dictionary for the IoTivity Project. > (Maybe we could add a page for this on the IoTivity WIKI) > > Here are some of the keywords that I'm working on, and I tried to define all > the keyword > "Resource-Centric" way. > I will be appreciated if everyone take a look at it and give me the feed back > if necessary. :) > > Thank you. > Jay. > > ps. I didn't refer the Spec doc. for now, 'cause I could be biased to the > concepts in the Spec. > Beside, I think it's better to have our(open-source community) own > dictionary so that we could > use this when we tried to sync the concepts between Opensource & > Standard. :) > > ============================= Key words ================================= > > Resource : Object of the network with physical/logical entity (Anything can > be a resource). > Composed with 3 different components. > a. Interface : scheme://address:port/path (= URI) > b. Property : resource type, interface type, > Discoverable/Observable Flags > c. Attribute : data of resource with key-value format > > Resource Server : An Application which provide resource(s) > > Resource Client : An Application which uses resource(s) > > Resource Caching : A Service/feature which stores all the components of the > resource(s). > > Resource Hosting : A Service/feature which stores(caches) only resource(s) > data > with new address:port info (as in Web > Mirroring) > (Plays both the resource server & client > role) > > Resource Directory : A Service/feature which stores(caches) resource > interface with its property info. > (Plays both the resource server & client > role) > > Resource Proxy : A Service/feature which act as an intermediary for > requests from resource clients > seeking resources of resource server (Referred > the Web Proxy Server in WIKI.) > Can be implemented by mixing the Resource > Caching/Hosting/Directory service/feature > > Well-Known Resource : A Resource with Well-knows URI > ex) /oc/core --> for resource > discovery functionality > > Virtual Resource : A resource created as a result of resource hosting. > To off-load the request handling works from > the resource server > where original resource is located > Pat : Since the IoTivity Base use this > keyword inside, I hope there should be a > definition of it. If you have, could > you share use what it is? > If there's no definition of it and > "Well Known Resource" meets the need for > describing the "/oc/core, /oc/d, > etc.." can we change the definition of these > resources from "Virtual" to > "Well-Known"? :) > > Local Resource : A IoTivit Stack point of view, if the stack has the > resource then it's local resource. > > Remote Resource : A IoTivit Stack point of view, if the stack does not have > the resource > but if the other IoTivity stack outside the > process has the resource > then it's remote resource. > > ==================================================================================== > > Jung-hyun Oh. > IoT Solution Lab. | SW R&D Center | SAMSUNG ELECTRONICS CO.,LTD > Mobile +82-10-9890-6731 | Beyond your imagination, Always > > > > _______________________________________________ > 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/20150329/6ad89323/attachment.html>
