-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description of headline property shows its newspaper heritage #205
Comments
I still don't understand how http://schema.org/headline is different from http://schema.org/name, other than having a more newspaper-y label. I would suggest deprecating it and http://schema.org/alternativeHeadline (which has the much broader description "A secondary title of the CreativeWork.") in favour of name & alternateName, unless a compelling reason & set of examples that provide guidance for users in differentiating the proper uses of name vs. headline and alternateName vs. alternativeHeadline are provided. Yes, this is a rehash of http://lists.w3.org/Archives/Public/public-vocabs/2014Jan/0198.html but, unless I missed it, there has been no good argument put forward for why we would need to apply all four properties to a single CreativeWork. |
Metabug #418 says about this bug: "Description of headline property shows its newspaper heritage Proposal: working as intended. It is for news. Perhaps add an example or qualifying info to indicate usage intention?" In addition to an example, and changing the description to something more specific like "Headline of the news article.", how about we then move it down to http://schema.org/NewsArticle instead of hanging off of http://schema.org/CreativeWork so that it is found in the appropriate context? |
"how about we then move it down to http://schema.org/NewsArticle instead of hanging off of http://schema.org/CreativeWork so that it is found in the appropriate context?" +1 |
Rather than continuing the tradition of keeping both name/alternateName and headline/alternativeHeadline attached to the domain of CreativeWork, move the latter to the domain of NewsArticle, as was indicated was the intention in metabug schemaorg#418. Closes schemaorg#205. Signed-off-by: Dan Scott <dan@coffeecode.net>
Rather than continuing the tradition of keeping both name/alternateName and headline/alternativeHeadline attached to the domain of CreativeWork, move the latter to the domain of NewsArticle, as was indicated was the intention in metabug schemaorg#418. Closes schemaorg#205. Signed-off-by: Dan Scott <dan@coffeecode.net>
See pull request #423 accordingly. |
@dbs - thanks for the (very sensible) suggestion and implementation. It sounds promising to me but how about we postpone this beyond the looming sdo-gozer release and use it as an excuse to check back in with the rNews team? |
For most users, more convenient to have a general property of things - title Otherwise, have used (name or headline) as title - is not nice. Thank. |
@danbri did you check in with the rNews folks? |
I did some rNews pinging a while back, it may be a good time to try again. My preference would be to declare these as sub-properties of the more general properties, and move on. It might not add a huge amount more information to say 'headline' instead of 'name' but it also feels largely harmless. |
There's a need in the entertainment and publishing industry from a few providers I've spoken to regarding temporary names and working titles. I think this makes it more clear our intended usage of http://schema.org/alternateName and http://schema.org/alternativeHeadline I've created a pull request here: #1227 |
This issue is being tagged as Stale due to inactivity. |
What was the justification for closing #423? As someone coming to this in 2023, it reads like there was a general desire for superseding |
http://schema.org/headline
Currently "Headline of the article".
Not all CreativeWorks that have a headline are necessarily articles.
Suggested alternative "Headline or initial brief description or title at the top or beginning of an article or group of creative works"
The text was updated successfully, but these errors were encountered: