05:03:52 RRSAgent has joined #webapi 05:03:52 logging to http://www.w3.org/2015/10/28-webapi-irc 05:03:57 Zakim has joined #webapi 05:04:09 meeting: W3C Web API 05:04:14 scribe: Antonio 05:04:17 scribenick: tripu 05:04:18 q? 05:04:20 agenda? 05:04:24 I have made the request to generate http://www.w3.org/2015/10/28-webapi-minutes.html tripu 05:05:01 chair: vivien 05:20:19 tripu has changed the topic to: Slides: http://www.w3.org/2015/10/web-api-tpac/?full#Cover 05:43:47 timbl has joined #webapi 05:51:51 dom has joined #webapi 05:55:08 dom has joined #webapi 06:20:53 timbl has joined #webapi 06:45:32 Chair: Vivien 06:58:39 I have made the request to generate http://www.w3.org/2015/10/28-webapi-minutes.html tripu 07:05:23 mkaki has joined #webapi 07:05:48 dom has joined #webapi 07:08:32 David_clarke has joined #webapi 07:10:35 vivien: hello and welcome 07:10:48 vivien: Why the need for this data from W3C? 07:11:07 ... people will be able to build more things with this data; and also it's data we want to give back to the community 07:11:22 ... It's a public API; tested in the last weeks/months. 07:11:37 ... It returns data in JSON format; ready to test at api-test.w3.org. 07:11:56 ... Follow our project on GH; we keep track of issues there 07:12:16 ... The code itself is *not* on GH; as it's closely related to some of our internal tools 07:12:25 scribe: tripu 07:12:47 ... You can get info about specs, groups, orgs and users right now 07:13:12 vivien: You can get information from, eg invited experts, and all users who are participating in WGs 07:13:28 ... http://www.w3.org/2015/10/web-api-tpac/?full#api-sample 07:13:40 ... here's a simple example: the HTML5 spec 07:13:56 [vivien going through all the properties/fields on the slide] 07:13:59 I have made the request to generate http://www.w3.org/2015/10/28-webapi-minutes.html tripu 07:15:08 vivien: Among other things, we have links to related versions of a spec, eg previous version 07:15:22 http://www.w3.org/2015/10/web-api-tpac/?full#apikey 07:15:43 vivien: You can create your personal API keys from your W3C user profile page 07:16:04 ... keys can be revoked, regenerated, etc. Also, they may or may not be associated to a specific origin. 07:16:21 http://www.w3.org/2015/10/web-api-tpac/?full#apikey2 07:16:44 [vivien showing an example of real JSON returned by the API, and following links to new pieces of information] 07:17:27 [vivien following some of the links on http://www.w3.org/2015/10/web-api-tpac/?full#4 ] 07:18:11 -> https://api-test.w3.org/groups/47318?apikey=dr7ri39me1kckkkk44sk8400sw4cgc4 Example of a group info 07:18:26 vivien: name of the group, its type, list of chairs, team contacts, participants... 07:18:51 ... info about the charter(s) of the group: extension, IPP, URL to join the group... 07:19:26 https://api-test.w3.org/domains/41381?apikey=dr7ri39me1kckkkk44sk8400sw4cgc4 07:19:52 vivien: Domains: page of the domain, groups it "contains", resources (repos, channels, lists)... 07:20:08 https://api-test.w3.org/affiliations/9826?apikey=dr7ri39me1kckkkk44sk8400sw4cgc4 07:20:47 vivien: Organisation: home page, participants (info that is already publicly available) groups that this company is involved on... 07:22:24 @participant: does this allow "joint" queries, eg participants of group X who are also in group Y? 07:22:38 vivien: Let's talk about that later 07:23:01 s/@participant:/DavidClarke:/ 07:23:15 http://www.w3.org/2015/10/web-api-tpac/?full#8 07:23:30 vivien: Two options for authenticating users of the API. 07:23:35 Zakim has left #webapi 07:23:56 http://www.w3.org/2015/10/web-api-tpac/?full#9 07:24:13 vivien: we have pagination, to avoid answers that are too long 07:24:17 I have made the request to generate http://www.w3.org/2015/10/28-webapi-minutes.html tripu 07:24:36 vivien: More about all this on the GH site. 07:24:54 vivien: Coming back to David Clarke's question... 07:25:38 ... right now, you'd have to make 2 queries, and then merge the results. 07:26:04 s/"joint"/"join"/ 07:26:47 vivien: For the i18n group, for example, you get a list of participants, each with a URL with details 07:27:10 ... if you were to follow those links, that would be already ~76 requests. 07:27:31 ... To avoid that, and to get more information from just one request, we have the "embed" parameter 07:28:29 ... Also, the pagination might help to reduce the # of requests. 07:28:46 q? 07:29:06 vivien: The API is JSON, so probably you want something else on top of that 07:29:14 ... We have written Apiary for that 07:29:25 -> https://github.com/w3c/apiary Apiary 07:29:58 vivien: It's a declarative JavaScript library; the project is on GH. 07:30:08 http://www.w3.org/2015/10/web-api-tpac/?full#apiary-sample 07:30:33 vivien: we specify our API key, and the ID of the (group|domain|user|whatever) we need... 07:30:59 ... then put "placeholders" where we need the actual data. 07:31:19 http://www.w3.org/UbiWeb/Overview_tmp.html 07:31:45 vivien: This example shows how to use Apiary to populate info about a particular domain... 07:32:03 ... on this page, the list of activities, with links, comes from the API. 07:32:32 ... On GH you have a link to the API documentation: parameters, how to use the keys... 07:32:40 I have made the request to generate http://www.w3.org/2015/10/28-webapi-minutes.html tripu 07:32:58 junichi-hashimoto has joined #webapi 07:33:36 vivien: Some people are already using the API in the real world. 07:34:04 vivien: For example, GH contributions may be checked against the ID of the committer, using the API. 07:34:46 DavidClarke: I haven't seen info about translations, eg of specs. 07:34:58 ted: We don't have info about those translations. 07:35:37 DavidClarke: By definition, the i18n WG has a lot of material translated. If my preferred language were, eg, Japanese, I might want that if it's available. 07:36:28 vivien: All this info is coming from our DB; all that I've shown now -- we only have the English version; no translations. 07:36:42 ... as far as the DB is concerned, there's only English. 07:37:40 DavidClarke: Too often, we present the English version and expect that to be "good enough" [for all users]. 07:38:23 ted: I'm not against i18n, but this is an early version and... 07:38:52 DavidClarke: I'm fully aware. I'm saying it's easier to embed support for i18n at this early stage, as opposed to doing that later. 07:40:59 vivien: I'll have to look at how to do that in JSON-LD. Any pointers? 07:42:06 DavidClarke: BCP-45...? BCP-64...? 07:42:21 vivien: Not those ones; if you could send that to us later. 07:42:34 vivien: Who would be the best person as a contact in the i18n WG? 07:42:40 DavidClarke: r12a. 07:43:31 ... I come across so many projects where encoding and language were not taking into account from the beginning. 07:45:25 So we don't have info about languages in the DB? 07:45:35 vivien: no that I'm aware of. There might be some, but we assume it's English. 07:46:04 ted: We'll need to keep that information, because... well, machine translation isn't good. 07:46:48 ... We get people who enter their name localised, using non-English chars, etc. 07:46:53 ... What would be the right way to deal with those cases? 07:47:34 [DavidClarke going through various examples of person names that are difficult to infer, in terms of language.] 07:54:45 [David & Vivien looking at some localised testimonials from members; there we do know the language...] 07:58:09 [Vivien & David discussing the benefits of i18n in relation with the API] 07:59:38 I have made the request to generate http://www.w3.org/2015/10/28-webapi-minutes.html tripu 08:23:56 RRSAgent, bye 08:23:56 I see no action items