– DRAFT –
DXWG profgui
31 October 2018
https://www.w3.org/2017/dxwg/wiki/Meetings:ProfGui-Telecon2018.09.31#Annotations
Action: ncar email to group re: time zones
roba: frames in json-ld; this is a profile because selects subset of it
… with contract around serialization. Rob S said he would write up a use case
here are the minutes: https://www.w3.org/2018/10/26-dxwg-minutes#x06
roba: we need more detail, could be a use case
… suggest we put an issue in prof guidance doc to see if appropriate to json-ld frames
roba creates issue 524 for json-ld case
ncar: json-ld is very long, very complex spec. We need to take it seriously and understand how it may fit with profiles
kcoyle: no other things from f2f friday afternoon that are profile guidance
roba: there can't be implementations of guidance, can there?
ncar: will there be a best practices list in the profgui?
roba: identify conformance and testing would be so there can be implementation evidence
… make known in fpwd that we want feedback
<ncar> Created issue https://github.com/w3c/dxwg/issues/525 for Guidance conformance target
roba: and https://github.com/w3c/dxwg/issues/524
ncar: would be good to use same terminology for all of the documents
… what does w3c require for a guidance document?
Action: kcoyle ask Dave and Philippe what we need as implements for a guidance document
<ncar> conformanceTarget issue: https://github.com/w3c/dxwg/issues/521
roba: qsa parameter names, we need to know if a range of existing implementations conform to the abstract model
… some checks in w3c have a profile, like fpwd
… some existing implementations of negotiation by profiles, and are these in scope in the guidance?
kcoyle: will we discuss profile negotiation in the guidance document? and to what extent?
roba: yes
ncar: I don't jump to that
kcoyle: is this dependencies between documents?
roba: this is preparing ourselves for the scope of the guidance document?
… are these in scope?
ncar: can this be an issue?
… close the conneg issue and raise this as an issue?
kcoyle: just qsa or a larger issue?
ncar: should the guidance doc? ...
roba: there are existing things that are called profiles in the wild. Does the guidance document recognize those
<roba> Should guidance about profiles identify existing practices using implicit profiles as valid examples or as prior work only
roba: as valid profiles, or non-conformant prior work?
<ncar> Issue initially https://github.com/w3c/dxwg/issues/526
Should the Guidance doc recognise existing, non-interoperable, profiles as valid
kcoyle: has taken action about relation to best practices
ncar: security and privacy issue
… do have text in conneg, lars answered questionnaire
… do the same thing for this doc?
kcoyle: our text will be different from conneg
ncar: putting link to questionnaire in issue
ncar: closing issue relating to family of docs
ncar: closing #428
roba: close "what is a profile?"
kcoyle: this is more than a definition; it's what is the nature of a profile?
kcoyle: improve and move definitions?
ncar: yes, close this one: #371
ncar: improve introduction - antoine says leave open
ncar: profiles ontology example - have examples in profgui, not yet known which one
… which would be useful in the guidance document?
ncar: human-readable (https://github.com/w3c/dxwg/issues/369)
kcoyle: we aren't there yet
ncar: profont gives us a way to address this problem
kcoyle: can we remove the profgui label from some of the older ones?
Action: ncar will propose issues that no longer need the profgui label
kcoyle: asks nick how we will get the writing done
ncar: been busy with conneg, so no
kcoyle: suggest prioritize, and assign writing sections to people
roba: anyone other than antoine?
kcoyle: both annette and alejandra have shown an interest
roba: or make a call
ncar: how close are we?
kcoyle: my guess is that we need a more detailed outline
… maybe look more at issues and requirements than the document, which is very vague
roba: using issues means we can assign them in github
kcoyle: requirements tend to be broad; issues may be more specific
roba: go through issues decide if they go into the document, find a place, ask someone to write it up
Action: ncar (and rob) will go through issues and try to place in document and make assignments or ask volunteers to write
kcoyle: also need to prioritize
ncar: can we not prioritize ?
roba: we can reference dependencies in issues
kcoyle: really like referencing dependencies