[dxwg] Distinguish query and item access semantics (accessURL)

rob-metalinkage has just created a new issue for https://github.com/w3c/dxwg:

== Distinguish query and item access semantics (accessURL) ==
If you are submissing a new USE CASE, please use the template below. Otherwise, delete the use case template before submitting your contribution.

---
### Use case name
Status: new

Identifier:

Creator: rob Atkinson

Deliverable(s): 
(DCAT1.1)

## Tags
DCAT

## Stakeholders
''Mandatory list of stakeholders experiencing the problem. When describing the stakeholder, please be as specific as possible (e.g., data consumer, data producer, data publisher, program, etc.) and avoid using the term user.''

## Problem statement
Use Case

When considering Linked Data applications viewing datasets there are potentially multiple ways to access items. Large datasets in particular may support access to specific items, queries, subsets and optimally packaged downloads of data.

Because the implications for user and agent interaction vary greatly between these modes of access there is a need to distinguish between distributions that package the entire dataset.

Furthermore, access methods delivering queries and subsets may introduce container elements, independently of the dataset itself. 

So if we had a metadata catalog that supported a query service that returned a set of DCAT records (using say the BotDCAT-AP profile), 
and also an api that delivered a specific record using this same profile  we would need to be able to specify the query service support
 the BotDCAT-AP profile and MyDCATCatalogSearchFunction profile (that specifies how the container structure is implemented?)


2) we need to distinguish between enpoints that
a) deliver a single item
b) deliver a list based on some filter/criteria
c) deliver the entire dataset

case c) is  covered by dcat:downloadURL but dcat:accessURL is too general to distinguish between the others. we need  one of:
i.) canonical subclasses  of accessURL or item and list endpoints
ii.) a type property (dct:type?) for the distribution with canonical values for list and endpoint cases
iii) a property  e.g. dcat:containerProfile to indicate that data conforming to a domain profile will be wrapped in a container conforming to an access method profile.

Requirement:
Provide a (single extra level of) finer grainer distinction for AccessURL, consistent with the existing strategy of distinct accessURL and downloadURL. 


## Existing approaches
?

## Links
''Optional link list to documents and projects this use case refers to''

## Requirements
Provide a (single extra level of) finer grainer distinction for AccessURL, consistent with the existing strategy of distinct accessURL and downloadURL. 

## Related use cases

## Comments
''Optional section for editorial comments, suggestion and their interactive resolution''


---


Please view or discuss this issue at https://github.com/w3c/dxwg/issues/145 using your GitHub account

Received on Tuesday, 6 March 2018 21:08:07 UTC