W3C

- DRAFT -

Government Linked Data Working Group Teleconference

27 Sep 2012

Agenda

See also: IRC log

Attendees

Present
+1.540.898.aaaa, Sandro, +3539149aabb, mhausenblas, cygri, BartvanLeeuwen, +33.4.93.00.aaee, DeirdreLee, bhyland, gatemezi, fadmaa, DaveReynolds, PhilA2, Gofran, Mike_Pendleton, tinagheen, Yigal, +61.4.286.0.aaff, Chris_Beer
Regrets
Chair
SV_MEETING_CHAIR
Scribe
DeirdreLee

Contents


<trackbot> Date: 27 September 2012

<bhyland> Good morning & afternoon all

<bhyland> Agenda:

<bhyland> http://www.w3.org/2011/gld/wiki/Meetings:Telecon20120927

<bhyland> GT had last minute work obligation and asked me to chair today's meeting

<bhyland> Please confirm last week's minutes http://www.w3.org/2011/gld/meeting/2012-09-20

<mhausenblas> +1

<scribe> Scribe: DeirdreLee

<gatemezi> +1

<PhilA2> +1 to last week's minutes

Chris Beer has just joined GLD WG

<PhilA2> Public spending http://publicspending.medialab.ntua.gr/

There are also two other new members

Vassilios Peristeras is an invited expert

<bhyland> Welcome to the new IEs: Chris Beer, Agis Papantoniou, and Vassilios

<PhilA2> Agis Papantoniou shows up on IRC as agipap

Working towards getting deliverables to LC status

bhyland: is there sufficient interest in the group and enough work being done to justify an extension
... cygri emailed summary of deliverables and status to list
... could those named in that summary discuss status

<cygri> the deliverables summary is here btw: http://www.w3.org/2011/gld/wiki/Deliverables

Org Vocab

DaveReynolds: developed originally outside of WG

<bhyland> DaveReynolds: Mature and used vocab but there were changes suggested by Bart ...

DaveReynolds: feedback from BartvanLeeuwen on how vocab could be updated

<bhyland> ORG Vocab FPWD here http://www.w3.org/TR/vocab-org/

<DaveReynolds> http://lists.w3.org/Archives/Public/public-gld-wg/2012Sep/0030.html and http://lists.w3.org/Archives/Public/public-gld-wg/2012Sep/0031.html

DaveReynolds: need to define role within ORG
... longest use of ORG is from UK government publishing data periodically

<PhilA2> UK Government Organograms

DaveReynolds: Jeni Tenison carried out work on this
... it may be worth finalising, based on usage by Bart and Jeni
... incorporate Jeni's extension into ORG
... extension based around role and post
... this overlaps with some of ORG, so have to decide how to incorporate/integrate it
... recommendations should have to be included

<mhausenblas> Michael: Would be happy to go to LC with that

DaveReynolds: asks should there be another working draft version or could we go straight to LC with these changes

<bhyland> Bart feels satisfied with the changes that DaveReynolds

<bhyland> mentioned

bhyland: as long as the issues that have been raised have been considered/addressed, there may not be a need for another FPWD

<bhyland> Sandro: If we say it is ready to LC, that means everyone in the WG has considered it & made whatever comments they wish to make.

DaveReynolds: agrees with Bernadette. Highlights that once the document goes to LC, all comments should have been made

PhilA2: Is there still writing to be done on ORG?

DaveReynolds: there is still some writing to be done
... suggests that this writing is finalised, and there is then sent to list for review, and then lt document go to LC

<mhausenblas> Michael: based on http://www.w3.org/2005/10/Process-20051014/tr.html#last-call

<Zakim> mhausenblas, you wanted to say just waiting for a proposal from DaveReynolds ;)

mhausenblas: confirms that LC means the requirements has been met in terms of charter and dependencies on other groups has been satisfied
... once this is the case, Dave could push for LC

<Zakim> PhilA, you wanted to talk about implementations other than UK gov

PhilA: Do we know of an implmentation of ORG other than UK government organograms?
... in order to get to LC we need at lest 2

<bhyland> PhilA2: Asked whether there are any other reference implementations for ORG besides UK Organograms project

DaveReynolds: There have been other uses, but doesn't know if they are public

<bhyland> MartinAlvarez: Said there are two implementation in Spain … Martin to add links.

MartinAlvarez: It has been used by the andalucia government and in the Spanish OD initiative

<gatemezi> Here http://data.lirmm.fr/ontologies/sp in France,

BartvanLeeuwen: is involved in a disaster-managment project that plans to use ORG vocabulary

<gatemezi> you have also a ude -case of Org vocab

<martinAlvarez> Andalussian Open Data: [http://www.juntadeandalucia.es/datosabiertos/portal.html] (Datasets are not public yet, but in process)

bhyland: Can Dave specify a date when all these updates will be made?

<PhilA2> So when we get to CR we should be sitting in clover

DaveReynolds: Has just received a comment from Chris Beer, needs time to incorporate these
... aims to send out a revised document by next Thursday's meeting, so we can take a vote by the following Thursday

<martinAlvarez> Spanish Open Data [http://datos.gob.es] will publish these data as well

<bhyland> … suggested appointing a Reviewer

DaveReynolds: should we point to a reviewer now?
... a reviewer is one or two people who are appointed to read the document, both for content and typo purposes, before LC version is published

<bhyland> Process note: 1-2 reviewers appointed to ensure QA within GLD WG … to avoid typos and glaring errors before going to LC

<bhyland> Many thanks to Bart and Michael for agreeing to be Reviewers.

<mhausenblas> Michael: You're *very* welcome

bhyland: will read as native english speaker and as a potential user and as chair

<bhyland> Woohoo!

DCAT

<bhyland> Yes please Deirdre!

<bhyland> two actions really, one for Dave, second as reviewers for Michael, Bart and me

fadmaa: suggests to go through the issues in dcat and try and clear them

<bhyland> Fadi proposed going through tracker re: DCAT see https://www.w3.org/2011/gld/track/products/2

<cygri> ISSUE-4?

<trackbot> ISSUE-4 -- Should we define ranges for other people's vocabularies? -- raised

<trackbot> http://www.w3.org/2011/gld/track/issues/4

suggestion: close issue with no actions reason: based on the related discussion it seems that this doesn't make big difference. My preference (and Phil's as in the issue description) is to provide usage note without stating assertions about external properties

<sandro> PROPOSED: Close ISSUE-4 saying "No", but we'll include usage notes

<cygri> +1

<mhausenblas> +1

<gatemezi> +1

<sandro> +0

<DaveReynolds> +1

<fadmaa> +1

<sandro> RESOLVED: Close ISSUE-4 saying "No", but we'll include usage notes

<cygri> ISSUE-5?

<trackbot> ISSUE-5 -- Implications of the domain of dcterms:accrualPeriodicity -- raised

<trackbot> http://www.w3.org/2011/gld/track/issues/5

suggestion: close with no actions reason: the implication of inferring dcat:Dataset as dcterms:Collection is fine

<sandro> PROPOSED: Close ISSUE-5 with no action.

(suggestions come from Fadi's mail to mailing-list)

<gatemezi> +1

<martinAlvarez> +1

<fadmaa> +1

<sandro> RESOLVED: Close ISSUE-5 with no action.

<cygri> ISSUE-6?

<trackbot> ISSUE-6 -- How should dcat publishers figure out good URIs for properties with non-literal ranges? -- raised

<trackbot> http://www.w3.org/2011/gld/track/issues/6

suggestion: close with no action reason: out of scope. We can provide some pointers in the usage note for values that have some general consensus but without making this part of the vocabulary specification

fadmaa: does anyone have concrete suggestions?

cygri: we don't need to make any formal recommendations, but we should make some comment outlining possibilities

<bhyland> cygri: There should be mention of the possibilities for handling non-literal ranges

<sandro> cygri: We don't need a formal MUST, but we should say something, outlining the possibilities. Or maybe in the Best Practices document. Some paragraphs, with some examples.

cygri: could this be included in the best-practice document?

<PhilA2> +1 to talking about this in the BP document. It's an issue but I agree it's not specific to DCAT

<bhyland> +1

<sandro> bhyland: Right, it's not unique to DCAT.

cygri: these patterns are applicable to all vocabularies, not just DCAT

<gatemezi> +1

<sandro> PROPOSED: Close ISSUE-6, deferring to Best Practices for this kind of advice

<bhyland> +1

<cygri> PROPOSAL: move ISSUE-6 from DCAT to BP, and add ACTION to a DCAT editor on putting in a link

<bhyland> +1

<fadmaa> +1

<sandro> +1

PhilA2: there is a dependency on the BP doc

<cygri> +1

<sandro> RESOLVED: move ISSUE-6 from DCAT to BP, and add ACTION to a DCAT editor on putting in a link

<PhilA2> ACTION fadmaa to include text in DCAT to point to the BP doc, with link to the issue in the interim

<trackbot> Created ACTION-77 - Include text in DCAT to point to the BP doc, with link to the issue in the interim [on Fadi Maali - due 2012-10-04].

<cygri> ISSUE-7?

<trackbot> ISSUE-7 -- Drop dcat:accessUrl, use the URI of the dcat:Download resource instead -- raised

<trackbot> http://www.w3.org/2011/gld/track/issues/7

<cygri> PROPOSAL: drop ISSUE-7 with no action

<sandro> PROPOSAL: Close ISSUE-7, no action, keeping accessUrl as it's still needed.

suggestion: close with no actions reason: dcat:accessURL is needed especially when a dataset has multiple distributions (see the related emails on the issue page for details)

<cygri> +1

<sandro> +1

<DaveReynolds> +1

<fadmaa> +1

<mhausenblas> +1

<gatemezi> +1

<sandro> RESOLVED: Close ISSUE-7, no action, keeping accessUrl as it's still needed.

<cygri> ISSUE-8?

<trackbot> ISSUE-8 -- add a property to distinguish direct and indirect access of dcat:Distribution -- raised

<trackbot> http://www.w3.org/2011/gld/track/issues/8

<sandro> PhilA2: I hate accessUrl, but I see it's necessary.

suggestion: no suggestion reason: need some further discussions. I summarized three possible options here at: http://lists.w3.org/Archives/Public/public-gld-wg/2012Mar/0080.html

<cygri> ISSUE-9?

<trackbot> ISSUE-9 -- dcat:Distribution and its subclasses are unnecessary -- raised

<trackbot> http://www.w3.org/2011/gld/track/issues/9

fadmaa: there is no clear consensus on this issue

<cygri> +1

<sandro> yes, all issues need to be closed before going to LC

bhyland: leave issue 8 and 9 open

DeirdreLee: can we have a plan to resolve these issues

<sandro> issue-10?

<trackbot> ISSUE-10 -- Refine dcat:granularity to dcat:spatialGranularity and dcat:temporalGranularity -- raised

<trackbot> http://www.w3.org/2011/gld/track/issues/10

bhyland: follow-up on this on email, if it can't be resolved, it will be discussed in future telco

suggestion: close with no actions reason: dcat:granularity is not much used in practice now (but still used by data.gov for example and therefore I don't support dropping it). It is hard to suggest refinement to it. suggest keeping it as a general property in case people want to use it. --> close no action

<bhyland> I hear 'move it to Open status'

<gatemezi> fadmaa, so we leave it just because is used by data.gov?

fadmaa: it is not clear how it will be used, but there is potential for it, so therefore just to leave it and not further refining it to subproperties

<sandro> +1 cygri don't include properties that wont be understood/consistently used.

<bhyland> Cygri: Prudent thing to do is drop it *if* we don't think it will be used consistently...

cygri: if it is unclear how it is used, the prudent thing is to drop it

<bhyland> +1

<gatemezi> +1

<bhyland> Deirdre: Mentioned it is used on data.gov so we might break something which is undesireable.

<gatemezi> +1 to have a sample of the use-case of data.gov

<bhyland> I suggest we move this to Open status and check back next week with George as our data.gov POC

<tinagheen> Is Chris Musialek still a member of this WG? We could ask him for more details as he works on data.gov.

PhilA: if we are discussing granularity or coverage, because spatial and temporal are DC terms

<cygri> i'm ok with changing ISSUE-10 to open

<bhyland> Please make sure you visit this page, http://www.w3.org/2011/gld/wiki/Deliverables

bhyland: we didn't get to discuss the deliverables summary that Richard sent around
... we should review ISA vocab docs in our own time and use telcos to discuss

<sandro> fadmaa, can you email proposed resolutions, like I've been putting on IRC?

<bhyland> ta

<mhausenblas> Michael: for the record, Gofran is already a member

<PhilA2> DeirdreLee: We've discussed ADMS here at DERI. Gofran Shukair has been involved with it from the beginning so she's going to join the editoral team for ADMS

<bhyland> +1 to adding Gofran to the ISA Programme vocab review group

<bhyland> s/Gogran/Gofran

Deliverables Schedule

<bhyland> Please review http://www.w3.org/2011/gld/wiki/Deliverables for next week


.mhausenblas: People vocabulary. what should the namepace be?

ISA Programme vocabs


.mhausenblas: this decision should be made by the group

<Zakim> mhausenblas, you wanted to quickly state something re People vocab

<sandro> The only promise to the EC was that this would considered.

<PhilA2> No one disagrees with you Michael, certainly not me :-)

<PhilA2> And it's why these things have not yet been published...

<sandro> bhyland: We just agreed to review it.

<mhausenblas> [[ Finally, W3C and the WG chairs made a commitment to the European Commission that we would, in some way, publish the ISA Person Core Vocabulary in w3.org space. We can't just ignore that commitment. ]]

bhyland: there's no rubber-stamping on this, so it does needs everyones input to review it and agree to it, before we include it

<bhyland> Right, the commitment is to *review* it and if OK, we'll go through the normal & usual REC track process

<mhausenblas> Michael: I agree with the interpretation that the chairs have committed to review it, yes.

<cygri> thanks all!

<gatemezi> thanks!

<DaveReynolds> Thanks all.

Action Dave to include all updates and distribute next version of ORG vocabulary by next Thursday's meeting (4th Oct)

<trackbot> Created ACTION-78 - Include all updates and distribute next version of ORG vocabulary by next Thursday's meeting (4th Oct) [on Dave Reynolds - due 2012-10-04].

ACTION mhausenblas and bartvanLeeuwen to review the final version of the ORG vocabulary for content and typo errors before the document is released as LC

<trackbot> Created ACTION-79 - And bartvanLeeuwen to review the final version of the ORG vocabulary for content and typo errors before the document is released as LC [on Michael Hausenblas - due 2012-10-04].

<bhyland> Thanks Deirdre for keeping up with today's minutes

<bhyland> Do you need any help publishing minutes Deirdre?

<bhyland> OK, I'll do it.

thanks Bernadette

<bhyland> np

<bhyland> Minutes have been published here http://www.w3.org/2012/09/27-gld-minutes.html

<bhyland> Thanks all

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.137 (CVS log)
$Date: 2012/09/27 15:46:51 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/ICR/IRC/
Succeeded: s/Topics/Topic/
Succeeded: s/Bart/BartvanLeeuwen/
Succeeded: s/voca/vocab/
Succeeded: s/chaire/chair/
Succeeded: s/Gogran/Gofran/
FAILED: s/Gogran/Gofran/
Found Scribe: DeirdreLee
Inferring ScribeNick: DeirdreLee
Default Present: +1.540.898.aaaa, Sandro, +3539149aabb, mhausenblas, cygri, BartvanLeeuwen, +33.4.93.00.aaee, DeirdreLee, bhyland, gatemezi, fadmaa, DaveReynolds, PhilA2, Gofran, Mike_Pendleton, tinagheen, Yigal, +61.4.286.0.aaff, Chris_Beer
Present: +1.540.898.aaaa Sandro +3539149aabb mhausenblas cygri BartvanLeeuwen +33.4.93.00.aaee DeirdreLee bhyland gatemezi fadmaa DaveReynolds PhilA2 Gofran Mike_Pendleton tinagheen Yigal +61.4.286.0.aaff Chris_Beer
Agenda: http://www.w3.org/2011/gld/wiki/Meetings:Telecon20120927

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 27 Sep 2012
Guessing minutes URL: http://www.w3.org/2012/09/27-gld-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]