Saturday, 30 June 2018
- Closing requirement issues on github?
- Closed: [dxwg] Profiles SHOULD have both both machine and human-readable views. (6.1)
- Re: [dxwg] Profiles have URI identifiers that resolve to more detailed descriptions (6.1)
- Closed: [dxwg] 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)
- Poll for new time for the CNEG meeting
Friday, 29 June 2018
Thursday, 28 June 2018
- Re: New requirements on github?
- Re: ODRL community group - and profiles
- Re: Initial notes on profileDesc
- Re: New requirements on github?
- DCMI/ASIS&T Webinar slides on profiles
- Re: [DCAT] group meeting 2018-06-28
- Re: [dxwg] Profile Composition and Languages
- New requirements on github?
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] How to express distributions provided as compressed files
- [DCAT] group meeting 2018-06-28
- Re: In DCAT, Is is possible to specify an void:rootResource in DCAT?
- [dxwg] Add void:rootResource as property of dcat:Resource ?
- Re: [dxwg] Related datasets [RRDS]
- Re: [dxwg] Catalogues in which dataset is a bag of files
- dxwg-ACTION-138: Trigger feedback from ANDS
- dxwg-ACTION-137: Add some notes into https://â??github.com/â??w3c/â??dxwg/â??issues/â??259 about our discussion
- dxwg-ACTION-136: Create issue from mailing list comment
- dxwg-ACTION-135: Acknowledge comment
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] Catalogues in which dataset is a bag of files
- [dxwg] Pull Request: Remove minor nits left behind in copy-and-paste
- [dxwg] Pull Request: Remove minor nits left behind in copy-and-paste
Wednesday, 27 June 2018
- Re: [DCAT] team meeting 2018-06-28 - Agenda
- [DCAT] team meeting 2018-06-28 - Agenda
- Re: [dxwg] Requirement: Profiles can have what is needed to drive forms for data input or for user display. [ID46] (5.46)
- Re: [dxwg] Requirement: Profiles should be able to indicate what external standards are expected to be applied/have been applied to the data provided.[ID43] (5.43)
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] Requirement: There needs to be metadata about the views provided by profiles (“named collections of properties”) that can included in a http header [ID5] (5.5)
- [dxwg] Requirement: There needs to be metadata about the views provided by profiles (“named collections of properties”) that can included in a http header [ID5] (5.5)
- [dxwg] Requirement: Invocation of a profile may be by profile name, a schema choice, an encoding, and/or a language. (schema? And assume that encoding is type as in type="application/xml".) [ID5] (5.5)
- [dxwg] Requirement: a 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)
- Re: [dxwg] Requirement: A profile can be modular, with a given response made up of more than one module. A server can indicate that a response conforms to multiple, modular profiles. [ID3] (5.3)
- [dxwg] Requirement: A profile can be modular, with a given response made up of more than one module. A server can indicate that a response conforms to multiple, modular profiles. [ID3] (5.3)
- [dxwg] 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)
- [dxwg] Requirement: a client should be able to determine which profiles are supported by a server, and with which content types or other properties, in order to receive the one most appropriate for their use.
- [dxwg] Requirement: a profile must have an identifier that can be served with a response to an API or http request. [ID2] (5.2)
- [dxwg] Requirement: Profiles can have human-readable definitions of terms and input instructions [ID46] (5.46)
- [dxwg] Requirement: Profiles may provide lists of values to pick from in order to populate data elements [id46] (5.46)
- [dxwg] Requirement: Profiles can have what is needed to drive forms for data input or for user display. [ID46] (5.46)
- [dxwg] Requirement: Profiles should be able to indicate what external standards are expected to be applied/have been applied to the data provided.[ID43] (5.43)
- [dxwg] Requirement: Profiles may be written in or may link to a document or schema in a validation language (ShEx, SHACL, XMLschema). [ID41] (5.41)
- [dxwg] Requirement: Profiles may express dependencies between elements of the vocabulary (if A then not B, etc.) [ID41] (5.41)
- [dxwg] Requirement: Profiles may provide rules governing value validity [ID41] (5.41)
- [dxwg] Requirement: Profiles may provide rules on cardinality of terms (including “recommended”) [ID41] (5.41)
- [dxwg] Requirement: Profiles are "named collections of properties" or metadata terms (if not RDF) [ID41] (5.41)
- [dxwg] Requirement: data publishers may publish data according to different profiles, either simultaneously (in one same data "distribution") or in parallel (via content negotiation).
- [dxwg] Requirement: a profile may be (partially) "implemented" by "schemas" (in OWL, SHACL, XML Schema...) that allow different levels of data validation
- [dxwg] Requirement: a profile should have human-readable documentation that expresses for humans the main components of a profile, which can also be available as machine-readable resources (ontology or schema files, SHACL files, etc). This includes listing of elements in the profile, instructions and recommendations on how to use them, constraints that determine what data is valid according to the profile, etc.
- [dxwg] 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.
- [dxwg] Requirement: one can create a profile of profiles, with elements (constructs, axioms…) potentially inherited on several levels
- [dxwg] 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.
- [dxwg] Requirement: a vocabulary or data model can be a profile of several other vocabularies or data models at once
- [dxwg] Requirement: there is a need to distinguish between distributions that package the entire dataset and those that support access to specific items, queries, and packaged downloads of data. [ID51] (5.51)
- Re: [dxwg] Requirement: Return http link headers using the following relationship types... [ID30] (5.30)
- [dxwg] Requirement: Return http link headers using the following relationship types... [ID30] (5.30)
- [dxwg] Requirement: Enable the ability to negotiate the metadata profile via http, similar to the negotiation of metadata formats today. [ID30] (5.30)
- [dxwg] Requirement: Metadata about server profile support can be used for discovery and mediated traversal via content negotiation. [ID5] (5.5)
Tuesday, 26 June 2018
- Re: [dxwg] Define conneg interaction with media types that have a profile param
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] Define conneg interaction with media types that have a profile param
- RE: ODRL community group - and profiles
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] 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)
- Re: ODRL community group - and profiles
- Re: Agenda June 26
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] How to express distributions provided as compressed files
- Re: ODRL community group - and profiles
- RE: ODRL community group - and profiles
- Re: ODRL community group - and profiles
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] DCAT - DATS alignment (profile)
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] Define conneg interaction with media types that have a profile param
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] DCAT - CERIF alignment (profile)
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] Entailment of schema.org [RES]
- Re: [dxwg] further PROV alignment, including for mooted WebService class
- RE: ODRL community group - and profiles
- Agenda June 26
Monday, 25 June 2018
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] further PROV alignment, including for mooted WebService class
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] further PROV alignment, including for mooted WebService class
- Re: [dxwg] [profiledesc] role assumes closed world of the document
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] Define conneg interaction with media types that have a profile param
- Re: [dxwg] further PROV alignment, including for mooted WebService class
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] [conneg] IETF submission must not include query param pattern requirements
- Re: [dxwg] further PROV alignment, including for mooted WebService class
- [dxwg] [conneg] IETF submission must not include query param pattern requirements
- [dxwg] [profiledesc] role assumes closed world of the document
- Re: [dxwg] Define conneg interaction with media types that have a profile param
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] Profile Composition and Languages
- [dxwg] new commits pushed by nicholascar
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Define conneg interaction with media types that have a profile param
- ODRL community group - and profiles
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] A profile must be packaged as a self-contained artefact
- Re: Content Negotiation subgroup meetings (RE: Introduction - Rob Sanderson, J Paul Getty TrustI
- Re: [dxwg] How to express distributions provided as compressed files
Sunday, 24 June 2018
- Re: [dxwg] A profile must be packaged as a self-contained artefact
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] A profile must be packaged as a self-contained artefact
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] A profile must be packaged as a self-contained artefact
Saturday, 23 June 2018
- Re: [dxwg] A profile must be packaged as a self-contained artefact
- Re: [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] Qualified forms [RQF]
- Re: [dxwg] Qualified forms [RQF]
Friday, 22 June 2018
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] dcat:mediaType - check constraints
- [dxwg] Define conneg interaction with media types that have a profile param
- Re: [dxwg] A profile must be packaged as a self-contained artefact
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Requirement: A profile can be modular, with a given response made up of more than one module. A server can indicate that a response conforms to multiple, modular profiles
- Re: [dxwg] Profile Composition and Languages
- [dxwg] Pull Request: further PROV alignment, including for mooted WebService class
- [dxwg] How to express distributions provided as compressed files
- Re: [dxwg] dcat:mediaType - check constraints
- RE: Minutes from the CNEG meeting 2018-06-20
- [dxwg] Requirement: A profile can be modular, with a given response made up of more than one module. A server can indicate that a response conforms to multiple, modular profiles
- Re: [dxwg] 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)
- RE: Content Negotiation subgroup meetings (RE: Introduction - Rob Sanderson, J Paul Getty TrustI
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] A profile must be packaged as a self-contained artefact
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Profiles must support discoverability via search engines (UC 5.40)
- Re: [dxwg] Entailment of schema.org [RES]
- Re: [dxwg] Profiles must support discoverability via search engines (UC 5.40)
- Re: Minutes from the CNEG meeting 2018-06-20
Thursday, 21 June 2018
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profiles listing [RPFL]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] A profile must be packaged as a self-contained artefact
- Re: [dxwg] Responses can conform to multiple, modular profiles (UC 5.3)
- Re: [dxwg] Profiles should provide both machine and human readable views (6.1)
- Re: [dxwg] Profiles must support declaration of vocabulary constraints (6.1)
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] A profile must be packaged as a self-contained artefact
- Re: [dxwg] Responses can conform to multiple, modular profiles (UC 5.3)
- Re: [dxwg] Profiles should provide both machine and human readable views (6.1)
- Re: [dxwg] Profiles must support declaration of vocabulary constraints (6.1)
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Profile Composition and Languages
- Re: [dxwg] Usage notes [RUN]
- Re: [dxwg] Provenance information [RPIF]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profiles listing [RPFL]
- Re: [dxwg] Entailment of schema.org [RES]
- RE: Media Types URIs
- Re: Content Negotiation subgroup meetings (RE: Introduction - Rob Sanderson, J Paul Getty TrustI
- Use case/requirement ID40
- Re: Minutes from the CNEG meeting 2018-06-20
- Fwd: Publication moratoria for second half of 2018
- DCAT sub-group meeting 2018-06-21
- Minutes from the CNEG meeting 2018-06-20
- dxwg-ACTION-134: Draft some text about the drivers for DCAT
- RE: Meeting details for the CNEG subgroup meeting on Wednesday, June 20
- Re: Media Types URIs
Wednesday, 20 June 2018
- List of proposed new use cases
- RE: Media Types URIs
- Re: [dxwg] 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)
- Re: Meeting details for the CNEG subgroup meeting on Wednesday, June 20
- Re: [dxwg] DCAT - LDP (Linked Data Platform) alignment
- [dxwg] new commits pushed by davebrowning
- [DCAT] Telecon2018.06.21 - Proposed agenda
- dxwg-ACTION-133: Report back progress to plenary.
- dxwg-ACTION-132: Report back this expectation to plenary (accepting in the plenary meeting will generate action to generation pr against ucr)
- dxwg-ACTION-131: Report back this expectation to plenary (accepting in the plenary meeting will generate action to generation pr against ucr)
- RE: Meeting details for the CNEG subgroup meeting on Wednesday, June 20
- [dxwg] Pull Request: Add description of relation to LDP and LDN
- Content Negotiation subgroup meetings (RE: Introduction - Rob Sanderson, J Paul Getty TrustI
- Re: Meeting details for the CNEG subgroup meeting on Wednesday, June 20
Tuesday, 19 June 2018
- Re: Meeting details for the CNEG subgroup meeting on Wednesday, June 20
- Introduction - Rob Sanderson, J Paul Getty Trust
- Was this Use Case ever accepted?
- New use-case - Catalogues in which dataset is a bag of files
- [dxwg] new commits pushed by agbeltran
- [dxwg] new commits pushed by agbeltran
- Re: [dxwg] Best practice for a loosely-structured catalog
- Re: [dxwg] Catalogues in which dataset is a bag of files
- [dxwg] Catalogues in which dataset is a bag of files
- Re: [dxwg] 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)
- Re: [dxwg] 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)
- Re: Agenda Tuesday 19 June
- Re: [dxwg] Profile negotiation [RPFN]
- RE: [ExternalEmail] Media Types URIs - profileneg - lang
Monday, 18 June 2018
- Re: Media Types URIs
- Re: [ExternalEmail] Media Types URIs - profileneg
- Re: Media Types URIs
- Re: Media Types URIs
- Media Types URIs
- Updates to G-Doc
- Re: Agenda Tuesday 19 June
- Agenda Tuesday 19 June
Saturday, 16 June 2018
- Re: Meeting details for the CNEG subgroup meeting on Wednesday, June 20
- Meeting details for the CNEG subgroup meeting on Wednesday, June 20
Thursday, 14 June 2018
- Fwd: TPAC 2018 registration now open
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Allow license property to link to other than LicenseDocument
- TPAC 2018 registration now open
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- DCAT sub-group meeting 208-06-14
- Closed: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] dcat:accessURL - check constraints
- Re: [dxwg] dcat:downloadURL - check constraints
- Re: [dxwg] Quality-related information [RDQIF]
- Closed: [dxwg] Quality-related information [RDQIF]
- Re: [dxwg] Quality-related information [RDQIF]
Wednesday, 13 June 2018
- Re: dxwg-ACTION-130: Create github issue for id42
- Re: [dxwg] Revision to UC19
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] DCAT - LDP (Linked Data Platform) alignment
- Re: [dxwg] Profile negotiation [RPFN]
- RE: [DCAT] Telecon2018.06.14 - Dataset Exchange Working Group
- [DCAT] Telecon2018.06.14 - Dataset Exchange Working Group
- Re: [dxwg] DCAT - LDP (Linked Data Platform) alignment
- Re: [dxwg] DCAT - LDP (Linked Data Platform) alignment
- Re: [dxwg] DCAT - LDP (Linked Data Platform) alignment
- Re: [dxwg] Datasets vs. Catalog relation [RDSCR]
- Re: [dxwg] Adding dct:accessRights to DCAT
- Re: [dxwg] Best practice for a loosely-structured catalog
- Re: [dxwg] Adding dct:accessRights to DCAT
- Re: [dxwg] Revision to UC19
Tuesday, 12 June 2018
- [dxwg] 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)
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- dxwg-ACTION-130: Create github issue for id42
- Re: [dxwg] Profile negotiation [RPFN]
- dxwg-ACTION-129: Create new use case and requirements for more complex situation
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Datasets vs. Catalog relation [RDSCR]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Best practice for a loosely-structured catalog
- Re: [dxwg] Best practice for a loosely-structured catalog
- Re: [dxwg] DCAT - LDP (Linked Data Platform) alignment
- Re: [dxwg] Profile negotiation [RPFN]
Monday, 11 June 2018
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Datasets vs. Catalog relation [RDSCR]
- Re: [dxwg] Adding dct:accessRights to DCAT
- [dxwg] DCAT - LDP (Linked Data Platform) alignment
- Re: [dxwg] Adding dct:accessRights to DCAT
- [dxwg] Best practice for a loosely-structured catalog
Sunday, 10 June 2018
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- Re: DCAT-rev as First Public Working Draft
- [dxwg] new commits pushed by agbeltran
Saturday, 9 June 2018
Friday, 8 June 2018
- RE: Best practice for a loosely-structured catalog?
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- Re: [dxwg] Profile negotiation [RPFN]
- [dxwg] Examples of quality for services
- RE: Best practice for a loosely-structured catalog?
- RE: Best practice for a loosely-structured catalog?
- Re: Best practice for a loosely-structured catalog?
- Re: [dxwg] Extending DCAT for services
- [dxwg] new commits pushed by dr-shorthair
- [dxwg] new commits pushed by dr-shorthair
- Re: [dxwg] Remove one instance of "government"
- Re: [dxwg] Add Czech translation to dcat.ttl
- Best practice for a loosely-structured catalog?
Thursday, 7 June 2018
- Re: [dxwg] Profile negotiation [RPFN]
- Re: ACTION-128: Re-write requirement: profiles should be able to indicate what external standards are expected to be applied to the data provided. [id42, id43] (5.42, 5.43) [profile] (Dataset Exchange Working Group)
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] dcat:accessURL - check constraints
- Re: [dxwg] DCAT - schema.org alignment (profile)
- [dxwg] DCAT - schema.org alignment (profile)
Wednesday, 6 June 2018
- RE: [DCAT] - Draft agenda telecon 2018-06-07
- RE: [DCAT] - Draft agenda telecon 2018-06-07
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- Re: [dxwg] Profile negotiation [RPFN]
- [DCAT] - Draft agenda telecon 2018-06-07
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] Extending DCAT for services
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
Tuesday, 5 June 2018
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- Re: [dxwg] Added a section to deal with quality and started some guidance for r…
- [dxwg] new commits pushed by dr-shorthair
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: ACTION-127: Re-write requirement from id46 "profiles can have rules for data value validation, including pick lists [id46] (5.46) [profile]" (Dataset Exchange Working Group)
- dxwg-ACTION-128: Re-write requirement: profiles should be able to indicate what external standards are expected to be applied to the data provided. [id42, id43] (5.42, 5.43) [profile]
- dxwg-ACTION-127: Re-write requirement from id46 "profiles can have rules for data value validation, including pick lists [id46] (5.46) [profile]"
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- Re: [dxwg] Profile negotiation [RPFN]
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- Re: [dxwg] Profile negotiation [RPFN]
- Re: ACTION-120: Add requirements to the europeana use case (Dataset Exchange Working Group)
- Re: ACTION-126: Prepare a proposal for issue 57 about quality information (Dataset Exchange Working Group)
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- Re: [dxwg] Profiles have URI identifiers that resolve to more detailed descriptions (6.1)
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- Re: [dxwg] Profiles must support discoverability via search engines (UC 5.40)
- Re: [dxwg] Extending DCAT for services
- RE: [dxwg] Extending DCAT for services
- Closed: [dxwg] vann:usageNote used incorrectly in DCAT RDF representation
- Re: [dxwg] vann:usageNote used incorrectly in DCAT RDF representation
- [dxwg] new commits pushed by agbeltran
- [dxwg] new commits pushed by davebrowning
- [dxwg] Pull Request: dcat:keyword - Remove sub-property axiom for consistency with document
- [dxwg] Pull Request: Replace vann:usageNote with skos:scopeNote
- [dxwg] Pull Request: dcat:keyword - Remove sub-property axiom for consistency with document
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] Distribution schema [RDIS]
- Re: [dxwg] Distribution definition [RDIDF]
- Re: [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- [dxwg] Incorrect type for *URL properties - should be owl:DatatypeProperty with range xsd:anyURI
- Re: [dxwg] Extending DCAT for services
- Re: [dxwg] Qualified forms [RQF]
Monday, 4 June 2018
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profiles have URI identifiers that resolve to more detailed descriptions (6.1)
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] Qualified forms [RQF]
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] Licenses/rights/obligations on Services
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] profileDesc and the Guidance document
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- Re: Plenary agenda June 5
- Re: Plenary agenda June 5
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- Re: Plenary agenda June 5
- Re: [dxwg] Profile negotiation [RPFN]
- Re: Plenary agenda June 5
- Re: Plenary agenda June 5 / Partial list of requirements for approval / Informative supplement
- RE: Plenary agenda June 5
- Re: [dxwg] Extending DCAT for services
- Re: [dxwg] Entailment of schema.org [RES]
- Re: [dxwg] Provenance information [RPIF]
Sunday, 3 June 2018
- RE: ACTION-125: Coordinate qualified relations topics (Dataset Exchange Working Group)
- [dxwg] new commits pushed by dr-shorthair
- [dxwg] new commits pushed by dr-shorthair
- [dxwg] new commits pushed by dr-shorthair
Saturday, 2 June 2018
- RE: Plenary agenda June 5
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] Provenance information [RPIF]
- Re: [dxwg] Use case: web browser navigation of profile information
- Closed: [dxwg] ID49 created - dataset business context / 'Project' class
- Re: [dxwg] profileDesc and the Guidance document
- Re: [dxwg] Profile negotiation [RPFN]
- Re: Plenary agenda June 5
- Re: [dxwg] Profile negotiation [RPFN]
- Re: [dxwg] Profile negotiation [RPFN]