11:39:50 <RRSAgent> RRSAgent has joined #rax
11:39:50 <RRSAgent> logging to http://www.w3.org/2016/10/14-rax-irc
11:49:07 <fsasaki> meeting: rax cg
11:49:10 <fsasaki> chair: Christian
11:49:14 <fsasaki> scribe: fsasaki
11:49:31 <fsasaki> agenda: https://lists.w3.org/Archives/Public/public-rax/2016Oct/0002.html
11:49:35 <fsasaki> regrets+ phil
11:49:37 <fsasaki> present+ felix
11:52:30 <cdirschl> cdirschl has joined #rax
11:53:11 <cdirschl> chair: cdirschl
11:53:23 <cdirschl> scribe: cdirschl
11:54:00 <cdirschl> meeting: rax
11:54:14 <cdirschl> rrsagent, make log public
11:54:36 <cdirschl> present+ cdirschl
11:59:03 <fsasaki> scribe: fsasaki
12:25:40 <quentin> quentin has joined #rax
12:26:00 <quentin> sorry for joining late
12:26:51 <quentin> we are leveraging JSON-LD to store triples in NoSQL databases
12:31:20 <fsasaki> topic: discussion on group scope
12:31:32 <fsasaki> present+ evian, quentin
12:31:39 <RRSAgent> I have made the request to generate http://www.w3.org/2016/10/14-rax-minutes.html fsasaki
12:32:37 <fsasaki> quentin: json-ld allowing to store triple info in more "performant" serialzation, e.g. for no sql DB
12:34:17 <fsasaki> jean-pierre: XML <> RDF discussion for years. many want to go from an XML schema to RDF
12:34:35 <fsasaki> ... people doing automatic translation, but no good results so far.
12:34:44 <fsasaki> ... what does it (not mean) to go from XML to RDF
12:35:14 <fsasaki> quentin: agree, a lot of transformation solutions, but no agreed standardization
12:35:34 <fsasaki> ... W3C having XML > RDF transformation, that is not available
12:35:45 <fsasaki> ... one reason may be: there are too many serizalizations
12:36:11 <fsasaki> ... publisihing industry is XML oriented. They don't understand that RDF is not XML
12:36:25 <fsasaki> ... XSLT can get you to RDF, but not to the end, since you deal with a graph
12:36:42 <fsasaki> ... you loose information and then need to create libraries
12:36:59 <RRSAgent> I have made the request to generate http://www.w3.org/2016/10/14-rax-minutes.html fsasaki
12:37:15 <fsasaki> present- evian
12:37:20 <fsasaki> present+ jean-pierre
12:37:47 <fsasaki> jean-pierre: can do conversion without any issues
12:39:08 <fsasaki> ... I don't believe that we can come up with a standard way to go from XML > RDF
12:39:56 <fsasaki> felix: gathering examples could help
12:40:08 <fsasaki> jean-pierre: you can learn from that
12:40:42 <fsasaki> ... I am using RDF/XML instead of turtle, since most of the data I get is XML, I am using XSLT, for me it is much better to go from XML to XML serialization
12:41:22 <fsasaki> https://www.w3.org/community/rax/wiki/Draft_Material#Enrichment_in_Localization_and_Translation
12:42:08 <fsasaki> christian: part of our request was: give us a problem, use case, and then make clear what that means
12:43:14 <fsasaki> ... that will make it clearer
12:44:21 <fsasaki> felix: have on the call agenda to have introduction of examples
12:44:33 <fsasaki> christian: agree, to add that to the normal agenda
12:45:22 <fsasaki> jean-pierre: can provide example after mid november
12:46:09 <fsasaki> discussion on further examples to be provided
12:46:40 <fsasaki> action: felix to provide example for next call
12:47:20 <fsasaki> action: phil to introduce https://www.w3.org/community/rax/wiki/Draft_Material#Enrichment_in_Localization_and_Translation during the next call
12:48:46 <fsasaki> adjourned
12:48:52 <RRSAgent> I have made the request to generate http://www.w3.org/2016/10/14-rax-minutes.html fsasaki
12:49:05 <fsasaki> next call in two weeks
12:49:07 <RRSAgent> I have made the request to generate http://www.w3.org/2016/10/14-rax-minutes.html fsasaki