- From: Niklas Lindström <lindstream@gmail.com>
- Date: Wed, 22 Jan 2014 11:36:28 +0100
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: "David I. Lehn" <dil@lehn.org>, Linked JSON <public-linked-json@w3.org>
- Message-ID: <CADjV5jevzLQqWUG21Kd0F+Lmn0jGFxPPiMGj9=iUYFeCD5-tGA@mail.gmail.com>
On Fri, Jan 17, 2014 at 7:31 PM, Markus Lanthaler <markus.lanthaler@gmx.net>wrote: > On Friday, January 17, 2014 6:32 PM > > > > On Fri, Jan 17, 2014 at 6:13 AM, Markus Lanthaler > > <markus.lanthaler@gmx.net> wrote: > > > I'm wondering whether we should set up a temporary redirect for the > > specs to > > > w3.org now that they've become RECs: > > > > > > http://json-ld.org/spec/latest/json-ld/ > > > -> http://www.w3.org/TR/json-ld/ > > > > > > http://json-ld.org/spec/latest/json-ld-api/ > > > -> http://www.w3.org/TR/json-ld-api/ > > > > > > This would make it clear that there's (at least currently) only a > > single > > > version of the spec. As soon as we start working on these document > > again, we > > > just remove the redirect. > > > > > > > -1 > > > > I don't think we should be switching around the meaning of those > > spec/latest/ links. Let's keep those pointing at the latest draft > > from this group. > > Well, that's the REC at w3.org. > > > > One reason is people may use the json-ld.org link vs > > w3.org one and then when we change the meaning of those links, they > > would be pointing at the wrong document. > > > > How about this: On the website navbar dropdown, add a group at the top > > called "Recommendations" that links to the latest w3.org docs and > > change the text "Latest" to "Latest Draft" (and still use spec/latest/ > > for the link). Then on the spec/ page, for each doc with official > > recommended specs, add another line with links to each recommedation > > doc, and change the "Links to JSON-LD specifications" text to "Links > > to JSON-LD drafts". > > Yeah, that's great but overkill till we really update the drafts. We > hopefully don't have to for a while. > > People have been waiting hard for a stable spec. I think the most important > thing to do now is to show them that they are stable now. Confusing them > with different documents (even if they might contain exactly the same > content) is counterproductive at the moment. Just redirecting them > (temporarily) to w3.org sends a strong enough signal. As soon as we make > changes, we can switch back and serve the new latest speck at json-ld.org. > > Does that make sense? > +1 Definitely. Cheers, Niklas > > -- > Markus Lanthaler > @markuslanthaler > > >
Received on Wednesday, 22 January 2014 10:37:30 UTC