[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: a methodical approach to defining what date elements we need



On 7/13/04 5:49 PM, "Sam Ruby" <rubys@xxxxxxxxxxxxxxxx> wrote:

> 
> Norman Walsh wrote:
> 
>> I'm now convinced that it would be better to use just two:
>> 
>> Issued = when I published the essay
>> Modified = when I last changed any of the bits in the entry.
>> 
>> If I make a "significant" change, I should
>> 
>> 1. Create a new entry with a new ID and new dates
>> 2. Indicate that this new entry dcterms:replaces the original.
>> 2. Update the original to say it's been dcterms:isReplacedBy the new one.
>> 
>> It's more work, but it'll make for a better historical record.
> 
> It's not much more work for you, but it is much more work for consumers.
> 
> Consider that a typical aggregator polls for data.  If you replace an
> entry twice, and the aggregator missed the first one, then it has an
> incomplete history to reconcile.

But if he just tweaks a date field each update, the consumer won't even know
it missed anything.

Robert Sayre