Supersedes or Superseded by not displayed for Types #1109

Closed
RichardWallis opened this Issue Apr 19, 2016 · 7 comments

Projects

None yet

4 participants

@RichardWallis
Contributor

Only currently visible on attribute pages

@RichardWallis RichardWallis self-assigned this Apr 19, 2016
@RichardWallis RichardWallis added a commit that referenced this issue Apr 19, 2016
@RichardWallis RichardWallis Added display of Supersedes or Superseded by for Types
Fix for (#1109)  emulates what already happens for Supersedes or Superseded by attributes
1c248e5
@danbri
Contributor
danbri commented Apr 19, 2016

I was pretty sure we had an issue for this, but I've not managed to find it yet :)

@danbri
Contributor
danbri commented Apr 19, 2016

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...

@danbri danbri pushed a commit that referenced this issue Apr 19, 2016
Dan Brickley Noted fix for #1109 fc28893
@danbri
Contributor
danbri commented Apr 19, 2016

Ok this is live on webschemas.org - is there a good example we can look at to test?

@Dataliberate
Contributor

http://webschemas.org/CreativeWorkSeason
http://webschemas.org/Season

“do you handle if a type is superseded but not by any particular new term”

  • would need to find an example to check

We should in addition probably display a warning near the top saying “This
term has been superseded by XXXX. Please consider before using”

~Richard.

Richard Wallis
Founder, Data Liberate
http://dataliberate.com
Linkedin: http://www.linkedin.com/in/richardwallis
Twitter: @rjw

On 19 April 2016 at 16:36, Dan Brickley notifications@github.com wrote:

Ok this is live on webschemas.org - is there a good example we can look
at to test?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#1109 (comment)

@danbri
Contributor
danbri commented Apr 20, 2016 edited

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.

@RichardWallis
Contributor

Fixed in V3.0

@unor
Contributor
unor commented Oct 27, 2016 edited

do you handle if a type is superseded but not by any particular new term

would need to find an example to check

Maybe a relevant case is ProfessionalService? See #1418

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment