– DRAFT –
DXWG Plenary

<kcoyle> https://‌www.w3.org/‌2018/‌11/‌13-dxwg-minutes

<kcoyle> PROPOSED: approve the minutes of November 13

+1

<SimonCox> +1

<kcoyle> +1

<DaveBrowning> +1

<ncar> +1

<Jaroslav_Pullmann> +1

<annette_g> +0 was not there

<antoine> +1

Resolved: approve the minutes of November 13

<kcoyle> https://‌www.w3.org/‌2017/‌dxwg/‌track/‌actions/‌244

antoine: this action is to do with guidance and the name of resourcedescriptor Class

<kcoyle> close action 258

<kcoyle> close action-258

<trackbot> Closed action-258.

<AndreaPerego> Reply to Luca Trani's mail: https://‌lists.w3.org/‌Archives/‌Public/‌public-dxwg-comments/‌2018Nov/‌0002.html

kcoyle: have docs passed pub rules

ncar: have passed recently - only text changes - will take an action to re-run

Action: ncar - re-scheck pubrules compliance for profiles ontology and conneg docs.

<trackbot> Created ACTION-260 - - re-check pubrules compliance for profiles ontology and conneg docs. [on Nicholas Car - due 2018-11-27].

naming of documents and artefacts

dsr: global space, names need to be indicative of the area
… need to look at other uses of profile
… its not clear if its about DCAT, or dataset exchange

<kcoyle> roba: prof ontology not exclusive to catalogs; common abstract catalogs; europeana use case, ogc use case

<kcoyle> ... not limited to data exchange

<kcoyle> ... problem with developing specific use case is that people complain that they are too narrow

<kcoyle> ... we tried to avoid that by working with a high-level scope, the DC terms standard

<kcoyle> ... hard to narrow to w3c

<kcoyle> dsr: many profiles types; definition was clear to me; the broader the defintion the more communities we need to reach to

<kcoyle> ... suggest using the dx or dxwg in the namespace

<kcoyle> ... doesn't restrict you, says this group is responsible

<kcoyle> roba: I'm agnostic about that; looks like precident is changing (cf. prov)

<kcoyle> ... general sense is profile is a specification conforming to something

<kcoyle> ... prof meets that

<kcoyle> ... semantically prof ontology not tied to DX case

<SimonCox> How much has the technology been tested? (really?) if it is in DX context so far, then DX is probably the best option ...

<kcoyle> dsr: "profile" means different things to different people

antoine: in the light of discussion would be OK with /dx - not preferred - but if it helps reduce discussion its good
… there doesnt appear to be any consistent policy at w3c

annette_g: suggest we think about use of term profile - and can it be refined?

ncar: no-one wanted the /dx but if it will really make a difference at W3C we can live with it?

<SimonCox> else first-come, first served -

SimonCox: the counter-argument - structure naming is appropriate if you have a lot of names - experience suggests that this is a bad idea.
… tend not to eventuate.

<SimonCox> ... because lots might not arrive

<annette_g> dxprof is still pretty short

<kcoyle> roba: this isn't limited to data exchange - send to w3c as is

<kcoyle> ... it's worthwhile looking at it on its own merits

<kcoyle> dsr: definition in document meant very little; come up with a few words to narrow it down

<annette_g> +1

<kcoyle> dsr: the way you are using profile and assumptions you are making; others could use word in other ways

<kcoyle> ... what other words would you add to make it clearer?

<kcoyle> roba: profiles guidance document has those words

<annette_g> Think of how many of us were unsure about what a profile was when we joined this group.

<kcoyle> dsr: profiles of what? of datasets? protocols?

<kcoyle> roba: all of the above

<kcoyle> dsr: if you claim general than you need to reach out to a broader community

<kcoyle> ... need words that unambiguously identify the area - there will be other groups coming along who use this word

NB: pther communities are "in the room" in the sense of their published definitions and usages we have taken into account

<antoine> ncar++

ncar: adding the short wg code in the name adds barrier to understanding - its not interpretable

<ncar> +1 dx

<kcoyle> straw vote: use dx as intermediate level in domain name

<SimonCox> +1 time to move on - we don't want FPWD held up any longer

<kcoyle> straw vote: use dx as intermediate level in domain name in the TR documents

+1

<annette_g> -1 put it in the name of a profile

<ncar> so /TR/dx/profile-guidance?

<AndreaPerego> -1

<antoine> 1+

<antoine> +1

<ncar> 0

<Jaroslav_Pullmann> 0

<DaveBrowning> 0

<ncar> so /TR/dx-profile-guidance?

<ncar> so /TR/dx-profiles & /ns/dx/prof

<ncar> so /TR/dx-prof-conneg

this group wont exist in 6 months .. so for documents these are legacy and OK - but for ongoing things like dcat and prof ontologies is just messy and looks different for all others.

<ncar> so dx- avoids /dx/

<annette_g> could we do /TR/dx-prof and /ns/dx-prof?

<ncar> yes! (annette_g)

<antoine> http://‌www.w3.org/‌2004/‌02/‌skos/‌core#

<kcoyle> strawpoll: use dx- instead of /dx/ as per ncar above (e.g. dx-prof-conneg)

<annette_g> +1

<antoine> +1

<SimonCox> +1

<ncar> +1

+0

+1

<DaveBrowning> +1

<Jaroslav_Pullmann> +1

<AndreaPerego> +1

Resolved: group wishes to use /TR/dx-... for namespaces

<annette_g> can't it be both?

Resolved: group wishes to use /TR/dx-... for docment namespaces

<kcoyle> proposed: group wishes to use /TR/dx-... for docment namespaces

<ncar> +1

<AndreaPerego> +1

<antoine> +1

+1

<annette_g> +1

<DaveBrowning> +1

<SimonCox> +1

<Jaroslav_Pullmann> +1

Resolved: group wishes to use /TR/dx-... for docment namespaces

<kcoyle> propose consistent approach

<AndreaPerego> -1 to change DCAT namespace

<SimonCox> https://‌www.goodreads.com/‌quotes/‌353571-a-foolish-consistency-is-the-hobgoblin-of-little-minds-adored

<ncar> http://‌www.w3.org/‌ns/‌prov#, http://‌www.w3.org/‌ns/‌org# therefore http://‌www.w3.org/‌ns/‌prof/. It is as abstract!

dsr: two things - the document shortnames and the ontology namespaces

kcoyle: we have resolution for the document namespaces - can the ontology namespaces come later?

dsr: no

kcoyle: what about using github locations

dsr: profiles ontology - definition should not be in abstract.

<ncar> Namespace in abstract follows SSN precedence

Action: roba to change abstract to take out definition to add explanation of scope, to change document shortnames

<trackbot> Error finding 'roba'. You can review and register nicknames at <https://‌www.w3.org/‌2017/‌dxwg/‌track/‌users>.

Action: change abstract to take out the definition, to add explanation and change document shortnames.

<trackbot> Error finding 'change'. You can review and register nicknames at <https://‌www.w3.org/‌2017/‌dxwg/‌track/‌users>.

Action: roba to change abstract to take out the definition, to add explanation and change document shortnames.

<trackbot> Error finding 'roba'. You can review and register nicknames at <https://‌www.w3.org/‌2017/‌dxwg/‌track/‌users>.

Action: @roba change abstract to take out the definition, to add explanation and change document shortnames.

<trackbot> Error finding '@roba'. You can review and register nicknames at <https://‌www.w3.org/‌2017/‌dxwg/‌track/‌users>.