<harsh_> scribe: ElmarK

<scribe> scribe:ElmarK

<harsh_> chair: harsh_

Vote to publish DPVCG as a public CG working draft

<scribe> ACTION: ElmarK to send a pull request to harsh_ with minor fixes (typos, full names)

<trackbot> Error finding 'ElmarK'. You can review and register nicknames at <https://www.w3.org/community/dpvcg/track/users>.

<harsh_> Any other issues/comments?

Axel's comments on the working draft.

Regarding the missing figure, Harsh was hoping that Bert would be in the call. We will have to check with him regarding relative links.

Bert proposed to link to GitHub repository for the individual modules and host them there.

<harsh_> +1's for vote if agree

<ramisa> +1

+1

<Fajar> +1

<bud> +1

<harsh_> Thanks, we can accept this suggestion

Draft: https://dpvcg.github.io/extract-sheets/index.html

We can go ahead with NACE vocabulary as is.

Fajar: is there any complete example that integrates all modules/aspects?

Harsh: we need a use cases section that shows how the vocabulary can be used.

We'll publish the working draft and later add use cases,..

<harsh_> ISSUE: Describe use-cases and examples showing how the vocabulary should be or can be used

<trackbot> Created ISSUE-26 - Describe use-cases and examples showing how the vocabulary should be or can be used. Please complete additional details at <https://www.w3.org/community/dpvcg/track/issues/26/edit>.

How much time should we leave for comments?

Axel suggested 1 month.

Harsh: we can always extend it.

1 month ok for everyone?

+1

<Fajar> +1

<harsh_> +1

<ramisa> +1

<bud> +1

<harsh_> Accepted 1 month for comments on vocab

ISSUE: Discuss accompanying primer document

<trackbot> Created ISSUE-27 - Discuss accompanying primer document. Please complete additional details at <https://www.w3.org/community/dpvcg/track/issues/27/edit>.

Harsh: How are we going to process comments. We included multiple options, which ones should we allow.

Suggestion harsh_: Comments are welcome everywhere, but formal requests should be filed via the mailing list.

+1

<Fajar> +1

<ramisa> +1

<bud> +1

Accepted: have multiple channels for comments, but formal requests for extension should be sent via Email.

Harsh: Is it ok to create a separate repository on GitHub for the vocabulary (just for the RDF and HTML, not for the code that generates it, keep those separate)

Should be better organized that way.

+1

Right now we have several repositories. We could remove those and have one repository that has all the vocabularies and the documentation. So everything that is hosted on the w3c website should be there.

Proposal is to clean up the repository to make it easier for people to comment on GitHub.

Separate repositories for each namespace or all vocabularies in one repository?

Fajar: In favor of having separate repositories.

<harsh_> So we should have three repositories: dpv, dpv-nace, dpv-gdpr ?

+1

<harsh_> Or one repository for all three?

Vote: Shall we have 3 separate repositories?

<Fajar> +1

+1

<harsh_> @axelpolleres online? would appreciate comments on this-

<axelpolleres> what again is the question?

<harsh_> So we should have three repositories: dpv, dpv-nace, dpv-gdpr ? Or one repository for all vocabularies?

(repositories on GitHub)

<axelpolleres> what is meant by "repositories"? on git?

(repositories on GitHub)

<harsh_> Yes, how we organise them on Github

<axelpolleres> no strong opinions

<harsh_> Okay, let's go with general consensus

<axelpolleres> kk

<harsh_> separate repositories for each vocab as agreed

Decision: to have three GitHub repositories: dpv, dpv-nace, dpv-gdpr

<scribe> ACTION: harsh_ to update the document according to today's agreement.

<trackbot> Error finding 'harsh_'. You can review and register nicknames at <https://www.w3.org/community/dpvcg/track/users>.

<scribe> ACTION: harsh_ to clean up/restructure the GitHub repository according to today's agreement.

<trackbot> Error finding 'harsh_'. You can review and register nicknames at <https://www.w3.org/community/dpvcg/track/users>.

<harsh_> ACTION: harsh to update the document according to today's agreement.

<trackbot> Created ACTION-120 - Update the document according to today's agreement. [on Harshvardhan Pandit - due 2019-06-25].

<harsh_> ACTION: harsh to clean up/restructure the GitHub repository according to today's agreement.

<trackbot> Created ACTION-121 - Clean up/restructure the github repository according to today's agreement. [on Harshvardhan Pandit - due 2019-06-25].

<scribe> ACTION: elmar to send a pull request to harsh_ with minor fixes (typos, full names)

<trackbot> Created ACTION-122 - Send a pull request to harsh_ with minor fixes (typos, full names) [on Elmar Kiesling - due 2019-06-25].

Harsh suggests that one of the chairs should send the published draft to the semantic web mailing list once published.

<harsh_> Welcoming comments/feedback

Timeline: Harsh will send final version to Bert; by the end of the week a first draft can be published.

Decision on next call will be made via the mailing list.

<scribe> ScribeNick: ElmarK

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: Fajar Ramisa bud Elmar Harsh
Found Scribe: ElmarK
Inferring ScribeNick: ElmarK
Found Scribe: ElmarK
Inferring ScribeNick: ElmarK
Found ScribeNick: ElmarK
Found Date: 18 Jun 2019
People with action items: elmar elmark harsh harsh_

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)