- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Tue, 11 May 2021 11:56:10 +0200
- To: Benjamin Young <byoung@bigbluehat.com>
- Cc: Manu Sporny <msporny@digitalbazaar.com>, "public-json-ld-wg@w3.org" <public-json-ld-wg@w3.org>, Kazuyuki Ashimura <ashimura@w3.org>
On Fri, May 07, 2021 at 04:01:48PM +0000, Benjamin Young wrote: > Agreed! This is a far clearer, more researcher-friendly approach. > > It'd be great (as Kaz mentioned) to see this approach taken across all the various superseded and/or deprecated standards. I wonder if it shoule be up to individual WGs to decide whether to deprecate, supercede of just list versions. The Web platform waits for no man or spec; I feel like those folks tend to rev APIs quickly, create compatibility matrixes, and leave it to polyfills and clever app programmers to deal with the legacy. I think data formats and query and schema languages are more frequently referenced by version and should carry less judgemental pointers to future versions. > This is probably not the right list to do that discussion on, though. 😉 > > Kaz, would it make sense to start an issue somewhere and work there? > > Thanks, all! > Benjamin > W3C JSON-LD Chair > > > -- > > http://bigbluehat.com/ > > http://linkedin.com/in/benjaminyoung > > ________________________________ > From: Manu Sporny <msporny@digitalbazaar.com> > Sent: Friday, May 7, 2021 7:45 AM > To: public-json-ld-wg@w3.org <public-json-ld-wg@w3.org> > Subject: Re: JSON-LD 1.0 - "superseded" UI on site is overly harsh and pushy > > On 5/7/21 2:44 AM, Ivan Herman wrote: > > It displays the fact that the specification is superseded but, otherwise, it > > is exactly the same as before. > > Much better, Ivan! > > -- manu > > -- > Manu Sporny - https://www.linkedin.com/in/manusporny/ > Founder/CEO - Digital Bazaar, Inc. > blog: Veres One Decentralized Identifier Blockchain Launches > https://tinyurl.com/veres-one-launches > >
Received on Tuesday, 11 May 2021 09:56:19 UTC