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