08:04:59 RRSAgent has joined #opentrack 08:04:59 logging to http://www.w3.org/2017/04/26-opentrack-irc 08:05:08 Zakim has joined #opentrack 08:06:37 trackbot has joined #opentrack 08:06:43 Sorry, but no Tracker is associated with this channel. 08:07:06 scribenick: tripu 08:07:09 scribe: Antonio 08:07:13 chair: Martin 08:07:17 I'm logging. I don't understand 'draft logs', tripu. Try /msg RRSAgent help 08:07:21 I'm logging. I don't understand 'draft minuts', tripu. Try /msg RRSAgent help 08:07:22 I have made the request to generate http://www.w3.org/2017/04/26-opentrack-minutes.html tripu 08:07:56 Topic: open issues on GH 08:08:06 martin: I see you've replied to some of the issues -- much appreciated 08:08:20 ... I have read your proposals 08:08:32 ... I think it's good to have the conversation on GH 08:08:38 I have made the request to generate http://www.w3.org/2017/04/26-opentrack-minutes.html tripu 08:08:58 martin: About age categories ( https://github.com/w3c/opentrack-cg/issues/5 ) 08:09:28 Andy: It's complicated; it depends on the event. 08:09:41 present Andy Weir 08:09:46 present + 08:09:52 present Andy Robinson 08:09:54 present+ Antonio 08:10:08 present+ Andy Weir 08:10:13 present+ Andy Robinson 08:10:19 ... eg, if you're considering results *after* the event, you'd look at birth dates 08:10:46 ... we have this extra field we introduce on our DB: "is this suitable for rankings?" 08:11:11 ... eg, if wind is too strong, or if the measuring of the fields isn't accurate, that result would not count towards rankings 08:11:39 ... You cannot say "this person is permanently x years old -- all the time, everywhere" 08:12:05 ... All this is worth a little research 08:12:25 ... If you start tagging people on DBs, that may never end 08:12:47 ... About the process: how to suggest small changes, or comment on parts of a document? 08:14:14 tripu: For those small changes, I would suggest creating a new branch with all comments 08:14:31 martin: that's helpful 08:14:41 ... In that way, we could have contributions from all registered members 08:15:03 Andy: In several places you have "more cases and examples" placeholders 08:15:38 ... We could fill those in later; on a separate section, so we don't distract readers too much 08:16:05 martin: I have examples (partial, raw) on separate files 08:16:18 ... that was my own approach, but we could improve and change that 08:16:27 ... I'll continue, eg modelling relay races 08:16:38 ... I want to understand what's missing from there 08:17:03 ... Yesterday, Andy told me it's important to have all legs of relay races annotated with partial and intermediate times, and also the position 08:17:11 ... I agree -- I'll work on that 08:17:24 Andy: OK. We should adapt that, and make something for splits, too. 08:17:39 martin: According to the model, we can represent results of relays, only not intermediate results (legs). 08:17:47 ... It's important, and it's missing right now. 08:17:56 I have made the request to generate http://www.w3.org/2017/04/26-opentrack-minutes.html tripu 08:18:14 martin: I've been thinking about the proposal of having a subset of the vocabulary to share with organisers/partners 08:19:06 ... There's something we call "application profiles" -- we can create those depending on your tools and your specific needs 08:19:44 ... Is that a good approach? 08:20:05 Andy: Sure. It does not matter so much, because all you're writing is converging. 08:20:35 ... As long as we're choosing sensible variable names, later in the summer we can decide "these are the ones we need for this" 08:20:55 ... Maybe it's easier to wait and see what we are exchanging, then decide the subset. 08:22:24 martin: I'd like to emphasize that the goal of the model is to be both flexible and scalable 08:22:34 ... So we'll be able to extend it, depending on needs 08:22:46 ... Every single property is optional -- thus, very flexible. 08:23:39 Andy: We said the primary goal is to exchange results after the event has happened. 08:23:55 ... But it's also important for us to describe the structure of the competition 08:24:02 [Andy shares his screen] 08:24:51 Andy: there are rules and restrictions; combination of distances, ages, organisational needs, etc. 08:26:15 [Andy shares the intricacies of organising a particular championship] 08:26:56 martin: I think this could be represented using our model, eg using iCal to represent the events. 08:27:19 ... Also, using existing technologies, like schema.org 08:27:40 s/"iCal"? ^^^^/iCal (iCalendar) , also schema.org:Events 08:28:02 s/... Also, using existing technologies, like schema.org// 08:29:00 Andy: About times: it's common times change because of DST happen while now and the moment of the event, or because of different TZs 08:29:11 ... We use text fields now; it's a nightmare 08:29:36 martin: Anyway, this could be fixed by your tools, right? 08:29:54 Andy: absolutely. People would be confused, though. 08:30:14 ... Perhaps if we add a section on "programme planning"... 08:30:29 ... Also: who is allowed to compete in each event? Do we need to codify this? 08:30:47 ... eg, sometimes there's a clubs championship, but guests are allowed too 08:31:12 ... a way to say: "this competition is for X and Y" 08:32:05 martin: Good point. 08:32:37 Andy: another example of restrictions: limit to max distance per age 08:32:55 ... eg, young children cannot run long distances 08:33:12 ... Some of these rules are established by @body 08:33:40 Andy: how to flag results as "organisational record", "club record", etc 08:35:36 ... We'll do a screenshot, and try to model these too. 08:36:18 martin: Let's continue on GH's open issues 08:36:28 ... These suggestions look perfect to me 08:36:36 ... That's all from me -- anything else? 08:36:44 Andy: Not really. 08:36:55 ... The next couple of weeks are hectic for us. 08:37:09 ... Our most important date is May 10 08:37:19 ... So we don't have that much time to think about documents until then 08:37:31 ... Once that's over, we'll have plenty of results to share with you 08:37:39 ... So if you want to slow down a bit, that's fine with us. 08:37:48 I have made the request to generate http://www.w3.org/2017/04/26-opentrack-minutes.html tripu 08:38:02 martin: That's fine 08:38:09 ... We can skip the next meeting 08:38:40 s/Andy: Not really./Topic: AOB/ 08:39:01 s/... The next couple of weeks are hectic for us./Andy: Not really. The next couple of weeks are hectic for us./ 08:39:16 Andy: you can keep up the rhythm. 08:39:25 martin: OK, so we'll keep the next meeting anyway. 08:43:20 [Andy & Antonio talking about modern presentation of JSON results, backend, etc] 08:45:30 I have made the request to generate http://www.w3.org/2017/04/26-opentrack-minutes.html tripu 08:45:40 skype? 08:48:28 I have made the request to generate http://www.w3.org/2017/04/26-opentrack-minutes.html tripu 08:50:45 I have made the request to generate http://www.w3.org/2017/04/26-opentrack-minutes.html tripu