W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > August 2018

[dxwg] Use Case: Negotiation by Coordinate Reference System

From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
Date: Thu, 02 Aug 2018 03:56:42 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issues.opened-346850121-1533182195-sysbot+gh@w3.org>
rob-metalinkage has just created a new issue for https://github.com/w3c/dxwg:

== Use Case: Negotiation by Coordinate Reference System ==
If you are submissing a new USE CASE, please use the template below. Otherwise, delete the use case template before submitting your contribution.

### Negotiation by Coordinate Reference System (example of other dimension)
Status: Proposed


Creator: Rob Atkinson

Deliverable(s): ( AP Guidelines, Content Negotiation)

## Stakeholders

## Problem statement
As an example of interchange of spatial data on the Web, the MapML specification under development provides a spatial representation of metadata about data to be included in a typically cartographic map. A need has been identified to allow clients to access the same content using different "Coordinate Reference Systems (CRS)".  This is a potential dimension of content negotiation. Others in the spatial domain would include geometry type (point, bounding box, outline polygon, complex polygon with islands and holes) and spatial precision. Temporal dimensions are also relevant - last known position, version no etc.

## Existing approaches
HTTP Content negotiation already uses dimensions of media-type+encoding and language. Profiles (views) is another fairly common case.

## Links

## Requirements
Profile negotiation mechanisms must support or safely co-exist with negotiation over other dimensions of data organisation.

## Related use cases

## Comments
Raised by @larsgsvensson in Profile Negotiation sub-group - and we felt that this requirement was not captured and a Use Case was required.


Please view or discuss this issue at https://github.com/w3c/dxwg/issues/311 using your GitHub account
Received on Thursday, 2 August 2018 03:56:56 UTC

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