13:14:54 RRSAgent has joined #sdw 13:14:54 logging to https://www.w3.org/2021/06/24-sdw-irc 13:15:07 meeting: SDWIG monthly meeting 13:15:22 rrsagent, set logs world-visible 13:15:35 scribe brinkwoman 13:15:57 trackbot, status 13:16:15 ...workshop report: https://www.w3.org/2020/maps/report 13:17:20 ...accessibility requirements were a strong theme. Every feature needs to have an accessible name 13:17:29 ...so adding a featurecaption element 13:17:47 ogc-gobe has joined #sdw 13:17:47 rrsagent, draft minutes 13:17:47 I have made the request to generate https://www.w3.org/2021/06/24-sdw-minutes.html roba 13:18:03 ... implemented in polyfill and in server component 13:19:14 ...[demonstrates accessible popups on map] 13:21:26 ...feature caption makes it efficient to tab through features. Not perfected yet, still work to do. 13:23:12 ...Doug Shephert mapped MapML to requirements for maps on the web identified earlier. [shows matrix] 13:24:05 ...Looking for an editor to help continue this process 13:24:47 ...A student worked on custom projections. One of the comments of this group was that MapML was limited as to projections. 13:25:56 ...[demonstrates] 13:26:48 ...of interest is linking within maps 13:27:55 ...[demonstrates] not only within maps, but also linking out to external (map) sources 13:28:55 ...creating a web of feature information 13:31:34 ...zoom levels described in header of resource 13:31:53 ...and go to another resource for additional zoom levels as needed 13:32:32 ...shareable primitive APIs: providing interface to developers. We have a prototype for that. 13:32:49 ...zoom and pan buttons, layer controls, etc 13:34:03 ...Why I invited Gobe Hobana: a key thing is that you need parameters like origin, resolutions, bounds, tilesize for web mapping 13:35:13 ...need this to be retrievable somewhere. 13:35:51 jtandy_: so you want to understand how you can group up these things to get the atomic unit of info needed to generate a map. 13:36:09 PeterR: yes, and we need to have standard definitions for this 13:37:21 Gobe: we already have such descriptions for scale sets, I shared the links in the [Teams] chat. 13:37:58 ...these are already registered. New well-known scale sets can be added. 13:38:11 Descriptions of example WKSS in the 2D TMS standard http://docs.opengeospatial.org/is/17-083r2/17-083r2.html#56 13:38:33 ... only issue is OGC API Tiles SWG is considering if this concept needs to be included in the next revision of the standard. Because they can be derived from TMS. 13:38:41 Cross-posting Gobe's chat: 13:38:42 ... currently asking for comments on this issue 13:38:44 Descriptions of example WKSS in the 2D TMS standard http://docs.opengeospatial.org/is/17-083r2/17-083r2.html#56 Registrations in the OGC Definitions Server http://www.opengis.net/def/wkss/OGC Definitions of common Tile Matrix Sets, as specified in the 2D TMS Standard http://docs.opengeospatial.org/is/17-083r2/17-083r2.html#61 13:39:44 PeterR: I would go in the other direction. These parameters are important for interoperability, similar to an EPSG code. 13:41:00 Chris: EPSG code components can be parameterized 13:41:01 Registrations of TMS in the OGC Definitions Server http://www.opengis.net/def/tms 13:41:30 ...and there are other authoritative bodies 13:42:08 jtandy_: great conversation. We have more on the agenda unfortunately. 13:42:23 ...further discussion in a github issue 13:42:28 PeterR: happy to have more conversation 13:42:48 NB on defs-dev (development) we have implemented access to technical resources too.. http://defs-dev.opengis.net/def/tilematrixset/OGC/1.0/WorldMercatorWGS84Quad?_profile=alt 13:42:50 Topic: WebVMT 13:43:41 - so perhaps we need to separate concerns - identifiers vs parameterised information vs description publication 13:44:16 RobSmith: my most notable news: I have managed to change HTML 13:44:57 ... undefined endtime ended up in HTML spec, in collab with WebVTT, and wrote web platform tests 13:45:12 ... second thing is I finally published the Android app 13:45:14 Scale set issue: https://github.com/w3c/sdw/issues/1237 13:45:39 ... basically tracks where you are with video in sync on a smartphone, and it's free 13:47:03 ...Next thing is I got involved with GeoPose group in OGC, creating a standard for 'where are you and where are you looking' 13:47:07 Thanks @PeterR. I will take an action to the bring the issue (SDWIG#1237) up in the next OGC API - Tiles SWG meeting. 13:47:19 ...first draft already available, working on user guide and reviewers guide 13:48:05 ...considering putting some new features into the android app related to geopose / recording camera orientation 13:49:11 ...danger of overloading the text format 13:50:01 ...ties in with OGC testbed 17 moving features: trying to extract location of moving features observed in the video 13:51:09 ...trying to extract use cases: traffic, attempting to track school buses for example, from a gopro by the road, or from a drone. 13:51:50 ...currently trying to get British roadside footage to get metrics on traffic flow, in anonymous way, maintaining privacy. 13:53:26 ...second use case is river discharge. Using footage, measuring flow rate of water. Could be from drone, airplane, satellite 13:54:46 ...finally there's autonomous vehicles, with cameras, LiDAR, trying to work out where the footage the vehicle is showing, is being taken. 13:55:01 jtandy_: do you need our help with something? 13:55:47 RobSmith: yes, looking to get in touch with Perspective imagery, or Oblique Imagery DWG. 13:56:01 ogc-gobe: I can get you in touch with the chairs 13:56:18 Christine Perey: could you include me, also need to get in touch with them. 13:56:57 ogc-gobe: will send you their email addresses and also those of some active members. 13:57:14 jtandy_: well done getting HTML changed 13:57:45 ...Linda and I will put out a call for some work items we identified. 13:58:19 ...Simon sent some slides about OWL Time update, can skip this item and distribute the slides 13:58:40 Chris: Three things were changed. IANA links and two small changes. 13:59:19 Topic: Responsible Use note 13:59:37 RobSmith: Emily asked me to give the update 14:00:02 ...there was a workshop on the 25th of May, inviting a larger audience to give feedback 14:00:13 ...65 participents, very interactive meeting 14:00:32 ...actors: user, developer, regulator, and other 14:01:03 ...other is a significant group, because that's all of use - you are involved because data is created about you 14:02:33 ...strava use case: cyclist who attacked black lives protestor, police tracked the wrong person based on data. Discussed this use case from the 4 perspectives 14:02:51 jtandy_: as a result of that workshop, is new info going into the ethics doc? 14:03:28 RobSmith: yes, hoping to make an update to capture the feedback. Also looking to promote to a wider audience. It is not covering Asia, Africa, South-America yet 14:04:02 jtandy_: thank you very much. Apology to the speakers for small audience. Will make sure this gets attention of the group 14:05:09 ... the new charter is about to go to review in the relevant W3C body and we should have a new Team contact soon 14:06:10 roba: Been having some discussion with O&M group related to SOSA/SSN. Better guidance on observable property description is needed. Will get back about that 14:06:52 jtandy_: thank you all 14:07:17 rrsagent, create minutes 14:07:17 I have made the request to generate https://www.w3.org/2021/06/24-sdw-minutes.html brinkwoman 15:24:31 Zakim has left #sdw