11:59:44 RRSAgent has joined #sdw 11:59:44 logging to http://www.w3.org/2015/09/16-sdw-irc 11:59:46 RRSAgent, make logs world 11:59:46 Zakim has joined #sdw 11:59:48 Zakim, this will be SDW 11:59:48 I do not see a conference matching that name scheduled within the next hour, trackbot 11:59:49 Meeting: Spatial Data on the Web Working Group Teleconference 11:59:49 Date: 16 September 2015 11:59:54 present+ kerry 12:00:01 chair: ed parsons 12:00:06 scibe: kerry 12:00:12 present+ MaikRiechert 12:00:12 scribe: kerry 12:00:18 eparsons has joined #sdw 12:00:21 present+ jtandy 12:00:22 scribenick: kerry 12:01:07 trackbot, start meeting 12:01:09 RRSAgent, make logs world 12:01:11 Zakim, this will be SDW 12:01:11 I do not see a conference matching that name scheduled within the next hour, trackbot 12:01:12 Meeting: Spatial Data on the Web Working Group Teleconference 12:01:12 Date: 16 September 2015 12:01:22 RRSAgent, make logs public 12:01:31 present+ eparsons 12:01:34 regrets + andreas harth 12:01:46 regrets+ frans knibbe 12:02:00 regrets+ bart van leeuwen 12:02:02 Meeting: SDW WG Weekly 12:02:59 regrets+ andreas harth 12:03:48 PhilippeThiran has joined #sdw 12:03:55 people in the room at the ogc meeting keyworth: 12:04:05 Alejandro_Llaves has joined #sdw 12:04:07 present+ PhilippeThiran 12:04:21 present+ Alejandro_Llaves 12:04:23 AndreaPerego has joined #sdw 12:04:30 jeremy tandy, chris little, phil archer, josh lieberman 12:05:15 present+ AndreaPerego 12:06:15 ... linda van brink, simon cox, robert.., ,missing these> christine perey, ed parsons 12:06:32 Topic: Approve Minutes 12:06:44 topic: approve minutes 12:07:06 +1 12:07:08 http://www.w3.org/2015/09/09-sdw-minutes.html 12:07:09 +1 12:07:11 joshlieberman has joined #sdw 12:07:11 +1 12:07:14 Linda has joined #sdw 12:07:15 +1 12:07:22 present+ Linda 12:07:22 AZ has joined #sdw 12:07:29 +1 12:07:40 RESOLVED: Accept last meeting minutes 12:07:47 RESOLVED: http://www.w3.org/2015/09/09-sdw-minutes.html minutes approved 12:07:50 jonblower has joined #sdw 12:07:59 Topic: Patent Call 12:08:25 https://www.w3.org/2015/spatial/wiki/Patent_Call 12:09:07 topic: Its about time 12:09:20 ChrisLittle has joined #sdw 12:09:49 present+ AZ 12:10:53 Rachel has joined #sdw 12:11:06 present+ Rachel 12:11:41 Fen Pan: owl time was 10 years ago for my phd -- not state of the art any more 12:11:56 s/fen/Feng/ 12:12:09 .... motivation was semantic web and naturl language 12:12:49 ... e.g online shopping , user preferences, service time 12:13:22 ... question answering, event ordering, summarization 12:13:30 MattPerry has joined #sdw 12:13:40 ... in NL temporal information is vague 12:14:25 present+ MattPerry 12:14:31 .... now used with owl-s and TimeML in timebank corpus 12:15:04 ... also for data integration, video, GIS 10 years ago, .. 12:15:30 ...was once DAML-time -- for web pages and web services 12:15:59 LarsG has joined #sdw 12:16:09 ...goal to separate from other ontologies, alos avail as FOL axioms 12:16:11 present+ LarsG 12:16:25 ... includes Allen relations 12:17:20 ... duration descriptions as intervals or instants -- how long does it last? 12:17:45 ...clocks and calendars 12:18:13 ...temporal aggregates extends basic primitives 12:18:23 ...eg 4 consecutive sunday 12:18:50 ... goal to handle any collection of entities 12:19:10 ... complex aggregates 12:19:45 ... e.g. every other Monday in every 3rd month 12:22:57 ....next speaker: simon cox 12:23:12 ... minor extension to the barcelona presentation 12:23:26 ... small extension to owl-time 12:25:58 ... review of Allen's 13 interval relations 12:27:16 ...tied to gregorian calendar 12:27:45 ... misses geologic time such as counting backwrds and geological periods 12:28:05 ... also Hebrew calendar, GPS time, Unix time etc 12:29:29 ...propose to an extension that generalises the datetimedescription and temporal coordinates on a scale 12:29:56 ... this is a superclss of the original date-time 12:30:33 ... proposed generalisation supports indication of temporal reference system and more representations 12:30:54 ...preserves interval calculus 12:31:03 ...no change for owl-time users 12:31:24 ...applause 12:31:48 next speaker: chis little 12:32:05 Linda has joined #sdw 12:32:15 s/chis/chris/ 12:32:30 chris: have you got time? 12:33:17 slides are not fullscreen, maybe wrong screen shared 12:33:19 ...about a year ago we wanted a best practice doc in OGC 12:33:31 ... we have some ideas 12:34:28 the sound is not clear now... 12:35:27 sound is good 12:35:57 better no! 12:36:00 ... idea of tmporal regimes 12:36:06 now* 12:36:17 ...people confuse events, clocks and ... 12:37:12 jtandy has joined #sdw 12:37:12 ...events are ordered in time , coutably infinite, can do allen operators but cannot measure area, topological only 12:37:42 ... Clcks are different 12:38:01 ... ordered time instants 12:38:14 s/Clcks/Clocks/ 12:38:18 ... no intermediate times... can do some interval stuff 12:39:15 ... eg atomic time. most clock times, bad notation if precision too great (?) 12:40:06 ... coord ref system definable e.g. years before Christ, years before current year, 12:40:22 .... type 3 is calendar 12:40:54 ..a the class of calendards is disjoint with the class of CRSs! 12:41:31 ... type4: astronomical - requires observation of mon=on,sun,stars 12:42:01 ... type 5: Notation is not a timescale, CRS or calendar 12:42:26 < lost a lot of sound> 12:42:59 ... what notation is appliable for each regime? 12:43:19 ...here be dragons 12:45:54 ...welcom ray denenberg 12:46:06 Kerry, can you mute your mic during presentations as we can hear you typing? 12:46:09 ... ray can only do voice? 12:46:38 s/welcom/welcome/ 12:52:37 ... extended date time format 12:53:06 date time string more expressive than iso8601 12:54:11 ...some of 8601 is redundant-- seems good to restrict it, and also extend it for some common things that are missing 12:54:25 ... level 0 is a profile 12:54:36 ...level 1 is simple extension 12:55:09 .... level 2 is more complex 12:55:26 ... motivated by bibliographic data but spread widely 12:56:08 ... only thing we need from 8601 is date, time and interval 12:56:32 ... only 4 digit years and extended form (hyphnes) 12:57:15 ... data and time has one of three forms 12:57:58 ... interval is date/date... no times no durations but different precisions ok 12:58:06 ...now level 1 12:59:31 ... uncertain: ? , approx: ~, unspecified: u, 13:00:14 ... extended interval: "unknown" or "open" 13:01:47 ... years exceeding 4 digits: Y at beginning of string (but only the year is writable) 13:02:24 ... season: 21-24 are season indicators, look like months 13:03:07 ...level 2 allows these things to be mixed 13:03:49 ... e.g date with approx day but we are sure about the month and the year 13:04:59 ...level2 year can be written in exponential form with significant digit precision indicator 13:05:51 ... now a new group on ISO8601 part 2 iso tc 154 wg 5 13:06:09 ... links to more info in slides 13:06:23 jonblower has joined #sdw 13:06:43 applaus 13:06:45 13:07:01 s/applus/applause/ 13:07:45 chris: i can see that route, but concern it is north american eg seasons (wet/dry) 13:08:02 ....p for precision may be confused with periods 13:08:15 ...u for unspecified looks like German for hour 13:08:43 Ray: all that is in the English version-- other languages available too 13:10:17 simon: only a subset of 8601 is used as other markup is used for the rest in Web languages 13:10:39 ... pushing it into short space may be outdated 13:10:55 ... sceptical about the coding 13:11:12 ... precision looks interesting 13:11:37 .... may be not applicable in this context 13:12:15 Ray: would like to see it as a datatype like in xsd 13:13:01 jeremy: many good use cases around this 13:13:07 Topic: Coverages and Earth Observation in Linked Data 13:13:19 Questions I would have asked Ray - what is the difference between "uncertain" and "approximate" time? 13:13:50 Also, a use case - it's common to find a photograph where you know what month (or even day) it was taken (e.g. a birthday) but you don't know what year it was taken in. 13:14:35 http://www.w3.org/2015/ceo-ld/ 13:15:02 topic: CEO-LD 13:15:27 phila: concenr that interenst and capacity on coverages is limited 13:15:37 s/concenr/concern 13:16:32 phil: bringing in the uk stallite centre and chines people from <> and Martin sweeting from surrey 13:16:49 ...they cannot write the standard... that is our job. 13:17:20 jitao yang and manolis kouubarakis (+ another?) will be editors 13:17:36 ...close cooperation but we are in charge! 13:18:06 ... prg j bolton is behind this ... the earth began in edinburgh 13:18:16 ... thats where the big bang was.. 13:18:27 ...the queen did it all... 13:19:23 ... 13:19:34 Topic: Best Practice Doc. Planning 13:19:54 topic: best practices 13:20:15 jeremy: BP is the BIG deliverable 13:20:27 ... progress to date 13:21:00 ... agreed 7 common themes 13:21:05 https://www.w3.org/2015/spatial/wiki/BP_Consolidated_Narratives 13:21:38 .... wanting a narrative form 13:21:59 ... reads out the 7 themes 13:22:31 +1 subject to a later check on completeness wrt use cases 13:23:00 ChrisLittle has joined #sdw 13:23:06 jeremy: e.g. 1.6 13:23:31 ...are these the right 7? 13:23:37 zakim presesnt+ 13:23:50 zakim present+ 13:24:18 jon: why should i do anything differnt for linked data -- why not GIS solution? 13:24:39 Ed: also looking at a broader community without that baggage 13:25:12 jeremy: yes need to address this in introdcution -- these are are reasons for revisiting these things 13:25:29 s/introcution/introduction/ 13:25:57 action: bl;ower 13:26:23 ACTION: jon blower to do soething kerry did not catch 13:26:23 Created ACTION-77 - Blower to do soething kerry did not catch [on Jon Blower - due 2015-09-23]. 13:26:39 action: blower to provide text around value add of following the BPs 13:26:39 Created ACTION-78 - Provide text around value add of following the bps [on Jon Blower - due 2015-09-23]. 13:27:00 jeremy: not just data on a USB stick. Not necessarily RDF though. 13:27:26 (Just for the record, I volunteer to do this based on info gathered in the MELODIES project, http://melodiesproject.eu) 13:27:27 jeremy: are we talking about linked data here? 13:27:34 kerry +1 13:27:39 ed +1 13:28:06 jeremy: consensus sought -- are there other views? 13:28:43 ed: different platform and methodology to waht we have done before -- but building on all that has gone before 13:29:01 phial: does not have to be rdf 13:29:23 phil: in theory not just rdf but in practce probably yes 13:29:34 ..... uris are critical 13:29:58 .... do we spend the net 37 montjs talking about urls and uris???? 13:30:14 jeremy: original web architecture 13:30:23 ... is being checked over 13:30:41 .... we have consensus that linked data perspective is key to out work 13:31:19 ... does not need to be so obviously rdf .... gml was rdf once long ago.. 13:31:36 ...what makes a good best practice? what makes it come alive? 13:31:58 ...could use json-ld sometimes 13:32:09 ...maybe geojson where appropriate 13:32:26 ..."coming at it from a linked data perspective" 13:32:52 jonblower: this is key, but may not be linked data everywhere 13:33:18 jeremy: this will come out of our discussions especially around ceo-ld (coverages) 13:34:07 peter: surprised at non-evolutionary... in the end rdf is just another encoding (like XML was) 13:34:32 ... can be represented in netcdf and xml and rdf 13:34:54 jeremy: that is why we have "publishing with clear semantics" 13:35:26 ... our best practice will answer how to do this 13:35:51 ... big new idea is that we want to be able to talk about stuff about the data right inside the dataset 13:36:08 .... number 4 and number5 are realted in some stated way 13:36:32 peter: 13:36:52 Jeremy: its a global reference rather than a local reference this time 13:37:07 ....web scale foreign keys 13:37:46 ed: you will publish your data at the most granular level you feel happy with on the web 13:38:55 jeremy: what are the methodologies that will go in the best practice doc? e.g for geospatail we know htere are at least 4 vocabs with overlap 13:39:20 ...or job is to say in this case use X, or ain all cases use X 13:39:27 s/ain/in/ 13:40:07 peter: different concepts need to be delineated... (?) 13:40:24 : is the order of the issues meaningful? 13:40:33 ed: not yet 13:40:49 jeremy: top of list might be geometry 13:41:37 SimonCox has joined #sdw 13:42:05 peter: coverage is my topic... will there be one overarching ... need to be clear on ... 13:42:09 http://w3c.github.io/sdw/bp/ 13:42:28 jeremy: phil has created a skeleton 13:42:50 phil: doing this is easy this time 13:43:04 ... everything is on github 13:43:10 ...respec does clever stuff 13:43:30 ... a psace for ogc doc number when assigned 13:43:48 ... a price if you know who william lloyd was 13:44:01 13:44:20 Jeremy: our BP doc looks ike this now 13:44:33 s/proce/prize/ 13:44:40 s/price/prize/ 13:45:25 https://www.w3.org/2015/spatial/wiki/BP_Structure_Examples 13:45:32 jeremy: what makes a good practice 13:46:01 jeremy: asked contributers to identify where they have sen bp before 13:46:12 ed: eddystone project at google 13:46:28 ...connenct your computer to prjector by speaking, uses bluetooth 13:46:46 s/connenct/connect/ 13:47:31 ...balances a formal description with code snippets for developers 13:48:01 chirs: 150107 is best practice OGC doc number! 13:48:31 Allejandro: ? 13:49:26 allejandro: data on the web best practice is good becuase it summariesed the pocedure well at the front with more details linked to those steps 13:49:51 /me : I'm back. 13:49:58 s/pocedure/procedure/ 13:50:13 s/chirs/chris/ 13:50:19 s/\/me : I'm back.// 13:50:50 jeremey: api oc for google maps for mixture of tutorial and sample code 13:51:09 ...but you get what you pay for -- this would have ben a big effort for thousands of readers 13:52:05 ...plan to identify technologies and methodologies for each best practice next. assign to members of wg to write up and buld code snippets 13:52:25 ...one of the seven to be lead exemplar 13:52:43 .... what should that be? 13:52:52 s/150107/15-107/ 13:53:05 +q 13:53:45 floor: how do people participate if they have only an hour? 13:54:11 https://www.w3.org/2015/spatial/wiki/BP_Consolidated_Narratives 13:54:16 jeremy: using the wiki.. get started using the mailing list 13:54:45 ... mail on the mailing list most useful now 13:54:56 floor == Mark Hedley, Met Office 13:55:24 ed: 1.1 or 1.4 13:56:16 kerry: semantics 13:56:34 ed: tosses coin 13:56:54 Topic: Geonovum tender for a SDW testbed 13:56:58 jeremy: linking data it is. 13:57:10 resolved: focus on linking data narrative first 13:57:32 Topic: linda on geonovum tender 13:58:01 linda: first news item on geonovum website mentions request for tender for testbed 13:58:49 linda: this doc describes what we want to o -- want to help to get spatail data infrastructures to be a success 13:58:52 http://www.geonovum.nl/sites/default/files/Invitationtotender-SDWtestbed.pdf 13:59:18 ... having trouble with traditional spatail standards but we need somequestions answered. 13:59:36 ... decided not to answer these ourselves but to ask the market. 13:59:53 ...can see the questions and how to go about responding 14:00:31 ...could be a consortium or a sngle company or... 14:00:57 jeremy: overlap between your questions and ours in SDWWG 14:01:14 linda: any questions direct to me 14:01:44 rrsagent, draft minutes 14:01:44 I have made the request to generate http://www.w3.org/2015/09/16-sdw-minutes.html ChrisLittle 14:01:44 meeting closed midnight 14:01:44 Bye 14:01:45 bye, thanks! 14:01:58 bye 14:02:04 bye 14:02:07 bye! 14:02:15 bye 14:02:23 thanks Kerry (PP Phil) 14:02:27 rrsagent, make logs world 14:02:37 by all thanks Kerry !! 15:56:28 Zakim has left #sdw