– DRAFT –
(MEETING TITLE)

* i just did zakim

feedback from W3C on namespace

proposed: approve minutes https://‌www.w3.org/‌2017/‌dxwg/‌wiki/‌Meetings:ProfGui-Telecon2018.10.31

<antoine> +0

<ncar> proposed: approve minutes of last meeting https://‌www.w3.org/‌2018/‌10/‌31-profgui-minutes.html

+1

<ncar> +1

<antoine> +0

Resolved: approve minutes of last meeting https://‌www.w3.org/‌2018/‌10/‌31-profgui-minutes.html

open action items https://‌www.w3.org/‌2017/‌dxwg/‌track/‌products/‌3

<ncar> close: action-124

<ncar> close action-124

<ncar> resolved to close ACTION-124 & ACTION-219

<ncar> close action-124

<trackbot> Sorry, but no Tracker is associated with this channel.

<ncar> resolved to close ACTION-248 & ACTION-250

feedback from W3C on namespace

close action-124

<trackbot> Sorry, but no Tracker is associated with this channel.

ncar: feedback is that FPWD - short names are approved - its still not clear that the recommendation to use /ns/prof has been correctly relayed to the W3C staff

roba: how does redirect work to github if FPWD is frozen?
… and how does desire to conneg to JSON-LD work

Status of Guidance doc

ncar: not obvious - content type headers not supported by github
… we dont have enough detail - wait for official response?

Status of Guidance doc

ncar: chairs had asked for focus on guidance doc - but effort on FPWD for ontology of conneg-by-ap has been needed

@antoine: mainly been working on UCR .. can look next week

ncar: do we need a plan

roba: can we assign issues now
… @antoine how do we get requirements

<ncar> roba: antoine has a new list of requirements now

<ncar> roba: how can we get the Profiles doc to reflect this?

roba: these were introduced manually by nick based on tags at time

<ncar> https://‌github.com/‌w3c/‌dxwg/‌issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3Aprofile-guidance+label%3Arequirement+label%3Aplenary-approved+

<ncar> that is the link for profile-guidance, plenary-approved, requirements

roba: we should only have UCR requirements as issues - tagged as requirement and profile-guidance
… all other requirements should be cross linked to the new requirement and closed - and any position/resolution fo the issue recorded in new issue.
… so sort out github issues then resync document open issues.

<ncar> Steps to sort out Issues:

<ncar> 1. Antoine review plenary-approved requirement tagged Issues - to sync with UCR

<ncar> 2. ncar to review Issues tagged with requirement, not tagged with plenary-approved and deduplicate/close

<ncar> ... or update as needed

<ncar> 3. profgui group to remove plenary-approved tag

<ncar> 4. profgui to place all profile-guidance requirement tagged Issues in HTML doc

@antoine: what is deadline for ESWC paper?

ncar: paper is due Dec 10