W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > February 2019

[dxwg] Actions (DCAT) #173, #174, #197: use case for "wasGeneratedBy" and for rate (#726)

From: pwin via GitHub <sysbot+gh@w3.org>
Date: Fri, 01 Feb 2019 10:20:37 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-405637841-1549016435-sysbot+gh@w3.org>
pwin has just created a new issue for https://github.com/w3c/dxwg:

== Actions (DCAT) #173, #174, #197: use case for "wasGeneratedBy" and for rate ==
If you are submissing a new USE CASE, please use the template below. Otherwise, delete the use case template before submitting your contribution.

### Data Streams and Pushed Data
Status: Draaft

Identifier: ID52

Creator: (your name)

Deliverable(s): DCAT 

## Tags

## Stakeholders
Data Consumers

## Problem statement
When delivering time-critical data the periodic polling of an API may miss the exact time of a data update.  To avoid this latency varied approaches are used including the use of a variety of protocols including ftp, rsync, STOMP, OpenWire, and also HTTP using PUT. Examples of this type of data include news data in general, and particularly sports event data.  The problem of latency requiring a "push" service occurs in many other areas too.  In order to accommodate this sort of data feed, recipients would like to be aware of features of the data feed such as the maximum rate of the data feed, the maximum unit size of the data that is provided in one bolus, in addition to other attributes necessary for connecting with this type of data services.  

## Existing approaches

## Links
Examples include:  https://www.pressassociation.com/pa-ready/  , http://www.xmlteam.com/feeds.php  and  http://datafeeds.nationalrail.co.uk/ (see also https://wiki.openraildata.com/index.php?title=Darwin:Push_Port )

## Requirements
For consumers to be able to document in their data repository that the content was generated by a specific set of push services..  For publishers to be able to alert potential recipients to the scale of the data bolus that they need to be prepared to receive, and the maximum rate at which to expect the push feed.

* Provide consumers with a means to document the source of their data coming from a push service
* Provide publishers with a means to describe the volume and maximum rate at which their data will be pushed to the recipient
* Provide  

## Related use cases
''Optional references to related local (refer to anchor identifier <nowiki>[[#Id...]]</nowiki>) and remote use cases (e.g. POE-WG UCs)''.

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


Please view or discuss this issue at https://github.com/w3c/dxwg/issues/726 using your GitHub account
Received on Friday, 1 February 2019 10:20:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:12 UTC