[go: nahoru, domu]

Skip to content
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

Is NewsArticle for only "news" or does it include "opinion", "interviews" etc. too? #1439

Closed
guyvalerio opened this issue Nov 21, 2016 · 7 comments

Comments

@guyvalerio
Copy link

Could someone clarify for me whether NewsArticle is intended to mean only "news" content that a news organisation creates, or is it intended to include comment, interviews features etc too?

We make a clear distinction in our internal data models between the genres of content and wondered how we might expose that in schema.org markup.

Apologies if I'm going over old ground.

@ghost
Copy link
ghost commented Nov 21, 2016

seeAlso: #1437

On Tue., 22 Nov. 2016, 2:56 am Guy Valerio, notifications@github.com
wrote:

Could someone clarify for me whether NewsArticle is intended to mean only
"news" content that a news organisation creates, or is it intended to
include comment, interviews features etc too?

We make a clear distinction in our internal data models between the genres
of content and wondered how we might expose that in schema.org markup.

Apologies if I'm going over old ground.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1439, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFdABocY5afTArkrjZcOoNTiejaGhf5Pks5rAb8vgaJpZM4K4Xaf
.

@thadguidry
Copy link
Contributor

@guyvalerio NewsArticle can be used. Its based off the IPTC work. In fact, if you look at IPTC codes, you will see that they have many additional ones compared to the simple cases that we absorbed into Schema.org.

IPTC already has "Interviewee" for instance: http://cv.iptc.org/newscodes/infosourcerole/

Anyways, spend some research time here: https://iptc.org/standards/subject-codes/ and https://iptc.org/standards/newscodes/

I forgot which code or type they have to hold the kind of Story or Article piece it is, like your use case for "Interview" "Opinion", etc. But you can ask someone at IPTC about that specifically, and then post a reply here to give us all a better understanding :) Thanks! Help us and we'll help you :)

@guyvalerio
Copy link
Author

Thanks @thadguidry

IPTC, as I understand it, define the genre of their "NewsItem" class using their http://cv.iptc.org/newscodes/genre/ vocabulary. Typical values being "analysis", "interview" and many more. They then have subclasses of NewsItem according to media ("Article", "VideoObject" etc) - that makes sense.

So I think that schema.org:NewsArticle is equivalent to rNews:NewsItem. In turn then, any type of content written by a news organisation whether it be news, comment, interview etc is a schema.org:NewsArticle but we cannot use schema.org to differentiate its genre (as IPTC define it) yet.

@davecompton
Copy link

Hi @guyvalerio
Afaik schema.org:NewsArticle inherits genre from CreativeWork per https://schema.org/NewsArticle . Does that work?

@RichardWallis
Copy link
Contributor

That should work - even, as schema:genre takes a URL, using IPTC genre codes if you wanted.

{
  "context": "http://schema.org",
  "@type": "NewsArticle",
  "name": "A biography of some celebrity",
  "genre": "http://cv.iptc.org/newscodes/genre/Biography"
}

@guyvalerio
Copy link
Author

@davecompton @RichardWallis
Great, that answers it. Thank you.

@davecompton
Copy link

Just to finish off the side convo: At TR we have a genre CV but it does not include 'News' as a value. Using a newsItem (from NewsML-G2) already provides the News context (as it would in rNews) ... the genre then indicates the 'style' of the article: Reviews | Interviews ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants