See also: IRC log
13 telcos left
<bhyland> Last week's minutes, please approve: http://www.w3.org/2011/gld/meeting/2013-02-21
<BenediktKaempgen> +1
<DaveReynolds> +1
<fadmaa> +1
<gatemezi> +1
<bhyland> accepted, thanks
no new members on today's call
<bhyland> Main page, see http://www.w3.org/2011/gld/wiki/Main_Page
hadleybeeman is currently updating main WG page
aim is to reach mature stage for all vocabularies
and deliverables
at least to recommended status
DaveReynolds: last week all
issues were resolved apart from two
... one issue on relationships
between vocabularies
issue #58
<james> http://www.w3.org/2011/gld/track/issues/58
agreed not to define any more specific details
close issue-58
<trackbot> Closed ISSUE-58 Relate org:Organization to prov:Organization.
<TallTed> close issue-## notations aren't picked up thru IRC
<bhyland> To close it, go to http://www.w3.org/2011/gld/track/issues/58
<bhyland> ISSUE-55, ISSUE-56 and ISSUE-57 are awaiting PROV WG review. Remain pending review
Awaiting response from PROV WG
<cygri> ISSUE-55?
<trackbot> ISSUE-55 -- Use of prov:wasDerivedFrom -- pending review
<trackbot> http://www.w3.org/2011/gld/track/issues/55
<cygri> ISSUE-45?
<trackbot> ISSUE-45 -- Align treatment of registered addresses between Org and RegOrg -- pending review
<trackbot> http://www.w3.org/2011/gld/track/issues/45
<bhyland> Wonderful progress, thank you DaveR
For ISSUE-45, On org side, there is no range constraint, just a recommendation referring to REG ORG, so there is now no inconsistency
<bhyland> Moving forward now to DCAT since we have Fadi and Olyerickson
<bhyland> See https://www.w3.org/2011/gld/track/issues?sort=product
<bhyland> Sandro: Point of CR is to gather implementation info
<james> to see just non-closed dcat issues: https://www.w3.org/2011/gld/track/products/2
<bhyland> RE: W3C transiitions, see http://www.w3.org/2005/08/01-transitions.html
<hadleybeeman> Okay, I'm also looking at http://www.w3.org/2005/10/Process-20051014/tr
<hadleybeeman> Thanks!
<james> https://www.w3.org/2011/gld/track/products/5
<james> https://www.w3.org/2011/gld/track/actions/99
CLOSE ACTION-99
<trackbot> Closed ACTION-99 Send approved draft response to PROV-O WG.
CLOSE ACTION-100
<trackbot> Closed ACTION-100 Ask PROV-O WG for feedback on ISSUE-58.
Some work remains on specification wording. Fadi is working on that
<bhyland> see http://www.w3.org/TR/vocab-dcat/
Proposals on resolutions on remaining issues were made
<olyerickson> I see this proposal: http://www.w3.org/2011/gld/wiki/Data_Catalog_Vocabulary/AccessURLRedesign
no comments as of yet
fadmaa: will arrange telco this week to disucss dcat issues
<olyerickson> I thought it was fine when fadmaa proposed it during a recent call
fadmaa: and to close the issues
bhyland: are there any major obstaces for remaining issues?
<fadmaa> http://www.w3.org/2011/gld/track/products/2
fadmaa: those with pending review, are close to being closed
<fadmaa> http://www.w3.org/2011/gld/wiki/Data_Catalog_Vocabulary/AccessURLRedesign
fadmaa: others have proposals on how to close them, with no suggestions or objection
<fadmaa> http://www.w3.org/2011/gld/track/issues/43
<gatemezi> +1 for having a telco just for DCAT
fadmaa: only thing that needs further discussion is the naming of certain classes, which will be discussed during telco
<bhyland> @Fadi, if you can address Relationship of DCAT and VoID, see https://www.w3.org/2011/gld/track/issues/54 that would be helpful.
olyerickson: suggests that fadmaa sends a mail itemising main problems, to try and resolve issues ahead of telco
<bhyland> ACTION: Fadi to itemize in an email the issues that can be readily decided via email. Bias towards action! [recorded in http://www.w3.org/2013/02/28-gld-minutes.html#action01]
<trackbot> Created ACTION-101 - Itemize in an email the issues that can be readily decided via email. Bias towards action! [on Fadi Maali - due 2013-03-07].
<bhyland> +1 olyerickson
olyerickson: then the telco can just be to agree on these final decisions
cygri: does not agree that these issues can be resolved via email
<fadmaa> I sent few emails a couple of weeks ago: http://lists.w3.org/Archives/Public/public-gld-wg/2013Jan/0058.html and http://lists.w3.org/Archives/Public/public-gld-wg/2013Jan/0051.html
<fadmaa> http://lists.w3.org/Archives/Public/public-gld-wg/2013Jan/0053.html
cygri: as all the info has
already been circulated by email & wiki
... need now is to close issues and get +1s
... this formality is easier to do on a call
bhyland: it's time to finalise DCAT :)
cygri: if WG participants want to have an input in DCAT issues, they should go through all existing issues, give feedback
<bhyland> See https://dvcs.w3.org/hg/gld/raw-file/default/data-cube/index.html
<JoaoPauloAlmeida> ??P0 is JoaoPauloAlmeida
<bhyland> ISSUE-29 see https://www.w3.org/2011/gld/track/issues/29
DaveReynolds: Has added notes to ISSUE-29
<bhyland> ISSUE-32 see https://www.w3.org/2011/gld/track/issues/32
DaveReynolds: Editors now waiting on some feedback from list on these notes
<bhyland> Our goal is to get a LC out next week
DaveReynolds: will need a vote on next Thurs' call
<bhyland> Need: People teed up to do a review of DataCube
DaveReynolds: members should give
feedback before next Thurs' call
... if there are any objections. Let Richard/Dave know in the
next day or two
... otherwise it will be assumed there are no objections
<cygri> ISSUE-39?
<trackbot> ISSUE-39 -- Data Cube: Allow skos:Collections as value of qb:codeList -- open
<trackbot> http://www.w3.org/2011/gld/track/issues/39
<bhyland> On cygri's plate, see ISSUE-37, see https://www.w3.org/2011/gld/track/issues/37
cygri: will review ISSUE-37, 39
DaveReynolds had commented on all other open issues for DATACUBE
scribe: any volunteer to do an editorial/content level check on the specification?
<BenediktKaempgen> bhyland: shall I shortly speak about QB UC document?
<BenediktKaempgen> +q
Phil not on call
bhyland will contact Vassilios about if he is still participating on REG ORG and in group in general
<bhyland> See https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html
bhyland has made changes to glossary
<bhyland> Process: Ask the WG for a resolution that we're ready to publish as a Working Group Note
bhyland will send out an email asking members to review glossary
<bhyland> See https://dvcs.w3.org/hg/gld/raw-file/default/data-cube-ucr/index.html
BenedickKaempgen will review DATACUBE doc
<BenediktKaempgen> https://dvcs.w3.org/hg/gld/raw-file/default/data-cube-ucr/data-cube-ucr-20130227/index.html
BenedickKaempgen: has received feedback on initial draft and now is a collection of deployments
<gatemezi> @bhyland re Glossary, there is some mix up in the numbers, such as 10, 10.1 or 10.55.1. Is it because you are still working on the file?
BenedickKaempgen: document is pretty much stable. BenedickKaempgen asks WG to review it, so that it can be published as WG note
<bhyland> Benedikt: DataCube UC doc is in a good state & ready for review by WG and should be published as Working Group Note
<sandro> sandro: I suggest UCR be published as a WG Note
bhyland: no requirement that DataCube UC should be reg track
<bhyland> cygri: Confirmed Use Case doc should be a WG Note
cygri: there is a dependency for UC doc on DATACUBE spec, so we should ensure all requirements in UC doc are satisfied by spec
<bhyland> Deirdre: Last Friday was deadline for call for contributions and they received many.
<bhyland> See http://2013.data-forum.eu/news/european-data-forum-2013-call-contribution
<cygri> cygri: as long as we verify that the UC&R doc doesn't imply new requirements that the spec doesn't cover now, i'm ok with publishing UC&R as Note
<bhyland> Call for Exhibits closes on 11-March
<gatemezi> We finally contribute to EDF2013 on the research track
<DaveReynolds> Benedikt - happy to review the Use Case doc. Though probably can't do that till after done the QB LC draft, just not enough hours in the day!
<bhyland> Deirdre: Big data in practice and commercial tools are welcome, also academic research projects & demos welcome.
<bhyland> See http://2013.data-forum.eu/call-for-exhibits
<bhyland> The deadline for submissions is: 11th Mar 2013, 02.00pm CET. Accepted exhibits will be notified on 15th Mar 2013
<bhyland> Table format, bring posters, roll ups, demos on laptops, flyers all welcome
<bhyland> Next F2F3 details see http://www.w3.org/2011/gld/wiki/F2F3
<bhyland> Please consider looking & updating the http://www.w3.org/2011/gld/wiki/F2F3#DRAFT_Agenda
<gatemezi> thanks all!
<BenediktKaempgen> Thanks
<bhyland> @DeirdreLee, are you right publish minutes or do you need any support?
need support
but time i learned :)
i'm still on call if that's easiert
<cygri> starting point: https://www.w3.org/2009/CommonScribe/panel/?group=ldp&go=Use+This+Group
<bhyland> I have summarized actions here:
<bhyland> http://www.w3.org/2011/gld/wiki/Meetings:Telecon20130228#Scribe.27s_End_of_Meeting_Checklist
<bhyland> I'll monitor IRC and if you don't publish within 5 minutes, I'll do it :-)
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/DATCUBE/DATACUBE/ Succeeded: s/DCAT/DATACUBE/ Succeeded: s/Proc/ Proc/ No ScribeNick specified. Guessing ScribeNick: DeirdreLee Inferring Scribes: DeirdreLee WARNING: No "Present: ... " found! Possibly Present: BartvanLeeuwen BenedickKaempgen Benedikt BenediktKaempgen DaveReynolds Deirdre DeirdreLee JoaoPauloAlmeida Mike_Pendleton Need P0 P27 Process Sandro TallTed bhyland cygri fadmaa gatemezi hadleybeeman https james martin_ olyerickson tinagheen trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy WARNING: No meeting title found! You should specify the meeting title like this: <dbooth> Meeting: Weekly Baking Club Meeting WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 28 Feb 2013 Guessing minutes URL: http://www.w3.org/2013/02/28-gld-minutes.html People with action items: fadi[End of scribe.perl diagnostic output]