12:11:29 <RRSAgent> RRSAgent has joined #wot-uc
12:11:29 <RRSAgent> logging to https://www.w3.org/2021/07/13-wot-uc-irc
12:11:35 <kaz> meeting: WoT Use Cases
12:12:09 <kaz> present+ Kaz_Ashimura, Christian_Block, Michael_Lagally, Michael_McCool, Sebastian_Kaebisch, Thomas_Jaeckle
12:13:42 <kaz> Agenda: https://www.w3.org/WoT/IG/wiki/IG_UseCase_WebConf#Agenda_13.7.
12:14:07 <kaz> topic: ECLASS liaison
12:14:20 <kaz> cb: (gives introduction)
12:14:43 <kaz> present+ Tomoaki_Mizushima
12:16:07 <kaz> ml: sorry but would like to remind you of the W3C patent policy
12:16:11 <kaz> kaz: mentions the PP
12:16:16 <kaz> cb: ok
12:16:29 <kaz> ... (starts to talk about his slides)
12:16:51 <kaz> ... basis of ECLASS
12:17:11 <kaz> ... hierarchical standard for master data to classify and describe products and services
12:17:31 <kaz> ... data supply chain
12:17:41 <dezell> dezell has joined #wot-uc
12:17:59 <kaz> ... data chain between product descriptions provided multiple companies
12:18:05 <kaz> ... standardization by ECLASS
12:18:18 <dezell> present+ David_Ezell
12:18:23 <kaz> ... fact & figures
12:18:46 <kaz> ... 4000 users, 19000 properties ,150 active members
12:18:59 <kaz> ... 45000 classes
12:19:16 <kaz> ... used internationally
12:19:24 <kaz> ... 16 languages
12:19:47 <kaz> ... more facts
12:19:59 <kaz> ... ISO/IEC based data model
12:20:08 <kaz> ... ISO 13584-42 / IEC 61360
12:20:19 <kaz> ... data transfer ISO 29002
12:20:34 <kaz> ... more facts
12:20:42 <kaz> ... consistent use
12:20:51 <kaz> ... international and multilingual
12:21:01 <kaz> ... more facts
12:21:23 <kaz> ... cross-sector, compatible to other standards
12:22:10 <kaz> i|mentions the PP|-> https://www.w3.org/Consortium/Patent-Policy-20170801/ W3C Patent Policy|
12:22:22 <kaz> ... conceptual data model
12:22:40 <kaz> ... ECLASS - structural elements
12:22:57 <kaz> ... elements and definitions
12:23:35 <kaz> ... classification class, application class, keyword, property, synonym, unit, value list, value, ...
12:23:39 <kaz> ... IRDI
12:23:59 <kaz> ... each structural element has an IRDI
12:24:24 <kaz> ... ISO/IEC 6523 and ISO/IEC 11179-6
12:24:34 <kaz> ... ECLASS basic vs advanced
12:25:05 <kaz> ... basic: all characteristics are provided flat in a one-dimensional list
12:25:16 <kaz> ... ECLASS advancd cocnepts
12:25:34 <kaz> ... aspect, block, cardinality, polymorphism
12:26:09 <kaz> ... how structural elements relate
12:26:30 <kaz> ... CC-advanced AC
12:27:12 <kaz> ... reference property is not included in the main body
12:27:17 <kaz> ... ECLASS use cases
12:27:38 <kaz> ... BMEcat, ISO 29002-10, AutomationML, Asset Administration Shell, OPC-UA
12:28:12 <kaz> ... new use case for WoT Thing Description to support semantic uniqueness
12:28:21 <kaz> ... dictionary exchange
12:28:46 <kaz> ... change requests -> eclassdownload.com -> ECLASS users
12:29:00 <kaz> ... dictionary exchange formats
12:29:13 <kaz> ... CSV, XML (Onto XML), ...
12:29:21 <kaz> ... RDF goal and process
12:29:32 <kaz> ... ECLASS -> RDF -> WoT TD
12:29:52 <kaz> ... ECLASS as RDF in W3C WoT TD (Draft)
12:30:04 <kaz> ... (example TD code)
12:30:38 <kaz> ... IRDI_0173_1_01_AKE525_013 for Thing
12:30:48 <kaz> ... also support for properties
12:31:22 <kaz> q?
12:31:33 <kaz> ... questions?
12:31:41 <kaz> ml: thanks!
12:31:57 <kaz> ... we mange question queue using the IRC channel
12:32:06 <sebastian> sebastian has joined #wot-uc
12:32:09 <sebastian> q+
12:32:35 <ChristianBlock> ChristianBlock has joined #wot-uc
12:32:41 <kaz> ack s
12:32:48 <kaz> sk: regarding the example
12:32:50 <kaz> q?
12:32:54 <kaz> q+
12:33:00 <kaz> ... not perfect yet
12:33:18 <kaz> ... IRDI as an ID is complicated
12:33:39 <kaz> ... this example is OK to show the ECLASS concept
12:33:52 <kaz> ... we can use a context file to manage the information
12:34:12 <kaz> ... to manage the detailed information, e.g., the manufacture
12:34:29 <kaz> ... mapping to the context file is important
12:34:31 <McCool> q+
12:34:39 <kaz> q-
12:34:41 <kaz> q+
12:34:54 <kaz> ml: agree
12:35:12 <kaz> ... we can simply property name, etc.
12:35:20 <kaz> sk: possibly annotation as well
12:35:47 <kaz> ... btw, support for multiple language is nice
12:36:18 <kaz> ... ECLASS provides very powerful mechanism
12:36:29 <kaz> ml: device class and device model
12:36:35 <kaz> ... same as the Thing Model?
12:36:44 <kaz> sk: think could be used for the Thing Model as well
12:36:59 <kaz> ... and can be adapted to the Thing Description
12:37:15 <kaz> mm: we duplicate things right now
12:37:31 <kaz> ... probably should have general discussion on subsets
12:37:33 <kaz> ... to be applied to Thing Model
12:37:45 <kaz> ... the example shows metadata of the Thing as the top level
12:37:47 <kaz> ack mm
12:37:50 <kaz> ack m
12:38:02 <kaz> sk: you can use the actions as well
12:38:17 <kaz> ... sometimes devices have voltage, etc.
12:38:33 <kaz> ... you can use that detailed level of terms as well
12:38:39 <kaz> q?
12:38:52 <kaz> mm: useful to see use cases about the details
12:39:00 <kaz> ... set of interactions, etc.
12:39:07 <kaz> ... how to mark up the semantics
12:39:18 <kaz> ... where ECLASS annotation to be applied
12:39:37 <kaz> kaz: yes
12:40:12 <kaz> ... would like to see how to refer to the ECLASS term definitions from TD for some concrete use case
12:40:16 <kaz> ml: good point
12:40:24 <kaz> ... what is the typical use case?
12:40:34 <kaz> cb: there is a catalog
12:40:45 <kaz> ... exchanges the information
12:40:57 <kaz> ... catalogues can be uploaded
12:41:19 <kaz> ... and this data can be reused for applications too
12:41:20 <kaz> q?
12:41:22 <kaz> ack k
12:41:45 <kaz> ... e.g., building control systems including switches and lamps
12:42:07 <kaz> q?
12:43:00 <kaz> ... btw, ECLASS might be able to be the basis for the Thing Model
12:43:12 <kaz> ml: regarding the value
12:43:31 <kaz> ... you had tree-like structure
12:43:42 <kaz> ... do you have more complicated structure than the example?
12:43:49 <sebastian> q+
12:44:10 <kaz> cb: more complex data type is also possible
12:44:34 <kaz> ml: regarding UnitsML
12:44:54 <kaz> cb: XML schema by ISO 13584-32 ontoML
12:45:07 <kaz> ... unit system is based on other schema
12:45:18 <kaz> ml: what kind of units?
12:45:32 <kaz> ... any standards to be referred to?
12:45:52 <kaz> cb: common dictionary is an ISO/IEC standard
12:45:55 <kaz> q+
12:46:29 <kaz> ml: ok
12:46:32 <kaz> ... another question
12:46:41 <kaz> ... how to handle different languages?
12:46:51 <kaz> ... semantic names and structure?
12:47:12 <kaz> cb: maybe Sebastian can provide some answer?
12:47:22 <kaz> sk: language-based context file is available
12:47:35 <McCool> q+
12:47:43 <kaz> ... one context file specific for one language, e.g., German
12:48:07 <kaz> ... would assume lang attribute like TD as well
12:48:18 <kaz> ... possible mapping with that
12:48:39 <kaz> ack s
12:48:42 <kaz> q-
12:48:44 <kaz> q+
12:49:08 <kaz> sk: use cases on retails?
12:49:20 <kaz> cb: possible future use cases
12:49:30 <McCool> sorry, will comment after David
12:49:44 <kaz> de: retail is about categorization
12:50:02 <kaz> mm: how can ECLASS help that purpose?
12:50:09 <kaz> ... specific use cases?
12:50:22 <kaz> ... also we have issues on internationalization
12:50:31 <dezell> q+
12:50:35 <kaz> ... how to handle multiple languages
12:50:38 <kaz> q-
12:50:39 <kaz> q+
12:50:54 <kaz> ack mc
12:51:12 <kaz> ... right now we have identifier for language
12:51:29 <kaz> ... but not sure how to handle every possible language
12:51:39 <kaz> ml: what is the primary domain for ECLASS?
12:51:55 <kaz> cb: electronic products currently
12:52:32 <kaz> ml: question for David
12:52:38 <kaz> ... any similar mechanism in US?
12:52:52 <kaz> de: most of the clarification of products is done by GS1
12:53:03 <kaz> ... code for everything
12:53:35 <kaz> ... but no actual useful categorization for door sensor, etc.
12:53:41 <kaz> s/etc./etc., yet./
12:54:04 <kaz> ... anybody aware of any classification?
12:54:12 <kaz> sk: ECLASS provides some
12:54:15 <McCool> q+
12:54:21 <kaz> ... the question is how far you want to go
12:54:24 <kaz> ack d
12:54:25 <kaz> q-
12:54:29 <kaz> q+
12:54:54 <kaz> ... what kind of items you want to use
12:55:08 <kaz> ... many interesting use cases there
12:55:35 <kaz> de: we do have products categorization for trays, etc.
12:56:13 <kaz> mm: already widely used standard for retails
12:56:31 <kaz> ... ECLASS also might want to work with that
12:56:46 <kaz> ... also about categorization data format
12:56:52 <kaz> ... ECLASS is a possibility
12:57:05 <kaz> ... easier integration for stores would be good
12:57:15 <kaz> ... kind of walking through the process would be beneficial
12:57:23 <kaz> sk: many to say for use cases
12:57:31 <kaz> ack mc
12:57:43 <kaz> ... how to proceed?
12:57:51 <kaz> ml: we could look into their standards
12:58:02 <kaz> sk: also we could think about possible use cases
12:58:06 <kaz> cb: will prepare one
12:58:25 <mlagally> q?
12:59:29 <kaz> kaz: we've been working with IEC CDD guys as well, so just wanted ask if ECLASS format is based that
12:59:29 <kaz> cb: yes
12:59:44 <kaz> ml: could you provide slides?
12:59:53 <kaz> cb: yes
13:01:01 <kaz> ... also data definition available on the ECLASS site
13:01:08 <ChristianBlock> https://www.eclass-cdp.com/
13:01:12 <kaz> q?
13:01:14 <kaz> ack k
13:01:20 <kaz> ml: thanks!
13:02:40 <kaz> ... we'll have the next Use Cases call next week on July 20th
13:02:44 <kaz> [adjourned]
13:02:51 <kaz> rrsagent, make log public
13:02:56 <kaz> rrsagent, draft minutes
13:02:56 <RRSAgent> I have made the request to generate https://www.w3.org/2021/07/13-wot-uc-minutes.html kaz
15:06:13 <Zakim> Zakim has left #wot-uc