I've posted the revised version of the Feed ranking draft updated to
reflect the recent conversations. This is a major update.
http://www.ietf.org/internet-drafts/draft-snell-atompub-feed-index-03.txt
Sample:
feed
...
r:ranking-scheme
domain=urn:my-ranking-domain
label=My
I know the Atom working group seemed to be against reusing dublin core in
the core Atom spec, but since this is an extension, were dcterms:valid
and/or dcterms:available ever considered as alternatives? From my
understanding they appear to be describing essentially the same thing.
I don't
I think this is good, but I would prefer the atom:link to be used
instead of
the fh:prev structure, as that would better fit the atom way of doing
things.
I also think it may be very helpful if we could agree on an extension
name space
that all accepted extensions would use, in order to
Hi Henry,
Thanks for the feedback. As I've explained before, I have a pretty
strong preference for the current design, to make it usable in other
formats; i.e., the scope of this is not just Atom (which is why I'm
probably going to do it as an Individual submission).
One path forward
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
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
James M Snell wrote:
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
Just a follow-up on the representation of Date Ranges in dublin core. I was
under the mistaken impression that you needed to use a DCMI Period encoding
to represent a date range, but apparently ISO 8601 time intervals are
perfectly valid. In order to clarify the situation, the DC Date Working
