Supersedes or Superseded by not displayed for Types #1109
Comments
Fix for (#1109) emulates what already happens for Supersedes or Superseded by attributes
|
I was pretty sure we had an issue for this, but I've not managed to find it yet :) |
|
Merged the pull request. But do you handle if a type is superseded but not by any particular new term, i.e. obsolete/deprecated. I think that was the other issue I left open somewhere... |
|
Ok this is live on webschemas.org - is there a good example we can look at to test? |
|
http://webschemas.org/CreativeWorkSeason “do you handle if a type is superseded but not by any particular new term”
We should in addition probably display a warning near the top saying “This ~Richard. Richard Wallis On 19 April 2016 at 16:36, Dan Brickley notifications@github.com wrote:
|
|
We shouldn't make the warnings too heavy or it creates awkwardness e.g. when search marketing people have recommended something to their clients then it gets superseded. We want consumers to respect older structures wherever possible and not worry publishers into constantly updating in the absence of concrete product-related incentives imho. |
|
Fixed in V3.0 |
Maybe a relevant case is |
Only currently visible on attribute pages
The text was updated successfully, but these errors were encountered: