James Holderness wrote:
James M Snell wrote:
the dcterms:valid element is not quite expressive enough in that it
is limited to dates (and does not include the time).
Are you sure about that? The example here
(http://web.resource.org/rss/1.0/modules/dcterms/#valid) certainly
shows a time range, and the documentation for DCMI Period here
(http://dublincore.org/documents/dcmi-period/) says nothing about
limiting to a date either. You get to specify the scheme used, but
they generally seem to use W3C-DTF which gives you as much (or as
little) precision as you want.
I'm going off of the description here:
http://www.dublincore.org/documents/dcmi-terms/
Term Name: date
URI: http://purl.org/dc/elements/1.1/date
Label: Date
Definition: A date associated with an event in the life cycle of the
resource.
Comment: Typically, Date will be associated with the creation or
availability of the resource. Recommended best practice for encoding the
date value is defined in a profile of ISO 8601 [W3CDTF] and follows the
YYYY-MM-DD format.
References: [W3CDTF] http://www.w3.org/TR/NOTE-datetime
Type of Term: element
<http://www.dublincore.org/usage/documents/principles/#element>
Status: recommended
<http://www.dublincore.org/usage/documents/process/#recommended>
Date Issued: 1999-07-02
Term Name: valid
URI: http://purl.org/dc/terms/valid
Label: Valid
Definition: Date (often a range) of validity of a resource.
Type of Term: element-refinement
<http://www.dublincore.org/usage/documents/principles/#element-refinement>
Refines: http://purl.org/dc/elements/1.1/date
Status: recommended
<http://www.dublincore.org/usage/documents/process/#recommended>
Date Issued: 2000-07-11
Also, the description and examples of the Date element here:
http://www.dublincore.org/documents/usageguide/elements.shtml
/Element Description:/ A date associated with an event in the life cycle
of the resource. Typically, Date will be associated with the creation or
availability of the resource. Recommended best practice for encoding the
date value is defined in a profile of ISO 8601 [Date and Time Formats,
W3C Note, http://www.w3.org/TR/NOTE-datetime] and follows the YYYY-MM-DD
format.
Guidelines for content creation:
If the full date is unknown, month and year (YYYY-MM) or just year
(YYYY) may be used. Many other schemes are possible, but if used, they
may not be easily interpreted by users or software.
Examples:
Date="1998-02-16"
Date="1998-02"
Date="1998"
According to the authoritative descriptions, there is no mention of a
time component.
dcterms:available is equivalent to atom:updated.
I would have thought that equivalent was dcterms:modified.
Sorry, was thinking atom:published, typed atom:updated
dcterms:modified -> Date on which the resource was changed.
dcterms:available -> Date (often a range) that the resource will
become or did become available.
There appears to not be any dcterm equivalent to my max-age element.
I thought about that, but I couldn't see any real advantage to max-age
in this context. It's not as if it's relative to the last time the
document was retrieved in which case an equivalent end date would have
to be recalculated every time the feed was downloaded. Since it's
relative to the atom:update time, it only needs to be calculated when
an item is updated and in that case you'd be updating the feed anyway.
With max-age, if your entry is supposed to expire after 6-months from
the time it was updated, there is no need to recalculate the value. If
I used expires for this, my software would have to recalculate the
expiration with every update operation. It may be a minor savings of
cycles, but it is still a savings.
- James
