Re: [httpapi] linkset draft ready for next steps

[Phil Archer <[e-mail]>]

We need to come back to this discussion and come to a resolution before we can progress to last call (and thanks MNot for your comments today as well).

As indicated earlier, I don't have a strong opinion that we definitely should or definitely should not support multilingual labels in the JSON format. However, it does 'feel right' to me that the JSON serialization and the Web Linking serialization are equivalent in the information they can contain. Round tripping between formats is not a requirement but it never feels right to me to throw away data or functionality unless the gain is substantial.

When I created a JSON Linkset visualization tool [1] I included support for multilingual labels (and there's one in the sample used in the demo) without any difficulty.

So Julian and others, would you be OK with keeping this?

Phil

[1] https://github.com/gs1/linkset






Phil Archer
Director, Web Solutions, GS1
https://www.gs1.org

Meet GS1 Digital Link Developers at
https://groups.google.com/forum/#!forum/gs1-digital-link-developers

https://philarcher.org
[phone]
@philarcher1
Skype: philarcher

On 08 July 2021 16:12, httpapi wrote:
Am 08.07.2021 um 16:35 schrieb Phil Archer:
> Can I clarify your comment please Julian.
>
> Are you suggesting that Linkset could drop support for multilingual titles on a given link? And does that apply to both the native HTTP Link header format and the JSON format, or just one? Such a move would remove complexity that may be little used. For better or worse, it seems that in the real world, a vanishingly small number of websites use content negotiation by language. The new W3C website design is not using it, for example, and is instead going for a {domain}/{lang}/{page} structure. So, yes, having a single link to a resource that is made available with language-based conneg is probably an edge case hanging on by its fingernails.
>
> Even so, it is part of HTTP and so leaving it out might be problematic, process-wise if nothing else? Apologies if I've misunderstood your comment.

For now I was just considering the JSON format due to the complexity it adds.

I can understand if feature parity has higher priority than terseness, but wanted at least see some discussion.

Best regards, Julian

--
httpapi mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/httpapi

CONFIDENTIALITY / DISCLAIMER: The contents of this e-mail are  confidential and are not to be regarded as a contractual offer or acceptance from GS1 (registered in Belgium). 
If you are not the addressee, or if this has been copied or sent to you in error, you must not use data herein for any purpose, you must delete it, and should inform the sender. 
GS1 disclaims liability for accuracy or completeness, and opinions expressed are those of the author alone. 
GS1 may monitor communications. 
Third party rights acknowledged. 
(c) 2020.