Spatial Data on the Web Working Group Teleconference

<trackbot> Date: 01 April 2015

<phila> This will be the SSN, Time and Coverages meeting. Head over to https://plus.google.com/events/ce2gg0fbtug4q7urls3u211gj1c for the BO meeting with Ed

<kerry> volunteer scribe?

<kerry> scribe: andreas

<scribe> scribe: aharth

<kerry> scribenick aharth

<scribe> scribeNick: aharth

kerry: we have two parallel meetings
... patent call

<kerry> https://www.w3.org/2015/spatial/wiki/Patent_Call

New members to introduce themselves

kerry: no new members

Continuing Use Cases

<kerry> https://docs.google.com/spreadsheets/d/1PSnpJYQDgsdgZgPJEfUU0EhVfgFFYGc1WL4xUX9Dunk/edit#gid=0

kerry: ssn, time and coverage are the topics for our meeting
... hierarchical geographical regions is the current use case
... use case 34

<kerry> https://www.w3.org/2015/spatial/wiki/Working_Use_Cases#Spatial_Sampling_.28Best_Practice.2C_SSN.29

kerry: we will go through the use cases and nominate requirements for the three deliverables
... focus is on new requirements
... nomination of requirement for ssn, coverage or time?

SimonCox: primarily seeing things related to best practices document

kerry: we could add a requirement around spatial and temporal representation

SimonCox: unclear whether it will add a requirement on time or coverage per se, but relation between time and spatial

Alejandro_Llaves: agree with simon
... propose to remove the coverage label from use case, not the coverage as we understand it

kerry: our coverage includes time series data, but i agree, it's changing geometry over time
... satellite data processing
... ssn and coverage are the proposed categories

Alejandro_Llaves: added several requirements to the spreadsheet already

ahaller2: positioning of satellite; satellite is sensor, is geo lat/long enough?

kerry: descriptive satellite positioning is a challenge

Alejandro_Llaves: new requirement, or in the ones we already have? maybe metadata on positioning method?

kerry: can we add to the requirement "and satellite position", rather than an new one?

Alejandro_Llaves: there's a mark at profiling the ssn ontology

kerry: profiling is a notion that arises from an xml description, similar to an extension in ontologies

SimonCox: profiling would refer to a set of validation constraints
... minimum information, checking compliance (column AC)

Alejandro_Llaves: what to add to description?

ahaller2: qualitative measurement, observation by humans
... do we have human observations as a requirement?

Alejandro_Llaves: column M (detecting qualitative events)

kerry: we have citizens as senors, but not scientists
... column R

Alejandro_Llaves: we could say citizens as sensors implies qualitative measurements

kerry: qualitative measurements could also come from an algorithm
... citizen sensor requirement was people observations vs. machines

Alejandro_Llaves: new requirement then?

kerry: put column R (and maybe add ... and scientists)

<SimonCox> Which uc are we lookingat?

Alejandro_Llaves: "soil moisture is only subjectively measured": unclear whether it adds qualitative measurements

ahaller2: people looking at images

kerry: people looking at the soil
... is also qualitative

ahaller2: people making the measurement, does it make a difference whether based on soil directly, or via images?

Alejandro_Llaves: they refer to other sources

ahaller2: they could say that they use other sources for unkown values... no matter what, it's still a requirement

kerry: agreed, i think we've caught it

Alejandro_Llaves: suggest for each use case we distinguish between deliverables (ssn, coverage...)
... in terms of requirements

kerry: next up marine observations

SimonCox: i have transcribed the use case from material provided to me (user stories)
... some ssn use, use of mobile instruments mounted on marine animals (mobile and spatial sampling features)
... column Z?
... also spatial sampling features, column F?
... number of use cases come from communities with core notions of spatial sampling
... marine, ALI...

kerry: is profile here the same as in previous use case?

SimonCox: these profiles are curves

kerry: geometries on which samples are taken

SimonCox: ssn didn't have anything on sampling, area chosen not to go

kerry: relevant geometries probably covered by Z and F
... any comment on ssn aspect?
... now coverage, marine observations
... any comments? happy with entries in spreadsheet so far

<ebremer> yes

kerry: next use case, marine observations data providers
... 3d location is suggested
... geo location also... anything else there?

SimonCox: do we have qualitative observations?
... species identification, entry in M?

kerry: M was about events
... species recognition done by person, looking at the images
... could be something new, original use case was about observing traffic jams, crowds...
... is species identification similar?

ahaller2: maybe separation is wether observation is automatic vs. manual (algorithm vs. person)

kerry: how is that related to citizen sensor?
... both under citizen sensing and also qualitative events

ahaller2: user story 2, last sentence
... can we capture: we had a value before but no value now

kerry: looks more like a visualisation thing
... do we need to cover absent values (null value measurements)?

ahaller2: we have uncertainty measurements, which could cover "no"

kerry: depends how it is coded up

ahaller2: we could include column AA for that

kerry: ok, let's do that, column AA
... which includes the null measurement, or null result

Alejandro_Llaves: simon, did you see comments 36 and 38?

<ChrisLit> Zakim aacc is me

Alejandro_Llaves: use case description includes parts for best practice use case

SimonCox: requirements have interaction with scope of best practice
... there's an encapsulation issue in general, what's the part of ssn vs. other practices or standards
... maybe first classification, then selection and cull

kerry: marine observations data consumers
... all about best practices?

SimonCox: fine

kerry: last one for today was use case 38
... plan is to go back to single track meeting next week

<phila> TPAC Venue 2015

kerry: request that use case presenters go through the spreadsheet and note where columns that should have been noted
... will put that in an email
... any questions or comments?

<SimonCox> What is 'TPAC'?

kerry: given the previous meeting with OGC, next meeting will be with TPAC in japan

W3C Technical Plenary / Advisory Committee Meetings

<ChrisLit> W3C equivalent of OGC TC

kerry: thanks, meeting closed

<LarsG> Bye, thank you

<Alejandro_Llaves> thanks, bye!

<ebremer> bye

<ChrisLit> Bye

<ahaller2> bye

<phila> trackbot, end meeting