23:28:49 RRSAgent has joined #sdw 23:28:49 logging to http://www.w3.org/2015/10/25-sdw-irc 23:28:51 RRSAgent, make logs world 23:28:51 Zakim has joined #sdw 23:28:53 Zakim, this will be SDW 23:28:53 I do not see a conference matching that name scheduled within the next hour, trackbot 23:28:54 Meeting: Spatial Data on the Web Working Group Teleconference 23:28:54 Date: 25 October 2015 23:30:38 RRSAgent, make logs public 23:31:00 Meeting: SDW TPAC Day 1 23:31:52 rrsagent, this meeting spans midnight 23:32:34 present+ eparsons 23:35:58 Still waiting for a few people... 23:37:38 present+ BartvanLeeuwen 23:42:46 phila has joined #sdw 23:42:48 Linda has joined #sdw 23:44:41 phila has changed the topic to: https://mit.webex.com/mit/j.php?MTID=mdf4fa0c03fdff386fddae06c1854fb4b US Toll Number: +1-617-324-0000 Access code:646 139 528 Ask Phila if you need the password 23:47:52 phila_ has joined #sdw 23:48:03 The_Room has joined #sdw 23:49:41 Still a few connection porblems... 23:49:58 agenda: https://www.w3.org/2015/spatial/wiki/F2F_Sapporo 23:51:28 ahaller2 has joined #sdw 23:55:12 chair: Ed and Kerry 23:55:45 present+ Ed, Kerry, jtandy, Linda, BartvanLeeuwen, ahaller2, phila 00:01:57 scribe: ahaller2 00:03:39 Kerry has joined #Sdw 00:03:43 phila_ has joined #sdw 00:04:10 Presentt+ kerry 00:04:43 Present+ kerry 00:04:55 jtandy In describing context of BP document "Best practice not best theory" 00:05:05 -> http://www.w3.org/2015/spatial/charter TNhe Charter 00:05:10 s/TNhe/The 00:06:53 jtandy - "spatial data still mostly in SDI silos" 00:07:37 yeonsoo has joined #sdw 00:07:55 ahaller2 has joined #sdw 00:08:07 eparsons: If we can provide the mechanisms, it will make it much easier for people to publish spatial data 00:08:20 present+ ahaller2 00:08:21 ... we all feel that there's more that cna be done to make it easier for publishers 00:08:31 s/cna/can 00:08:41 scribe: ahaller2 00:08:46 scribeNick: ahaller2 00:09:23 jtandy: assumption is that the Web is the data sharing platform 00:10:07 ... how can machine detect facts, especially if places are expressed in different levels of granularity 00:11:01 ... ABS, for example, is publishing data within spatial regions 00:11:33 ... challenge is, to combine data that may refer to the same place, or not 00:11:42 Europe uses NUTS codes to refer to regsions for statistical reasons. https://en.wikipedia.org/wiki/Nomenclature_of_Territorial_Units_for_Statistics 00:12:11 s/regsions/regions 00:12:31 ... identify tools and methods for publishing geospatial data 00:13:01 phila: geoJSON for example, is a language that is not standardised 00:13:14 yeonsoo_ has joined #sdw 00:13:16 ... Time Ontology is not a recommendation 00:14:08 jtandy: places change over time, and therefore the temporal aspect is important to be captured 00:15:09 eparsons: we only formalise a standard where necessary 00:15:23 present+ Chunming 00:15:41 ... benefit to point to best practises rather than inventing a long list of recommendation 00:17:12 phila: reminding that this group runs in collaboration with the OGC 00:17:37 jtandy: OGC is about 25 years old 00:17:55 ... based around a consensus process 00:18:11 ... working drafts in this group are published as drafts in OGC 00:19:02 -> http://www.w3.org/TR/sdw-ucr/ The WG's Use Cases doc 00:19:16 eparsons: is doing patent call 00:19:48 https://www.w3.org/2015/spatial/wiki/Patent_Call 00:19:56 rrsagent, this meeting spans midnight 00:20:13 phila: OGC requires to say at the beginning of every meeting to ask if there are patent claims 00:20:40 no objections from the group 00:21:54 Still connectivity issues for windows users - noted :-) 00:22:40 ahn has joined #sdw 00:23:14 ahn has left #sdw 00:23:53 Sangchul has joined #sdw 00:23:56 jtandy: is presenting the use cases document 00:24:50 present+ Sangchul, yeonsoo, Ahn 00:24:51 ... linking data is one of the key aspects we will be working on 00:25:18 ... second objective is semantics, just enough semantics 00:26:05 ... to describe, for example, other metadata in GeoJSON that is not geometries 00:26:12 The seven themes Liking data, Publishing Data, access via API's, Discovery, ID's, spatio-temporal , Sensors 00:27:23 ... another aspect is to describe places, for example, in the UK, if you say, we meet 'on the green' for tea and cakes on a sunday afternoon, we need to know what 'the green' is 00:28:12 ... enabling discovery is another important aspect of this WG 00:28:24 OCC standards require expertise in Geospatial 00:28:30 ... assignment of identifiers 00:29:29 ... for example, features, like a post box, or railway station, but in the geospatial world, the document is meant, whereas in the LOD there is a separate identifier for both 00:29:38 Things vs Features different approaches SDI and Web 00:29:51 ... expressing temporal and spatial information 00:30:13 ... we want to be able to give you a best practise to when to use what vocabulary 00:30:59 ... there is also the Time Ontology which needs updates, first published in 2006, but it can only to Gregorian calendar 00:31:32 ... we need another temporal reference system 00:32:00 ... there is no way of describing intervals as first class citizen 00:32:31 BartvanLeeuwen questions around vague descriptions of time 00:33:11 ... another important aspect in this group is to talk about sensors 00:33:21 ... there is the existing SSN ontology 00:33:37 ... there is also an observation and measurement ontology 00:34:23 ... we want to formalise how this metadata for sensors is best published 00:35:02 ... the last aspect is, dealing with large datasets 00:35:46 chunming_ has joined #sdw 00:37:07 -> http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html BP doc editors' draft 00:37:45 jtandy: we need to subscribe as a group to the 'Architecture of the Web' principles 00:38:13 ... best practises that do not fit with the AOW are not acceptable 00:38:28 http://www.w3.org/TR/webarch/ 00:39:08 eparsons: OGC may not subscribe to these AOW principles, but this group is on the forefront to potentially initiate this change 00:40:14 jtandy: OGC recognises that 'pointy APIs' as they call it is really useful on the Web, but some of their recommendations are too complex and don't work well implemented in APIs 00:40:19 yeonsoo has joined #sdw 00:40:59 edparsons: OGC is developing standards for the spatial community, but they recognise that other people on the Web use their geospatial standards 00:41:38 s/Web use/Web would use 00:42:17 bart: maybe we can say this the other way round too, maybe the Linked Data approach is not used by the Web community either 00:42:54 jtandy: we did agree in this group that the Linking of data in the geospatial domain is really important 00:43:55 eparsons: we love the 5 stars, but we don't need always to aim for that 00:44:26 sangchul: we use URIs to recognise physical objects 00:44:45 -> http://w3c.github.io/sdw/bp/ BP draft, now with Linda included as an editor 00:45:02 ... we develop www.insightar.org 00:45:15 present- Ahn 00:45:46 Kerry has joined #sdw 00:46:41 ... in an article that we published recently in a journal, we propose a different approach to identifying things other than URIs 00:47:27 eparsons: it is very valuable that we get input from the community to know what other approaches to recognise things are in the geospatial community 00:48:38 tahar: do you intend to extend SSN for other uses cases 00:48:49 kerry: yes, we intend to extend SSN 00:48:59 s/cases/cases? 00:49:16 jtandy has joined #sdw 00:49:28 Semantic sensor network ontology: http://www.w3.org/2005/Incubator/ssn/ssnx/ssn 00:49:53 phila_ has joined #sdw 00:50:10 kerry: there is for example, actuations that is not covered by SSN and which may not be enough driver in this group, but the WoT working group might provide us some input here 00:51:14 jtandy: currently there is a disjoint between how geospatial community formalise observations and measurements and how the semantics community is doing it 00:51:23 phila__ has joined #sdw 00:51:44 tahar: SSN does not have a big enough footprint yet 00:52:58 kerry: there are other things bubbling up that are related to SSN, for example, the sensor things api in the OGC 00:53:28 tahar: I have followed the academic community, but the developers are not yet picking up the SSN on the Web 00:54:33 ahaller2 Group will make SSN more modular ? More accessible 00:55:08 bart: most providers of sensor data want to keep their data close, as it is there unique selling proposition 00:55:23 ... they are not interested in publishing data freely 00:55:39 Kerry has joined #sdw 00:55:52 eparsons: the market will decide if a standardised approach will succeed 00:56:04 q+ to highlight http://www.w3.org/TR/generic-sensor/ 00:56:53 jtandy: one of the themes we need to focus on is to provide data through APIs 00:57:14 ack p 00:57:14 phila__, you wanted to highlight http://www.w3.org/TR/generic-sensor/ 00:57:20 eparsons: the OGC is challenged by defining what an API is 00:58:09 tahar: footprint SSN could have for sensors, we need SSN to be less data intensive 00:58:32 kerry: yes, that is one of the aims in this WG 00:59:06 jtandy: the ontological commitment to the dolce upper level ontology is known to be an issue for the uptake 00:59:08 RRSAgent, this meeting span midnight 00:59:08 I'm logging. I don't understand 'this meeting span midnight', phila. Try /msg RRSAgent help 00:59:14 RRSAgent, this meeting spans midnight 00:59:44 eparsons: we aim to do a spatial rosette to the spatial data 5 stars 01:00:27 jtandy: Another aim of this group is to align with the Data on the Web Best Practises WG 01:00:35 http://w3c.github.io/dwbp/bp.html 01:00:43 q+ 01:00:45 (data on the web best practices) 01:00:54 ack next 01:01:25 phila: the DOW WG has some very basic recommendations, such as 'you should provide metadata', but there are more techie ones later 01:01:38 s/DOW/DWBP 01:02:14 jtandy: since we are based on this work, we don't have to write down that we need metadata, because that is assumed by this DoW WG document 01:02:22 s/DOW/DWBP 01:02:57 jtandy: Hadley Beeman is the chair of the DWBP WG and she will be joining us 01:04:15 Kerry We should note where we interest with other groups eg. Data on the Web, WoT 01:04:26 kerry: we need to take notes today for things that we need to sync with these groups, i.e. DWBP and the AoW 01:04:49 linking data theme: https://www.w3.org/2015/spatial/wiki/Linking_Data 01:04:51 s/and the AoW/ 01:05:14 yeonsoo has joined #sdw 01:06:15 eparsons: we are not doing SSN in the next two days, focus on the BP document 01:06:54 jtandy: however, we need to hear from people how they intend to use the SSN ontology, because that will inform the BP document too 01:13:09 jtandy: planning the rest of the day and the distribution of the themes for the remainder of today and tomorrow 01:13:44 RRSAgent, draft minutes 01:13:44 I have made the request to generate http://www.w3.org/2015/10/25-sdw-minutes.html phila 01:14:02 RRSAgent, make logs public 01:14:07 RRSAgent, draft minutes 01:14:07 I have made the request to generate http://www.w3.org/2015/10/25-sdw-minutes.html phila 01:15:39 RRSAgent, draft minutes 01:15:39 I have made the request to generate http://www.w3.org/2015/10/25-sdw-minutes.html phila 01:21:21 phila_ has joined #sdw 01:48:51 eparsons has joined #sdw 01:51:39 ahaller2 has joined #sdw 01:54:39 Topic: Linking Data 01:55:35 ahaller2 has joined #sdw 01:57:42 jtandy has joined #sdw 01:59:18 present+ ahaller 01:59:24 present+ ahaller2 01:59:50 present+ Lars 01:59:57 scribe: phila 02:00:00 scribeNick: phila 02:00:21 Kerry has joined #sdw 02:00:23 eparsons: Before we start writing, we thought we'd talk a bit about GitHub 02:00:33 yeonsoo has joined #sdw 02:01:00 jtandy: Shows the GH repo http://github.com/w3c/sdw/ 02:02:07 ... talks about Pull Requests 02:02:45 ... Request is that everyone contributes, but that only editors merge Pull Requests 02:03:03 Jeremy Demonstrates GH process 02:05:36 -> http://www.w3.org/respec/ ReSpec 02:07:01 jtandy: Shows importance of making a summary comment when creating a PR 02:07:57 Please don't make changes directly in gh-pages 02:11:47 jtandy: Asks that you push to a branch and then create a pull request for the editors to merge your changes into the GH-Pages branch 02:12:51 LarsG has joined #sdw 02:14:09 jtandy: Recommends using rebase cf. merge afetr fetching 02:15:05 present+ Darko 02:15:08 s/afetr/after/ 02:15:13 present+ Andrei 02:15:46 timbl has joined #sdw 02:15:46 present+ Sebastian (Siemens) 02:15:47 deiu has joined #sdw 02:15:52 present+ timbl 02:15:57 present+ deiu 02:16:17 Darko_Anicic has joined #sdw 02:16:39 present- deiu 02:17:02 eparsons: Is keen to get on 02:18:19 eparsons: Asks jtandy to either create a wiki page about how the editors want to use Git or send a message to the list 02:18:58 https://www.w3.org/2015/spatial/wiki/How_to_work_with_GitHub 02:20:52 Recording the fact that Jeremy completed his action to put info on the wiki before the scibe had a chance to put it in trackbot 02:21:01 s/scibe/scribe/ 02:21:30 eparsons: Now we areally are going to talk about linking 02:23:14 -> https://www.w3.org/2015/spatial/wiki/Linking_Data Linking Data wiki page 02:23:32 jtandy: Goes through the summary list 02:24:28 jtandy: I think that linking between things at the dataset level is largely covered by DWBP. Its' about links between items within datasets, crawlable etc. 02:24:52 eparsons: It's important to socialise this. As LD, Geo and Web community not all on the same page 02:25:24 eparsons: The thing/the representation... we think in terms of the world in terms of points, lines and areas and we're happy to give those things IDs 02:25:50 ... but that's not always what we're talking about, esp if features don't have a geometry 'the Mid West', the east end of London etc/ 02:25:58 ... or there may be many geometries 02:26:14 Linda: But the whole Thing/feature discussion goes here or in the identification theme? 02:26:33 jtandy: I think it goes in the ID theme but we still need to talk about linking 02:26:57 ... SDIs don't talk about the real thing, just the description which is an information record 02:27:07 ... whereas in the LD world, we want to identify the real world thing 02:27:36 ... We have agreed that the LD approach is what we want to follow, which doesn't necessarily mean RDF but that's probably the easiest way 02:28:14 ... Need to think about attributes. Lighthouses have things like a height, spatial coordinates etc. 02:28:41 eparsons: I think we just need to write a narrative around the different world views 02:29:43 jtandy: We see another feature that talks about the same thing. May see the lighthouse as a navigational aid 02:30:09 jtandy: You can merge the different features that talk about the same thing (or not merge) 02:30:46 ... Imagine a dataset of lighthouses in UK, we'd give the dataset an id, and then inside the dataset there woujld be local identifiers 02:30:54 Not merge is important 02:31:41 jtandy: Local names are not typically URIs. We know we want to use URIs as identifiers. So we might take the dataset URI - which identifies a silo 02:31:48 DArko_Anicic has joined #sdw 02:32:36 ... think of a different dataset, this one about shiprecks near lighthouses. But problem is mapping the local IDs, we want to be able to express the linkages within the dataset 02:33:07 eparsons: That introducesthe more fundamental issue - we need the granularity to be able to link to an individual lighthouse 02:33:50 s/introducesthe/introduces the 02:35:51 timbl: So the aim is to produce a shim layer to enable things in the dataset to be exposed as LD? 02:36:02 jtandy: I see that as being important, yes. 02:37:31 eparsons: A shim might be the solution, but we want to encourage/enable people who are using W*S services to create that set of URIs 02:37:47 ... these are things you can add to your data to make it more linkable 02:38:03 eparsons: We don't want to put any overhead on publishers that we don't need to. 02:38:39 Kerry: I'd expect to go a little further in the ID section and talk about using URIs within the dataset 02:39:53 jtandy: Talks about use of authoritative sets of URIs, if you can find them 02:40:08 ... and a third party might create a saemAs set 02:40:25 s/saemas/sameAs 02:40:39 LarsG: It's out of scope to discuss who has the authority to create those URIs 02:40:46 Unanimous: yes 02:41:25 timbl: Work will be done by people motivated to do it. 02:41:46 ... And the BPs should encourage/facilitate that 02:42:40 eparsons: It might be helpful for us to help to identify those authoritative sets 02:42:43 q+ 02:43:25 eparsons: We could offer examples where it is appropriate to mint authoritative URIs 02:43:36 ack next 02:43:59 BartvanLeeuwen: I wonder if we want to go one step further and talk about features and making the properties more LD-like 02:44:11 ... How do I know what height means on a feature? 02:44:55 jtandy: We need to enxure that when people are publishing data that they have explicit semantics 02:45:02 s/enxure/ensure 02:45:14 q+ 02:45:39 jtandy: In the LD world, the predicate has a URI that you can look up. In the SDI world, it will be published as GML and that will say that it's written according to a XSD over there - and you don't always find that 02:45:43 q- 02:46:03 Sebastian_Kaebisch has joined #sdw 02:46:04 BartvanLeeuwen: We have a case in emergency response when working cross broder 02:47:05 jtandy: Talks about ht and ho as possible EN and DE abbreviations for height which would cause problems 02:47:29 kerry: we are committed to making our vocabs multilingual as far as we can 02:48:07 eparsons: Gives example of heights above sea level and floors in a building - different ways of describing the same thing 02:50:44 BartvanLeeuwen: German and Dutch notions of ambulance are different since German ones have two types of crew depending on the expected severity of the incident 02:50:51 ... no equivalent in NL 02:51:24 jtandy: Anyone could crerate a taxonomy of ambulances and it's up to the community to decide which one to use 02:51:25 q+ 02:51:36 ack next 02:52:02 BartvanLeeuwen: if you're going to publish this data then people should be able to look up what it means 02:52:54 ack next 02:53:15 LarsG: I'm less concerned with false negatives. But false positives think that two things are the same - e.g. creator of the feature or the real thing 02:53:20 yeonsoo has joined #sdw 02:53:29 jtandy: I recognise the problem you're identifying 02:53:52 ack me 02:55:17 phil: people called the same thing different names. PROV has some good solutions for that. For example, for the lighthouse example, Navigator calls the lighthouse something, geographer another name. PROV can be used for that. 02:55:29 s/phil/phila 02:56:02 jtandy: Because the GIS community has this issue of descriptions and real world things, we could refer to the Data in URLs work that JeniT did 02:56:26 -> http://www.w3.org/TR/urls-in-data/ Data in URLs 02:56:46 jtandy: The lighthouse is the thing. Landing page would be the record 02:57:01 eparsons: The landing page is something I can crawl, a record in a database might not be that 02:57:23 jtandy: This is an FPWD, it says that a landing page is similar to a record. 02:57:37 ... it makes some proposals around properties and shorthand properties 02:58:07 timbl: From experience of playing with VCard... A card is a social entity, either person or organisation 02:58:14 ... you get this data that says this is a person 02:58:54 ... it represents a business card and you can get hooked up on this. It turns out that talking about the card isn't usually useful 02:59:17 ... in fact just treat it as being about the person 02:59:54 ... Life's too short to get too hung up. Punning can be good. 03:00:02 q+ 03:00:35 ack next 03:01:10 jtandy: I saw something about this in some work from CSIRO. What was accessible on the WEB via WFS, implied that certain things existed and then used those IDs about the real world as the basis for reconcilliation. 03:01:32 ahaller2: In DCAT there is a distinction between a landing page and a document 03:02:08 jtandy: I just put the data in URLs work up as an example of where someone has done similar work 03:02:18 q? 03:02:58 ahaller2: DCAT has different URIs for dataset and landing page, CKAN does it differently 03:04:28 jtandy: We don't want to go down the rat hole 03:05:04 eparsons: In the BP doc, we'll need to recognise the problem and try and give some guidance without necessarily definitively solving it 03:05:39 jtandy: We could perhaps point to the CSIRO work as an example of how to pull out/infer IDs for real world objects 03:06:15 Linda: We added some data to some existing data about trees without getting too hung up on the details 03:06:37 Linda: So we're saying that features are info records and for practical purposes you can treat it as the thing. 03:06:46 Kerry: That's too strong 03:06:58 timbl: I was saying you shoujldn't get too philosophical about it. 03:07:13 timbl: The URI is generally for the thing and you're probably not so interested in the document 03:08:22 jtandy: If I have an ID in the dataset for 'Eddystone' then maybe I can infer an identifier within a dataset of Lighthouses that 'Eddystone' is something like lighthouses.com/Eddystone and that's the real thing 03:08:39 Linda: So how do you know how to reconcile across datasets? 03:09:00 Kerry has joined #sdw 03:09:06 jtandy: offers '303' and 'Eddystone' as internal IDs in diff datasets for the same thing 03:09:15 yeonsoo has joined #sdw 03:09:40 Linda: And if you know that they're the same, how do you make that assertion? 03:09:56 jtandy: You need sometehing like a sameAs statement 03:10:37 Linda: We have 2 datasets in NL about buildings, really a 1-1 set. One dataset has all the IDs of the other dataset in them. 03:11:02 jtandy: If you choose to subscribe to the assertions that that two things are the same. 03:12:02 eparsons: The key thing we need to do is to provide advice to publishers on how to make the data more accessible, more usefeul 03:12:39 ... we just need to come up with simple guidance. It's about URIs for your things, but I don't think we should worry too much about the mapping from one person's data to another. 03:12:47 jtandy: reconciling is a hard job. 03:12:54 eparsons: It's a really hard job. 03:14:45 jtandy: There will be a debate about what people mostly want to ask questions about. 03:15:04 ... Channelling Bill Roberts, people want to ask questions about real stuff, not the records about them. 03:15:36 eparsons: You can clearly version things as tech improves and techniques improve. 03:15:53 q? 03:16:37 jtandy: Hydrologists define catchments. Historically, catchment has been defined as the basis of an elevation model which got updated and, in the process (computer-wise) created a new piece of the world. 03:17:05 ... I think we're agreeing that the entity that people are most interested in learnign bout is the real world thing. 03:18:12 Kerry: Catchments don't have a real world existence. It's an abstract idea and they change anyway... 03:19:13 LarsG: A real world object is a real world object in the domain of discourse. So if catchments are in the domain of discourse, they are real 03:19:33 s/learnign/learning/ 03:19:41 Linda: So can we use the hydrology example as an example of a bad example? 03:19:51 jtandy: I don't think we can... 03:20:09 Linda: No the way they did it with the historial aspect 03:20:21 Darko_Anicic has joined #sdw 03:20:27 eparsons: Ah yes, but maybe without calling it a bad practice, mor an exmaple of someeting to avoid. 03:20:40 jtandy: So we have 2 examples of BP we could apply 03:21:09 ... One on UK consistuency boundaries and the otehr is the Australian catchment data 03:21:14 q? 03:21:46 jtandy: In CSV we have the crime data which was difficult as the boundaries of crime areas changed from one year to the next. 03:21:55 eparsons: You need to say 'you need to hink about this' 03:22:02 s/hink/think/ 03:22:12 RRSAgent, draft minutes 03:22:12 I have made the request to generate http://www.w3.org/2015/10/25-sdw-minutes.html phila 03:22:47 jtandy: Point 3 on Linking data is Spatial datasets are different in that they will (usually) have an "extra level of structure and granularity that is reflected in the data" e.g. the use of geometry and spatial relationships 03:23:01 ... Is there something special about Geo that doesn't apply to non-geo data 03:23:29 eparsons: I thought this was about recognising that geo data can be heirarchical - a village is part of a county is part of a country 03:24:00 ... there's a heirarchical relationship that isn't geospatial 03:24:30 jtandy: There's a geographical, topological anad social heirarchy. Does that make our data special or is it all DWBP? 03:24:55 eparsons: I don't want to fall down the trap of always using the topological relationships 03:25:09 jtandy: Places without boundaries, or with indistinct boundaries 03:25:25 ... are a problem. We have social boundaries, like 'London' 03:25:56 ... I might want to say that my working place is 'in London' when it is legally somewhere else. 03:26:14 Kerry: I think that's more of an identifier question. 03:26:36 eparsons: I want to be able to link something I can draw a boundary around to something I can't (or vice versa) 03:27:23 ahaller2: Questions the specialness of spatial data 03:27:53 Kerry: I think we do need to define the relationships. 03:27:55 q+ 03:28:10 ack next 03:30:26 phila: talking about charter: relationships that are very well known in this community are not registered in the ? registry. Best practises document is only a note and not in the registry. But we are allowed as a group to develop further recommendations that we can put in the registry. 03:31:15 ... link relationships are important and we may need to define a new recommendation, but it may be enough to have it in the Best practise document 03:31:41 s/?/IANA registry 03:31:55 s/registry registry/registry 03:34:15 q? 03:35:50 -> http://www.iana.org/assignments/link-relations/link-relations.xhtml IANA Link relations 03:36:45 jtandy: We have had agreement in our discussions around point 5 - Links are first-class citizens - it is 'connectedness' that makes for "Data on the Web"; allowing one to discover new information by traversing those links 03:37:03 eparsons: And I think that's where the biggest change will come in the GIS world 03:37:57 jtandy: We want data to be traversible via links 03:38:19 ... We want our datasets to infer a bunch of hyperlinks that can be link to other people's stuff. 03:38:36 Linda: So it's useful to have hyperlinks to things like Goenames, wikipedia etc. 03:38:41 jtandy: It's not our job to curate those 03:38:55 eparsons: No, but it's our job to give examples of what you can link to 03:39:10 eparsons: In Open Street Map, every item has an ID that can be accessed via a URI 03:39:29 ... That's not true with WFS and I think OGC needs to move in that direction 03:42:10 jtandy: We need to find a way to make it convenient to publish summaries of those linkages so that they can be discovered at the dataset level 03:42:58 ... You can publish things that refer people to a service that does stuff to the data 03:42:59 q+ 03:43:04 q+ to talk about HAL 03:43:09 ack next 03:43:09 q+ to talk about HAL https://tools.ietf.org/html/draft-kelly-json-hal-07 03:43:10 phila, you wanted to talk about HAL 03:43:30 ack me 03:43:30 phila, you wanted to talk about HAL https://tools.ietf.org/html/draft-kelly-json-hal-07 03:44:02 phila: talks about HAL, IETF draft, it is not RDF, but Linked Data 03:44:36 -> https://tools.ietf.org/html/draft-kelly-json-hal-07 JSON Hypertext Application Language 03:49:18 jtandy: Point 4 - Representations may be provided with varying degrees of authority and currency, for differing scales and purposes 03:49:38 ... There should be info about who published the data so otehrs can decide how authoritative it is. 03:50:05 s/otehrs/others/ 03:52:00 eparsons: Talks about the many maps of Jersualem - none of them the same 03:52:13 ... so you need to know who produced each one so you can choose the one you want to use. 03:53:12 eparsons: It's a common misunderstanding that maps are accurate and they agree. 03:53:21 timbl has joined #sdw 03:54:26 === LUNCH === 03:54:36 RRSAgent, draft minutes 03:54:36 I have made the request to generate http://www.w3.org/2015/10/25-sdw-minutes.html phila 04:25:44 yeonsoo has joined #sdw 04:42:48 yeonsoo has joined #sdw 04:44:10 hadleybeeman has joined #sdw 04:52:43 ahaller2 has joined #sdw 04:54:56 eparsons has joined #sdw 04:58:49 BartvanLeeuwen has joined #sdw 05:00:26 jtandy has joined #sdw 05:01:56 LarsG has joined #sdw 05:05:27 hadleybeeman, 202 05:06:50 ahaller2 has joined #sdw 05:07:45 === LUNCH END === 05:08:15 present+ BartvanLeeuwen 05:08:48 present+ ahaller2 05:08:52 kerry Web of things / SDW ad-hoc will take place on wednesday 05:09:02 Details TBA 05:11:20 eparsons: We want to recap the main points from this morning whuile it's fresh in our minds 05:11:26 Sangchul has joined #sdw 05:11:33