06:08:07 RRSAgent has joined #dxwg 06:08:07 logging to https://www.w3.org/2018/05/09-dxwg-irc 06:08:16 rrsagent, make logs public 06:08:34 chair: PWinstanley & KCoyle 06:08:48 rrsagent, create minutes v2 06:08:48 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html PWinstanley 06:12:33 kcoyle has joined #dxwg 06:12:39 SimonCox has joined #dxwg 06:12:45 present+ 06:12:54 Jaroslav_Pullmann has joined #dxwg 06:12:54 present+ 06:12:54 present+ 06:12:55 present+ 06:12:55 present+ 06:12:59 present+ 06:13:01 DaveBrowning has joined #dxwg 06:13:03 scribenick: SimonCox 06:13:08 present+ 06:13:25 meeting: DXWG f2f3 06:14:03 agenda: https://www.w3.org/2017/dxwg/wiki/F2f3#Wednesday.2C_May_9.2C_8-17_CEST_.28in_your_time_zone.29 06:14:23 scribenick: SimonCox 06:14:36 chair: PWinstanley 06:14:43 https://docs.google.com/document/d/15OfNXU9AJ-cZysc7uYP-Gks5dDa8n2B5IN6rWa3kRpo/edit#heading=h.70ebjavd7jrw 06:15:19 q? 06:16:20 PWinstanley: yesterday clarified issues re Profiles. Today - construct skeleton of Profile guidance document 06:16:25 https://www.w3.org/2018/05/08-dxwg-minutes 06:17:08 PWinstanley: focused on validation and relationships between profiles 06:17:34 ... all ok? Any overnight epiphanies? 06:17:41 q+ 06:17:45 q+ 06:18:10 kcoyle: relations are awkward 06:18:12 q- 06:18:18 PWinstanley: does section need breaking up? 06:18:27 kcoyle: need to go back to UCs ... 06:18:27 q+ 06:19:01 q? 06:19:25 ack Jaroslav_Pullmann 06:19:26 Action: kcoyle to review profiling use-cases 06:19:27 Created ACTION-112 - Review profiling use-cases [on Karen Coyle - due 2018-05-16]. 06:20:20 rrsagent, make logs public 06:20:41 Jaroslav_Pullmann: need to review scenarios for profiles, to correlate with UCs. Also check GitHub issues. Perhaps generate UCs from issues? 06:21:01 Makx has joined #dxwg 06:21:15 present+ Makx 06:21:37 kcoyle: wants to go the other way - re-extract reqs from UCs - some Reqs do not appear to be well grounded in UCs 06:22:06 ... conceptually the Reqs do not reflect the UCs :-( 06:22:12 rrsagent, generate minutes v2 06:22:12 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html DaveBrowning 06:22:31 Action: Jaroslav_Pullmann to work with kcoyle on profile UCs and Requirements 06:22:36 Created ACTION-113 - Work with kcoyle on profile ucs and requirements [on Jaroslav Pullmann - due 2018-05-16]. 06:22:44 q+ 06:23:15 PWinstanley: We didn't pay much attention to content negotiation by profile 06:23:34 DCAT-AP scenario drives most of the requirements - and there are not that many additional ones. So if folks are uncomfortable with complexity, the re-read the real world examples provided by Makx - if something missing provide example as evidence. 06:23:42 AndreaPerego has joined #dxwg 06:23:51 s/the re-read/then re-read/ 06:23:54 present+ AndreaPerego 06:24:09 RRSAgent, draft minutes v2 06:24:09 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html AndreaPerego 06:24:09 kcoyle, Jaroslav_Pullmann : I have one case about links between profile I could work with you if you want 06:24:29 ack antoine 06:24:41 q? 06:24:43 PWinstanley: need to make sure nothing left on the editing floor 06:25:04 * just mute conference room when someone else taling please 06:26:42 ... kcoyle will give presentation on Dublin Core approach, to see if anything we can adopt from there 06:26:51 q+ 06:27:04 ... then going forward we can ensure our approach is harmonised with that 06:27:05 q+ 06:27:11 ack roba 06:28:23 roba: looking at comments from yesterday - too much focus on expressivity of constraint language :-( 06:29:03 we shouldn't be inventing a constraint language. We need to adopt technologies that are available. 06:29:18 For the record the questions I asked was whether we should include elements about the content of profile specifciation (cardinality constraints etc) like Dublin Core work in the "profile content" sections. 06:29:32 ack SimonCox 06:30:34 SimonCox: harmonization is good, but not if the DC approach is not fit for our purpose 06:30:45 q? 06:31:00 PWinstanley: agree - just avoid unnecessary divergence 06:31:06 q? 06:31:49 http://dublincore.org/documents/singapore-framework/ 06:32:07 present+ tombaker 06:32:09 RRSAgent, draft minutes v2 06:32:09 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html AndreaPerego 06:35:12 http://dublincore.org/documents/dc-dsp/ 06:37:19 http://dublincore.org/documents/profile-guidelines/ 06:38:04 kcoyle: describing DC profile approach 06:38:17 ... SHACL/ShEX are too atomistic 06:38:38 ... Singapore Framework documents too dense 06:38:58 s/Singapore/2007 Singapore/ 06:39:24 https://github.com/kcoyle/RDF-AP 06:39:33 ... 2009 draft http://dublincore.org/documents/profile-guidelines/ is clearer about how to develop profiles 06:40:19 ... new draft 2018 https://github.com/kcoyle/RDF-AP also based on CSV-W 06:40:42 ... everyone develops application profiles as tables 06:41:14 ... goal is simple enough documents so that all interested parties can use them 06:41:55 ... see schemaList.csv - could also link out to Shacl/ShEx for validation 06:42:34 ... but spreadsheet should express AP, then can build data template as a tables 06:43:10 ... Gregg Kellogg works on software for converting spreadsheets to web-friendly data 06:43:14 q+ 06:43:42 ack SimonCox 06:44:21 automatically convert constraints-in-a-table into data-template-as-a-table 06:44:28 ? 06:44:38 kcoyle: yes - though not working yet 06:45:17 PWinstanley: discussion? 06:46:59 seems to show that a diversity of implementing resources is a reality - challenge is classifying the role each resource may have.. 06:47:11 http://xlsform.org/ is a route to building forms that uses a spreadsheet approach 06:47:28 SimonCox: tabular representation of constraints is another useful prof:resource associated with a Profile 06:47:57 ... with different role - e.g. 'data-template-rule' 06:48:46 meeting: DXWG F2F3 - Day 2 06:48:48 RRSAgent, draft minutes v2 06:48:48 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html AndreaPerego 06:48:49 Data entry is important goal. Can also use SHACL to drive forms (NickCar student; built in to TopBraid) 06:51:38 discussion on how to move forward 06:51:47 PWinstanley: need someone to take control ... 06:52:05 kcoyle: wants in-out list - see gdoc 06:52:54 riccardoAlbertoni: do not enforce/adopt one technology 06:53:14 kcoyle: shoudl we mention technologies? 06:53:38 roba: document must explain what profiles are, and how data conforms 06:54:19 kcoyle: what should we say about constraints in the guidance document? 06:54:59 q+ 06:55:06 roba: how many documents: 1. guidance document ... but must refer to 2. profile description formalization 06:56:18 ... 'guidance for DCAT profiles' does not need to describe profiles technology or constraints languages, they belong in a different document 06:57:07 kcoyle: how many documents ? not yet clear. 06:57:46 roba: two options - one complex document or two simple documents 06:58:35 ... willing to write up profiledesc as separate standalone document, which then will make DCAT guidance easier, because it will provide means for describing more complex requirements 06:59:12 ... Nick and roba have implementation plans ready (OGC, Oz) independent ot DCAT 06:59:23 s/ot/of/ 06:59:45 +q 07:02:31 kcoyle: guidance dcument should not define a vocabulary, its a document 07:04:54 roba: profiledesc will make writing profile-guidance easier 07:05:10 kcoyle: profiledesc could be the main deliverable? 07:05:36 q- 07:06:23 q+ 07:06:45 SimonCox: note that profiledesc document is generated by LODE from profiledesc RDF - it doesn't have a lot of text 07:06:59 +1 07:07:12 (to peter's summary) 07:07:34 PWinstanley: will need to add lots of text 07:07:44 note that the vocabulary is completely open to change to meet needs 07:07:58 ?q 07:08:05 q? 07:08:10 q? 07:08:15 ack antoine 07:08:43 antoine: the proposal to work on profiledesc makes a lot of sense 07:09:01 ... but must not forget content-negotiation requirement 07:09:44 ... conneg is a separate deliverable 07:09:46 yet to identify a requirement to access profile description during negotiation - but possibly inheritance may raise an need 07:10:05 kcoyle: must be corodinated with profile guidance/profiledesc 07:10:20 antoine: deliverables must cross-reference each other 07:10:52 PWinstanley: delverable are independent must must be coordinated, there must be no inconsistency 07:11:07 Happy for this to be the formalism part of a single deliverable, which describes how to use it and show examples of what specific constraint languages are used 07:11:10 s/delverable/deliverables/ 07:11:37 q+ 07:12:05 q+ to ask if profiledesc vocabulary is one chapter/clause in the guidance document? 07:12:37 ack AndreaPerego 07:13:27 q+ 07:13:48 q+ to say that the profile description should have the same content as profiledesc but doesn't have to implement it 07:13:58 +q 07:13:58 AndreaPerego: need to be careful about rolling in too many things. there are other profiling formalisms. Users may be confused. How does this complement SHACL, ShEx etc? 07:14:13 Most profile languages like SHACL ShEx, DC's DSP seek to describe the content of profile (ie constraints). Our Vocabulary describe profiles. It gives the hook to bind everything together. 07:14:24 q- 07:14:29 +1 to what antoine just said 07:14:30 +1 antoine 07:14:42 +1 to antoine 07:14:51 ack roba 07:15:50 q- 07:15:55 roba: there is no profile description language around (there are several constraint languages, mostly tech specific) 07:16:06 And the role of content negotiation should be to point users to constraints languages (SHACL, XML Schema), humaan-readable doc (HTML) or the 'hook' as represented in ProfildDesc (RDF) 07:16:26 ack LarsG 07:16:26 LarsG, you wanted to say that the profile description should have the same content as profiledesc but doesn't have to implement it 07:16:46 s/ProfildDesc /ProfileDesc / 07:16:48 the hook also indicates role of different artefacts, which wasn't there before 07:17:04 SimonCox +1 and LarsG +1 07:17:12 +1 LarsG 07:17:19 yes - thats correct 07:17:20 q? 07:17:23 q+ 07:17:30 LarsG: profiledesc complements constraints expressions and guidance documents 07:17:32 q+ to say that http://dublincore.org/documents/singapore-framework/ also had the goal of specifying the documentary components of a profile and how they relate 07:18:15 ack kcoyle 07:18:36 so @tombaker - can DC work be refactored to use a simple vocab with this scope? 07:19:13 My proposal would be to have the profile guidance as a Primer for ProfileDesc 07:19:21 and for Conneg 07:19:25 kcoyle: proposes that we use profiledesc as basis for guidance document 07:19:31 +1 antoine 07:19:50 ... need to plan AP Guidance doc using profiledesc as core resource 07:19:51 I think it's compatible with what kcoyle proposes 07:20:43 antoine is that for profile-negotiation or for how to distribute information about a specific profile? 07:21:14 PWinstanley: need to roadtest profiledesc 07:21:18 Suggested title: "Describing and publishing data profiles - a Primer" :-) 07:21:18 q+ to say it would be good to integrate also the draft made by antoine - https://docs.google.com/drawings/d/1dHkpwKwUwMgS1RqSCTPO3uOoRiY_qNk0z5bhXJlYi4Y/edit 07:21:24 it still needs work of course - role description and can we handle all the versioning complexity Makx highlighted? 07:21:36 LarsG: both 07:21:39 ack tombaker 07:21:39 tombaker, you wanted to say that http://dublincore.org/documents/singapore-framework/ also had the goal of specifying the documentary components of a profile and how they relate 07:22:29 Description of profiledesc is here https://w3c.github.io/dxwg/profiledesc/profiledesc.html 07:23:01 examples here: https://github.com/w3c/dxwg/tree/gh-pages/profiledesc/examples 07:23:44 Can we get some love to test profiledesc against singaporeframework requirements 07:23:51 tombaker: Singapore Framework (3 page doc) is important well-used resource, perhaps needs updating, coordinating 07:26:05 q? 07:26:16 q+ 07:26:43 q+ to propose that we combine the documentation part of the Singapore Framework with the structure of profileDesc 07:28:15 q+ to suggest we really need to set up a profile group to coordinate between the 3 deliverables 07:28:31 ack AndreaPerego 07:28:31 AndreaPerego, you wanted to say it would be good to integrate also the draft made by antoine - https://docs.google.com/drawings/d/1dHkpwKwUwMgS1RqSCTPO3uOoRiY_qNk0z5bhXJlYi4Y/edit 07:28:47 ack roba 07:28:51 SimonCox: urges people to review profiledesc resources mentioned above 07:29:25 * was trying to work out f just me... 07:30:23 roba: profiledesc meets operational needs known to the authors - several tests have been done 07:30:44 ... shoudl be crossed-checked against SF (Singapore Framework) 07:31:07 ... profiledesc is currently v small and could be evolved and aligned quite easily 07:31:10 ack LarsG 07:31:10 LarsG, you wanted to propose that we combine the documentation part of the Singapore Framework with the structure of profileDesc 07:31:16 Do we need more use cases to cover profiledesc? 07:31:22 LarsG: +1 to roba 07:31:26 ack antoine 07:31:26 antoine, you wanted to suggest we really need to set up a profile group to coordinate between the 3 deliverables 07:31:47 antoine: we agree on strategy, need to organize the work. 07:32:13 PROPOSED: Explore placing ProfileDesc as basis for Guidance deliverable 07:32:25 +1 07:32:29 +1 07:32:29 +1 07:32:30 +1 07:32:31 +1 07:32:32 +1 07:32:32 +1 07:32:33 +1 07:32:33 +1 07:32:57 +1 (with hesitation: I think it would be not *the* basis) 07:33:15 +1 07:33:19 resolved: we will explore placing ProfileDesc as a basis for Guidance deliverable 07:33:35 RESOLVED: Explore placing ProfileDesc as basis for Guidance deliverable 07:33:49 RRSAgent, draft minutes v2 07:33:49 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html AndreaPerego 07:34:00 4 months should be ok 07:34:06 PWinstanley: logistics - timing? 07:34:11 looking at the maturity for the rest 07:34:43 ... well before TPAC, Lyon October 25/6 07:34:56 ... so needs to be well underway by August 07:35:09 yes it's possible 07:35:28 ... so as not to clash with lazy northern summer 07:35:39 q+ 07:35:46 ... (excepting kcoyle of course) 07:36:13 q+ 07:36:31 q- 07:36:57 ... FPWD needs to show sense of direction. RobA, kcoyle Nick all champing at the bit 07:37:07 ... probably antoine too 07:37:38 ack antoine 07:38:03 ... (we are talking about potential editors here) 07:38:24 antoine: will ensure that conneg will be included 07:38:37 LarsG: what about previously nominated editors? 07:39:05 PWinstanley: roba has been v active, but not on profile/index.html 07:39:35 I can help co-editing stuff especially taking care of interrelationships and the wording that goes with it. 07:39:39 once scope is clear and contributions start then editing can start :-) Ready to go.. 07:40:30 Editors: kcoyle roba antoine (for now) 07:41:18 RRSAgent, draft minutes v2 07:41:18 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html AndreaPerego 07:41:26 coffee calls 07:41:31 I'm expecting that in the end we could have more editors, as I expect we'll pick contributions from Lars, Ruben, Nick about their 'products' 07:41:43 +1 antoine 07:41:57 and probably SimonCox too ;-) 07:42:35 q? 07:42:58 DaveBrowning: is this still a 'guidance' document 07:43:16 kcoyle: description is vague, can be bent to fit 07:43:32 ... phila encouraged us to take it in the direction required 07:43:47 PWinstanley: establish a position! 07:44:44 DaveBrowning: balance guidance vs. authoritative slant 07:45:01 ... we (Reuters) struggle with the balance 07:45:12 PWinstanley: DaveBrowning should be strong reviewer 07:45:38 q+ 07:45:47 LarsG: does profiledesc replace ruben/lars/roba document? 07:46:08 PWinstanley: need to verify that profiledesc-based work is sound 07:46:20 aiming for rec track - i need to implement at OGC Linked Data resources in next few months :-) 07:46:20 +1 to what PWinstanley said. Let's start with doing something then we see the formal status 07:46:27 ... need to bring forward milestones to verify quality 07:46:40 which probably means that we're aiming at Note first... 07:46:52 q- 07:47:07 let it emerge - buts its a very tiny little vocab .. 07:47:15 s/coffee calls// 07:47:49 * how long? 07:48:02 20 minutes or so? 07:48:07 * ok 07:48:19 we'll try to get back top of the hour 07:48:28 s/20 minutes or so?// 07:48:40 scribenick: AndreaPerego 07:48:49 [coffee break] 07:48:52 RRSAgent, draft minutes v2 07:48:52 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html AndreaPerego 08:04:59 topic: Project plan for the profile guidance doc 08:05:35 https://docs.google.com/document/d/15OfNXU9AJ-cZysc7uYP-Gks5dDa8n2B5IN6rWa3kRpo/edit# 08:05:41 PWinstanley: We need to decide all the bits - location of the doc and all the ingredients 08:06:15 kcoyle: Starting with the pre-requisites 08:07:05 kcoyle: [editing the google doc] 08:08:47 kcoyle: We need a project plan so we can determine what we can do. 08:09:09 ... Let's call it for the moment "guidance doc" but it may be called otherwise. 08:15:05 kcoyle: Given the idea of creating the doc around the profile desc voc, we need to follow the W3C process - which includes UCs + Reqs 08:15:37 ... Jaroslav_Pullmann and I will re-derive reqs from UCs, and compare them with the profile desc, and see if anything is missing (new UCs). 08:16:09 ... So we probably need to get UCs from Rob and Nick. 08:16:24 we need to set the github space 08:16:27 kcoyle: We need also to form the group + chairs. 08:16:47 PWinstanley: We also need a clear indication of the working space. 08:16:58 I can create github 'milestones' for the 3 deliverables. 08:17:08 kcoyle: So we need to decide whether or not to re-use the original space for the profile guidance doc. 08:17:40 PWinstanley: We need also to start our engagement with stakeholders - the wider community. 08:18:20 ... We should avoid what happened so far - very low engagement and feedback. 08:18:32 kcoyle: We also need to set the milestones. 08:18:41 PWinstanley: And a review process. 08:19:06 ... For efficiency, this needs to be coordinated. 08:19:47 ... Ensure quick feedback (couple of days). 08:20:00 q+ 08:20:05 q- 08:20:55 ... Note also that the stakeholders may be different from the ones of DCAT - scope of the profile document is broader than DCAT. 08:21:17 q+ 08:21:27 ack antoine 08:22:19 antoine: There was a discussion on the moderation of the comment list - so messages are not passing through directly. 08:22:45 kcoyle: We need DaveRaggett to dig deeply into it. 08:23:38 kcoyle: FPWD around early August. 08:24:17 kcoyle: Looking at how the profile desc relates to conneg is another point. 08:24:32 q+ 08:24:50 kcoyle: Who's going to do that and when? 08:25:20 LarsG: I can do that. June/July may be feasible to me. 08:25:39 kcoyle: Should this be separate from the group? 08:26:04 LarsG: I can join the group, but I'll be away for 2 months. 08:26:23 ack roba 08:27:19 roba: One of the things that needs to be checked is whether conneg requires anything on the side of profile desc. 08:28:09 * +1 08:28:20 +1 08:28:24 q+ 08:28:37 LarsG: May be worth you roba do the coordination with the conneg group. 08:28:46 roba: [agrees] 08:28:56 ack antoine 08:29:20 antoine: I wonder whether we should merge the groups... 08:29:52 seem to be quite different activities to me .. 08:29:59 kcoyle: I feel they are 2 different activities, although dependent to each other, so merging them could be an option. 08:30:12 antoine: We can discuss this in a later stage. 08:30:37 kcoyle: Anything else we should add to the project plan? 08:31:37 PWinstanley: We need a definitive version of profile desc and comparison with existing alternative approaches. 08:32:15 How does this github milestone look? https://github.com/w3c/dxwg/milestone/9 08:32:25 ... This should go in the pre-requisites. It's about a definitive version of the vocs we are going to refer to. 08:33:31 roba: We do need some feedback for consolidating it. 08:33:59 I've just created it 08:34:34 was there another one on Profile Desc? 08:34:46 also https://github.com/w3c/dxwg/projects/2 08:35:10 kcoyle: Thanks for creating that milestone, antoine. 08:36:24 SimonCox a kanban board looks great indeed! We'll have to see what is best (a kanban for all profile-related issues could be lot) 08:36:42 LarsG: [noting he posted some questions on profile desc that were not answered] 08:37:02 projects should help - i tried to respond to all issues I saw related - but may have missed some :-( 08:37:04 199? 08:37:52 kcoyle: About the doc outline, I will check other W3C docs. 08:37:54 ahh - yes thats a nick use case - will chase him for a response 08:37:56 riccardoAlbertoni has joined #dxwg 08:38:08 present+ 08:38:38 ... like definition of terms, what the document will cover... 08:39:03 q+ 08:39:12 riccardoAlbertoni: Maybe an introduction about the conceptual model behind it? 08:39:28 +1 08:39:36 kcoyle: Can we use DCAT and DCAT-AP as examples. 08:40:08 https://joinup.ec.europa.eu/solution/core-public-service-vocabulary-application-profile 08:40:08 we already use DCAT=AP as an example - but would be great to have Makx et al complete and clean these examples. 08:40:12 PWinstanley: Also the ISA Core Public Service vocabulary AP can be an option. 08:40:40 DaveBrowning: ODRL is another one. 08:41:35 ... They provide a meta-model, the provide support for extensions, ... 08:41:57 using prov for DCAT-AP versioning and profile activities is great - maybe profiles are in fact sub types of prov:Entity 08:42:13 SimonCox: [explaining the use of PROV in a similar way for describing projects] 08:42:19 ack roba 08:44:30 roba: What we need in the examples is to describe the roles, and decide whether they should be skos:Concept's / skos:ConceptScheme's or subclasses. 08:44:46 I'd be happy to work on SKOS :-) 08:44:53 q+ 08:45:29 Not quite sure what you're asking me to do 08:45:49 currently separate artefact - but aligning with prov may be a good idea? 08:46:45 AndreaPerego: Maybe also the PROV approach can be an example of building profiles - PROV is very generic, and they tell people that to do some more specific things you can create individuals / subclasses. 08:46:48 @roba maybe you can explain a bit what you would expect in e-mail? 08:46:48 @Makx - look at DCAT-AP examples - create a separate file and try to describe all the DCAT-AP metadata you feel is necessaru - and revert back to group with questions as required. 08:46:49 q? 08:47:02 ack AndreaPerego 08:47:28 @roba where are the DCAT-AP examples? 08:47:38 kcoyle: We need also clarify the notions of profile / application profiles / metadata application profiles 08:47:52 riccardoAlbertoni: The conceptual model can be useful to address this. 08:48:01 kcoyle: Do we have a conceptual model? 08:48:13 @antoine - do you see class/concept duality (concepts that may have further semantics modelled as classes?) 08:48:46 riccardoAlbertoni: The work done in the Singapore framework, the profile desc and antoine's diagram, put together can be the basis for that model. 08:49:11 +1 - its just a subset of the singapore framework model 08:49:19 @roba - it is doable but if there's a way to avoid it it's maybe better (and not only for OWL2-DL concerns) 08:49:33 +1 riccardoAlbertoni 08:49:54 ... There's also an example from DQV: generic classes and examples on how to use them by creating individuals / subclasses. 08:50:35 @antoine - hard-typing vs soft-typing is a pattern that exists in the real world 08:50:43 q? 08:50:50 kcoyle: Should we also talk about how people define profiles? From documents to code to validation 08:51:43 all: [general agreement] 08:53:01 PWinstanley: It may be worth to talk also about how they support communities, which are their functions (implementing consensus, data sharing) 08:54:25 ... Looking at the DCAT-AP example, they provide a collaborative framework ending up in domain-specific and/or country-specific extensions. 08:55:21 kcoyle: It seems that we can come up with quite a substantial document. 08:56:40 * internet issues 08:56:58 ... But now it looks difficult to see where profile desc fits in. 08:58:06 +1 for what PWinstanley it's a harness/hub 09:00:48 all: [discussion on notion of profile and role of profile desc] 09:01:14 PWinstanley: The starting point is to say what a profile is. 09:01:48 q? 09:01:52 kcoyle: We want to help people build profiles in their environment. 09:01:55 roba_ has joined #dxwg 09:02:53 guidance is that you should describe how your profile relates to other standards and what the artefacts do.. using profiledesc if you are in an RDF context 09:03:56 RRSAgent, draft minutes v2 09:03:56 I have made the request to generate https://www.w3.org/2018/05/09-dxwg-minutes.html AndreaPerego 09:04:24 q+ 09:04:50 kcoyle: We are not going deeply on how to do things 09:05:17 PWinstanley: Agreed, this is actually not possible - there are different ways of doing that, each with their requirements. 09:05:45