Meetings:Telecon2018.06.19

Agenda Tuesday 19 June 2018 20:00 UTC (in your time zone)

Chair: Karen Coyle

Regrets: Antoine

Reminding attendees to put Present+ <nickname>

I. Appoint Scribe

III. Check who is on IRC and WebEx

From last week:

Requirement: There needs to be a property in the profile where the rules for the descriptive content can be provided. This would apply to the entire profile. [ID42] (5.42) (github)

For Approval (Profiles):

Representation and distribution

Requirement: Profiles may be written in or may link to a validation language (ShEx, SHACL, XMLschema). ID41 (5.41) [profile]
Requirement: Profiles may be coordinated with validation schemas. ID48 (5.48) [profile]

Identification, versioning, linking and resolution

Requirement: profiles must have identifiers that can be served with a response to an API or http request. ID2 (5.2) [conneg]

Querying and discovery

Requirement: Clients should be able to determine which profiles are supported by a server, and with which content types. ID2 (5.2) [conneg]
Requirement: There should be a way for a client to look up additional information about a profile. (What kinds of information? Can we clarify this?) ID2 (5.2) [conneg]
Requirement: Profiles offered by a service must be discoverable through a machine-readable graph of metadata that describes what is offered and how to invoke the offered profiles. ID5 (5.5) [conneg]
Requirement: Profiles must support discoverability via search engines (UC 5.40) #222 (Github discussion) ID40 (5.40) [profile]

Reuse, composition, and compatibility

Requirement: Profiles can be modular, with a given response made up of more than one module. Servers can indicate that a response conforms to multiple, modular profiles. ID3 (5.3) [conneg] [profile]

Inheritance, conflict resolution and evaluation

Requirement: "Profiles may add to or specialise clauses from one or more base specifications. Such profiles inherit all the constraints from base specifications.” ID37 [ID39] #238

Europeana Use Case: Requirements for Profiles

See: ID37. Use case is greatly edited, new requirements replace requirement 12.:

12.1 Requirement: a vocabulary or data model can be a profile of several other vocabularies or data models at once
12.2 Requirement [derived from the previous one: it's rather trivial, but one never knows…]: profiles may or may not be "exclusive" of other profiles, i.e. some profiles may forbid the use of their elements in combination of other profiles, while others (in a typical open-world fashion) will allow such combined use.
12.3 Requirement: one can create profiles of profiles, with elements (constructs, axioms…) potentially inherited on several levels.
12.4 Requirement: from the perspective of management of profiles, and guidance to users and data experts, ecosystems of profiles should be properly described (e.g. in profile catalogues/repositories), especially documenting the relationships between profiles and what they are based on, and between profiles that are based on other profiles.
12.5 Requirement: a profile may be "implemented" by "schemas" (in OWL, SHACL, XML Schema...) that allow different levels of data validation.
12.6 Requirement: data publishers may publish data according to different profiles, either simultaneously (in one same data "distribution") or in parallel (via content negotiation).

Proposed new use cases

Still needed?

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)