SSN XG -- 08 Sep 2010

<laurent_lefort_cs> Previous: 2010-08-31 http://www.w3.org/2010/08/31-ssn-minutes.html

<laurent_lefort_cs> Scribenick: Kerry

Progress on "Module by Module" documentation (and examples)

<laurent_lefort_cs> http://www.w3.org/2005/Incubator/ssn/wiki/Report_Work_on_the_SSN_ontology

<laurent_lefort_cs> Page with the table with the links to all the sub-page for each module

<laurent_lefort_cs> SSN Sensor http://www.w3.org/2005/Incubator/ssn/wiki/SSN_Sensor

Andriy: informal overview+ some questions about measurement capabilities (wrt the ontology itself)

Laurent: o'view is right detail level

<michael> +q

Laurent: there was a figure from Raul - -could that go in too?

Michael: can change CMAP labels to be more precise; also importing is tricky

Laurent: has a script to remove the labels and another to extract subclasses and then some work by hand. Happy to go through this again

<Payam> I'd prefer RDF-style

<michael> prefer rdf

<laurent_lefort_cs> Kerry: like the are and is

<michael> I'd prefer is-a to are, though

<Payam> subClass?

Kerry: prefers the cmap style

<laurent_lefort_cs> Vote: Who is in favour of CMAP out of the box?

<michael> -1

<Payam> -1

<cory> -1

<Andriy> -1

<Arthur> -1

<laurent_lefort_cs> Abstain

Decision: apply the scipt to relabel

<Payam> +q

Laurent: "sub class of" for "are"?

<michael> subclass and 'member of' or 'instance of' ??

<laurent_lefort_cs> Vote: sub class of and instance of

<laurent_lefort_cs> +1

<michael> +1

<Andriy> +1

<Arthur> +1

<cory> +1

<Payam> none- I'd vote for standard RDFS types :)

<cory> subclass is one word

afree with cory

<Payam> -q

<michael> +1 for subclass

<Arthur> why not use subClassOf

also -- the camel case does not seem to be used for keywords

<laurent_lefort_cs> Vote: subclass instance equivalent

<laurent_lefort_cs> +1

<Arthur> +1

<Andriy> +1

<cory> +1

<michael> +1

<michael> +q

<Arthur> Laurent, I saw you also uploaded pictures of the knife examples, but those are not linked here yet.

Decision: subclass instance equivalent for CMAP figures

<michael> The diagrams have to change anyway, as they have thing inheriting from Thing, which isn't right for the DUL alignment.

<laurent_lefort_cs> ACTION: Laurent to regenerate the figures with the version aligned to DUL [recorded in http://www.w3.org/2010/09/08-ssn-minutes.html#action01]

<trackbot> Created ACTION-50 - Regenerate the figures with the version aligned to DUL [on Laurent Lefort - due 2010-09-15].

Laurent: Do we combine Raul's picture and your page? Or keep Raul introductory and use CMAP for yours?

Andriy: better to use CMAP consistently

Payam: prefer Rauls' for intro section and CMAP for detail

<Payam> +q

Laurent: other comments on this approach?

<michael> +q

Payam: sugeest Raul's for the whole ontology and CMAP for the parts

<Payam> +q

Michael: agree Payam. Raul's provides a nice map to the modules and their relationships

Payam: if CMAP need to use rdf labelling style

yes -- a simple explanation would do!

<michael> plus a link near each figure to the notation key

laurent: a table to explain keyword/labels?

<laurent_lefort_cs> ACTION: Laurent to provide picture and notation guide [recorded in http://www.w3.org/2010/09/08-ssn-minutes.html#action02]

<trackbot> Created ACTION-51 - Provide picture and notation guide [on Laurent Lefort - due 2010-09-15].

<Payam> +q

Payam: each figure should be self-contained in this respect

Payam, Laurent: ie a legend in each figure

<Payam> something like this: http://www.w3.org/Submission/OWL-S/Profile-Ontology-1.1ai.gif

<Payam> perhaps not a very good example

Laurent: agrees

Andriy: question on measurement capability module
... what is the right way to design property names and also <something else>

Michael: recall decision to change -- perhaps not done yet. Will do.

<scribe> ACTION: michael to make those changes to measurement capability module. consult eith Andriy [recorded in http://www.w3.org/2010/09/08-ssn-minutes.html#action03]

<trackbot> Created ACTION-52 - Make those changes to measurement capability module. consult with Andriy [on Michael Compton - due 2010-09-15].

Andriy: modelling a sensor's measurement capabilities <broke up...>

Laurent: use example in text the way you do -- this looks good
... use an example in its entirety -- a compromise to offer complete description in another page?
... one page per example, small text, plus then point to another page with complete figure?

<Payam> +q

<Payam> -q

Payam: looks good. for deployment section should I uses Andriy's or something else?

Laurent: your own example (a different one) would be good.

<scribe> ACTION: kerry to do example for observation module [recorded in http://www.w3.org/2010/09/08-ssn-minutes.html#action04]

<trackbot> Created ACTION-53 - Do example for observation module [on Kerry Taylor - due 2010-09-15].

Laurent: DUL documentation?

<scribe> ACTION: laurent to suggest Kryz does doc for DUL alignment [recorded in http://www.w3.org/2010/09/08-ssn-minutes.html#action05]

<trackbot> Created ACTION-54 - Suggest Krzysztof does doc for DUL alignment [on Laurent Lefort - due 2010-09-15].

Michael: will do subediting here.

XG Wrap up

<laurent_lefort_cs> http://www.w3.org/2005/Incubator/ssn/wiki/Incubator_Report

Laurent has reorgansied report following suggestions from Arthur. Are people ok with it now?

Laurent: looking for help with "recommendations" section

<Payam> +q

<michael> agree with kerry

All: various comments on report structure
... <summary> structure is good. some concern about too much... secs 4-7 are what matters.

<laurent_lefort_cs> ACTION: Laurent to update plannned content for section 2, 3 and 7 on basis of available material [recorded in http://www.w3.org/2010/09/08-ssn-minutes.html#action06]

<trackbot> Created ACTION-55 - Update plannned content for section 2, 3 and 7 on basis of available material [on Laurent Lefort - due 2010-09-15].

Laurent: question about importance of GeoRSS

Cory: don't really want to do everything

<Payam> +q

Cory: suggest just mention GeoRSS in recommendations but no worked example

Payam: structure is good. Do we need to do <something> for observations?

Cory: we have SOS examples which covers O&M

Payam: description how the ontology relates to O&M? mapping or annotation to O&M or both

<laurent_lefort_cs> +q

Michael: DUL alignment and O&M and our ontology are pretty well aligned

<michael> +q

<laurent_lefort_cs> Figure on the modules developed in priority

<laurent_lefort_cs> http://www.w3.org/2005/Incubator/ssn/wiki/File:UseCasesAndOntologyModules.png

Michael: aligns quite well and documents in ontology comments for sources of definitions

apologies: I've lost the connection (child interference) and can't get back in at this late time.

which means my notes are a bit empty.

<Payam> this figure is very helpful; a paragraph to explain this will help

<laurent_lefort_cs> Laurent: commenting the picture

<Payam> I'll scribe

<laurent_lefort_cs> The modules at the center are the most important

<Payam> +q

<laurent_lefort_cs> The modules at the periphery and the fact that our ontology is interfaced to them is important too

<Payam> Use case 4: covers some aspects which are not in the main scope of XG

<Payam> Do you have any content to contribute to section 7?

<Payam> Laurent: Do you have any content to contribute to section 7?

<Payam> same here

<laurent_lefort_cs> Sorry

could be cut off due to time -- we don't normally overrun this much

<laurent_lefort_cs> Let's close the conf

<cory> sure

<michael> ok, bye

bye!

-kerry

<Andriy> bye!

<Payam> bye!

<krzysztof_j> bye

- DRAFT -

SSN XG

08 Sep 2010

Attendees

Contents

Progress on "Module by Module" documentation (and examples)

XG Wrap up

Summary of Action Items

Scribe.perl diagnostic output