Meetings:Telecon2018.07.31
Agenda Tuesday 31 July 2018 20:00 UTC (in your time zone)
Admin
Chair: Karen Coyle
Regrets: Simon Cox, LarsG
Reminding attendees to put Present+ <nickname>
I. Appoint Scribe
II. Approve July 24 meeting minutes
III. Check who is on IRC and WebEx
IV. Reminder about registration for TPAC (early bird rates)
Checking Open Action items
DCAT-rev
- Subgroup report
- Responses to FPWD? Contacts list
Profile Guidance group
- subgroup report
- documentation of profile description
- Request (NC): can Requirements be moved from GDoc to GitHub?
- all items in the GDoc have had GitHub issues created and the doc has been annotated with them
- labeling of the issues has occurred and sorting queries placed in the GDoc
Profile Negotiation
- subgroup report
UCR
Requirements must be approved for Conneg and Profiles
Europeana Use Case: Requirements for Profiles
See: ID37. Use case is greatly edited, new requirements replace requirement 12.:
- 12.6 Requirement: a profile may be (partially) "implemented" by "schemas" (in OWL, SHACL, XML Schema...) that allow different levels of data validation.
- 12.7 Requirement: data publishers may publish data according to different profiles, either simultaneously (in one same data "distribution") or in parallel (via content negotiation).
- ["Virtual" requirement: from the EDM profile(s) it should be possible to infer specific requirements in terms of data validation: this is probably out of scope of DXWG now, but we've done it for the DCMI WG that Karen and I co-chaired. It should also be possible to derive requirement in terms of description of profiles vs their implementations/schemas and how all this should be served. Now I see that there are some requirements like "Profiles are "named collections of properties" or metadata terms (if not RDF)", "Profiles may provide rules on cardinality of terms (including “recommended”)", "Profiles may provide rules governing value validity" "Profiles may express dependencies between elements of the vocabulary (if A then not B, etc.)" that go in this direction already. But I lack time and am hoping this will be captured by other cases, or will be addressed at a later stage of DXWG work]
Note: Conneg group should review conneg requirements; see if profileDesc functionality and conneg are adequately covered
In the queue
Proposed new use cases
- Use case: web browser navigation of profile information #239
- Use Case: Profiles of DCAT-AP and various implementation resources
- Additional Use Case on Real World Objects (J Pullmann)
Still needed?
- Agentschap Informatie Vlaanderen provided use case - other resource types
- Modeling permissions new use case proposed
Joining instructions: (official participants and invited guests only)
WebEx Details
For text discussions, minutes, joining the speaker queue, actions & issues IRC channel: #dxwg on IRC on port 6667
Please be sure to join both IRC and WebEx and use the same nick in both (or it gets very confusing)
When you join the IRC channel, please immediately type 'present+ {yourname}' (this adds your name to the participants list in the minutes)
Annotations
- Telecon
- Profiles Requirements
- 2018-07-31
- https://www.w3.org/2018/07/31-dxwg-minutes
- Rob Sanderson (azaroth)