Re: proposal to add factChecker and copyEditor to NewsArticle

* Forwarding this response on behalf of AP's Stuart Myles, who is having problems with W3C's servers. *

As Andreas, Jean-Pierre and Trond have said, I think that there are 
various kinds of editorial and contributor roles that can be involved in
 the production of news stories. Exactly who plays what roles (and what 
their titles are) tends to vary a bit between news organizations. (And, 
in my experience, it can also vary by shift - there can be different 
somewhat different editorial workflows overnight versus during the day, 
even within the same publisher. And, certainly at the AP, different 
bureau have different practices, depending upon how lavishly or 
economically they have been staffed).

I think that being able to express different types 
of editorial input makes a lot of sense. And, as Andreas suggests, I 
think it is worth discussing in the rNews context at the IPTC (we have a face-to-face meeting next week and I'll add it to the agenda).

So far as the specifics of the copyEditor and 
factChecker roles, I think one good litmus test for this sort of thing 
is: can we find examples on the web of news publishers who are 
expressing these concepts (or something very like them)? If we have 
evidence that this is something that publishers are indicating to 
readers already, then it makes sense for it to be represented in a 
machine-readable fashion, too.

Regards,

Stuart

>________________________________
> From: "trond.huso@ntb.no" <trond.huso@ntb.no>
>To: public-vocabs@w3.org 
>Sent: Wednesday, October 17, 2012 4:23:57 AM
>Subject: RE: proposal to add factChecker and copyEditor to NewsArticle
> 
>In a typical workflow in a newsroom there is a journalist who writes/translate the story. The story is then sent to - depending on where you are working in the organization - the desk. Here the head of the desk or the one in charge of the current session will look at the story. He/she will check the story before sending it out, or check the story before returning it to the journalist who wrote it to correct the errors.
>In Norway it is common that the person checking the story will correct it (unless the mistakes are too many) before sending it out.
>
>He/she is again just another editor on the story though. 
>
>Trond Husø
>
>-----Original Message-----
>From: Evain, Jean-Pierre [mailto:evain@ebu.ch] 
>Sent: 17. oktober 2012 08:21
>To: Ivan Herman; Martin Hepp
>Cc: John Bachir; public-vocabs@w3.org
>Subject: RE: proposal to add factChecker and copyEditor to NewsArticle
>
>EBU is also providing role vocabulries that can make good use of "role" (also implemented like this in EBUCore) also referecenced by MovieLabs in their metadata specification. 
>
>However, the answer is not so straightforward.
>
>There is a good case for defining all these roles as subclasses of e.g. "contributor" or else. Then one global query on contributor would list them all. But it would equally list all contributors with different roles.
>
>One way or the other - these are anyway not mutually excluding.
>
>Jean-Pierre
>________________________________________
>From: Ivan Herman [ivan@w3.org]
>Sent: 17 October 2012 00:38
>To: Martin Hepp
>Cc: John Bachir; public-vocabs@w3.org
>Subject: Re: proposal to add factChecker and copyEditor to NewsArticle
>
>Martin,
>
>I think I agree with you. Actually, for this application there are already vocabularies that define those roles, bound to some FRBR related works, it may better reusing those.
>
>Just my 2 cents
>
>Ivan
>
>----
>Ivan Herman
>+31 641044153
>
>(Written on my mobile. Excuses for brevity and frequent misspellings...)
>
>
>
>On 16 Oct 2012, at 17:46, Martin Hepp <martin.hepp@ebusiness-unibw.org> wrote:
>
>> Since the two proposed properties represent roles that a certain person has for a certain NewsArticle, I am in general inclined to not recommend individual properties for each role but rather use a generic property "typeOfContribution" or "role" and have that link a) the NewsArticle (or CreativeWork) with b) the Person via an intermediate node (e.g. http://schema.org/Role) with enumerations (internal or external) for popular roles.
>>
>> Otherwise we will end up with a mess of properties.
>>
>> But this of course really a tradeoff between conceptual beauty and cleanness on one hand and ease of markup on the other.
>>
>> Just my 2 cents from experience
>>
>> Martin
>>
>> On Oct 16, 2012, at 10:34 PM, John Bachir wrote:
>>
>>> Anyone have any thoughts on this?
>>>
>>> Is there another venue more appropriate for this sort of thing?
>>>
>>> Thanks,
>>> John
>>>
>>>
>>> On Fri, Oct 5, 2012 at 9:00 PM, John Bachir <john@ganxy.com> wrote:
>>> The typical roles in producing a journalistic work are: writer, editor, fact-checker, copy-editor.
>>>
>>> Thing > CreativeWork > Article > NewsArticle has these properties of type Person:
>>>
>>> accountablePerson
>>> author
>>> contributor
>>> copyrightHolder
>>> creator ("the same as the Author property for CreativeWork" -- I 
>>> don't know what that means) editor provider
>>>
>>> All of these are from CreativeWork.
>>>
>>> I propose that NewsArticle, or maybe Article for one or both, add the following two properties of type Person:
>>>
>>> factChecker
>>> copyEditor
>>>
>>> Before I put together a more detailed proposal on the wiki, I'm looking for some initial feedback from this group.
>>>
>>> Thanks,
>>> John
>>
>> --------------------------------------------------------
>> martin hepp
>> e-business & web science research group universitaet der bundeswehr 
>> muenchen
>>
>> e-mail:  hepp@ebusiness-unibw.org
>> phone:   +49-(0)89-6004-4217
>> fax:     +49-(0)89-6004-4620
>> www:    http://www.unibw.de/ebusiness/ (group)
>>        http://www.heppnetz.de/ (personal)
>> skype:   mfhepp
>> twitter: mfhepp
>>
>> Check out GoodRelations for E-Commerce on the Web of Linked Data!
>> =================================================================
>> * Project Main Page: http://purl.org/goodrelations/
>>
>>
>>
>>
>
>------------------------------------------------------------------------------
>
>**************************************************
>This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
>If you have received this email in error, please notify the system manager. This footnote also confirms that this email message has been swept by the mailgateway
>**************************************************
>
>
>
>
>
>
>
>

Received on Wednesday, 17 October 2012 18:06:29 UTC