[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: Friday's Call
Folks, A bit more homework for Friday or next Friday. Dave From: Considine, Toby <Toby.Considine@unc.edu>
Observer on the TC, so not replying to the TC… I have a long-time interest in approaches to customized/personalized building services that preserve privacy. Much of this is based on energy usage, as described by the Fractal Microgrid model, using minimal service communications
as defined by the OASI smart energy specifications. To apply policy-based directives to operate internally based on these models, I have long wondered if COEL is a path. http://www.automatedbuildings.com/news/feb17/columns/170201110909considine.html For such personalized systems to exist, there has to be databases of what people want, and how they want their services. These databases can either erase privacy entirely, if in the cloud, or be local to the building.
http://www.automatedbuildings.com/news/jun18/columns/180531083003considine.html If local to the building, they must be a way to anonymize and pass to another building, by analogy, the way a Virtual Credit Card can be given to a particular vendor, and be usable only by that vendor. Such an info-BLOB
would need to include some standards-based information as to what services the person wants customized, and what the experience is. It has long seemed to me the COEL is part of this picture. With COEL moving to Committee Specification vote, are you aware of any papers discussing such models of use? As you are discussing W3C interaction, I can’t help but thinking that COEL might well travel alongside VCARD
information (the updated 6350, not the original, and perhaps by reference to rfc 6715). Alternately, a system/building might advertise that it is able to support the COEL goals with these services, or a single service might indicate its importance by reference
to a COEL-defined purpose. WS-Calendar is an OASIS specification developed to support M2M schedule negotiation (not scheduling), and COEL-defined services can only be valued based on schedule. The EMIX model (which incorporates WS-Calendar) defines
models for offering and pricing commodity services whose value is defined by time and location of delivery. WS-Calendar was defined with active participation of the W3C group that works on Calendar standards, and its goals required semantic mappability to
iCalendar (RFC 5545, an update that was developed in parallel to WS-Calendar). It seems that there should be an interesting ontological space in the Venn Diagram of these specifications. tc From:
coel@lists.oasis-open.org <coel@lists.oasis-open.org>
On Behalf Of dave.snelling@uk.fujitsu.com Folks, After picking on Chet for being on holiday on Friday, I am on holiday on Friday. ;-) I just got around to requesting the special ballot for approving the Committee Specification, so that won’t close until next week. If you do hold the call, perhaps keep it informal as there is nothing to do except discuss the W3C avtivity.
In any case, we will talk about that on the 22nd. Have a good weekend.
Dr. David Snelling Fujitsu Mob: +44 (0) 7590-293439 Email:
Dave.Snelling@UK.Fujitsu.com Web:
uk.fujitsu.com
Fujitsu is proud to partner with
Action for Children
P
Please consider the environment - do you really need to print this email?
Unless otherwise stated, this email has been sent from Fujitsu Services Limited (registered in England No 96056); Fujitsu EMEA PLC (registered in England No 2216100) both with registered offices at: 22 Baker Street, London W1U 3BW; PFU (EMEA) Limited, (registered in England No 1578652) and Fujitsu Laboratories of Europe Limited (registered in England No. 4153469) both with registered offices at: Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE. This email is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu does not guarantee that this email has not been intercepted and amended or that it is virus-free. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]