Re: [media-types] renamed draft: "A Media Type Structured Syntax Suffix for JSON Text Sequences"

[Erik Wilde <[e-mail]>]

hello mark.

On 2016-09-26 18:36, Mark Baker wrote:
> Erik - I don't see any issue with the registration per se, but I do
> wonder about the value. Is there anybody else using this approach? And
> why did the line get drawn at JSON-object-per-line rather than, say,
> the more generic data-per-line approach which already has a history
> (text/csv or text/uri-list, off the top of my head).

it sounds to me as if you have an issue with RFC 7464 itself. for our 
use of it, we simply have a JSON-based format to start with (GeoJSON, 
RFC 7946), and then using RFC 7464 is very straightforward if you're 
interested in representing sequences of whatever you're representing in 
JSON. if that's not what you want to do then other formats may be 
alternatives, but for us RFC 7464 is a good match. all we're looking for 
is a way to mint a media type that can use a structured syntax suffix 
for RFC 7464.

cheers,

dret.

-- 
erik wilde | mailto:[e-mail] |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |