W3C home > Mailing lists > Public > public-linked-json@w3.org > January 2014

RE: Redirecting specs to w3.org

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Fri, 17 Jan 2014 19:31:31 +0100
To: "'David I. Lehn'" <dil@lehn.org>
Cc: "'Linked JSON'" <public-linked-json@w3.org>
Message-ID: <010d01cf13b2$58edf550$0ac9dff0$@lanthaler@gmx.net>
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?

Markus Lanthaler
Received on Friday, 17 January 2014 18:32:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:40 UTC