From: newsml@yahoogroups.com [mailto:newsml@yahoogroups.com] On Behalf
Of Jayson Lorenzen
> Thanks Laurent, I agree it would be good to have in the
> Guidelines. It would be interesting to see how others
> are doing this and I hope this thread continues a bit
> (hint hint to all lurkers).


PA runs on a 24-hour news cycle. Our wire services are driven using
NITF, so we use du-key/@key and @version to indicate the threading of
our stories, with series/@series-part to indicate how pieces of the
story join together. Our du-key/@key is derived from the slugline.

In newsML terms, we map du-key/@key onto NewsItemId - so stories can
grow and have write-throughs whilst retainign the sane NewsItemId. We
spot parent and child stories, and use AssociatedWith to link up fromt
he child to the parent, and NewsItemRef in a
NewsComponent[/Role/@FormalName='Supporting'] hierarchy to link down
from parents to children.

Unfortunately what we don't have is a mechanism for carrying stories
across multiple days. Having not had the discussion with Editorial about
long-running stories and whether they really do 'replace' each other
across days, I'm not sure of we'd keep re-using the sane NewsItemId and
DateId and just jeep increasing RevisionId - if not, I think we'd create
a new dateId/NewsItemId pair and use DerivedFrom to point to yesterday's
story.

Paul

This e-mail is from the PA Group. For more information, see www.thepagroup.com.
This e-mail may contain confidential information.
Only the addressee is permitted to read, copy, distribute or otherwise use this
email or any attachments.
If you have received it in error, please contact the sender immediately.
Any opinion expressed in this e-mail is personal to the sender and may not
reflect the opinion of the PA Group.
Any e-mail reply to this address may be subject to interception or monitoring
for operational reasons or for lawful business practices.