Use /TR link for CSS Line Grid Module Level 1

[xfq]

No description provided.

[iherman]

@xfq, this is one of those things... The latest published version is from... 2014, whereas the CSS document is very recent. I have no idea why the CSS WG has not officially published since 2014. We may want to ask Chris or Bert what the best one to refer to is...

[xfq]

OK. If we decide to link to the ED, we should use "editors" instead of "TR" in the JSON file.

(See device-memory.json for an example.)

[tidoust]

More importantly, the framework cannot retrieve spec info from the Editor's Draft URL, and thus cannot even find the title of the spec (which appears blank in the generated table).

In the data files, we should be using the URL in /TR/ when available. From that /TR/ URL, I'll be able to fetch spec info, including the URL of the Editor's Draft. I created #105 for that.

One of the goals of this type of documents is to show what W3C is doing in a given space. While that's not always done properly, we're still expecting WG to publish specs on /TR/ on a regular basis. So I would actually suggest favoring the /TR/ link when it exists.

It may still be important to link to the ED, and/or to have a link to the ED appear in the generated tables. I created #106 and #107 to track progress there.

Data files should link to the document in /TR/ in the meantime (and even if we decide to link to the ED by default later on). I'm merging this as-is as a result.