Use of tentative for "not ready for implementation" specs?

[gsnedders]

Currently https://web-platform-tests.org/writing-tests/file-names.html#test-features says:

.tentative : Indicates that a test makes assertions not yet required by any specification, or in contradiction to some specification. This is useful when implementation experience is needed to inform the specification. It should be apparent in context why the test is tentative and what needs to be resolved to make it non-tentative.

However, https://github.com/web-platform-tests/wpt/pull/36353#issuecomment-1273504927 raises the issue of parts of CSS Color Level 6 (which has a banner saying: "This spec is not yet ready for implementation. It exists in this repository to record the ideas and promote discussion.")

Should tests for such things be marked as tentative or not?

[foolip]

Tentative tests so far are for things where there's no spec text yet, just an open issue or PR. If we want to be able to link tests to spec status, I think some other mechanism would be preferable.

If we have spec links this information could be inferred, right?

[nt1m]

The banner on CSS Color Level 6 does insinuate "not yet required by any specification".