hayagriva icon indicating copy to clipboard operation
hayagriva copied to clipboard

Using full date times in date fields

Open m-haug opened this issue 3 years ago • 4 comments

In a few cases, I've found myself wanting to specify date times, most often when tracking when I accessed URLs, but also for blog posts that specify this information.

Would you be willing to consider such a contribution?

m-haug avatar Aug 17 '22 12:08 m-haug

That would be a good addition I think. Which format did you have in mind?

reknih avatar Aug 17 '22 19:08 reknih

I think RFC 3339 is a good compromise between representable information and ease of implementation.

AFAIK, biblatex supports full ISO8601, including date ranges, in date fields, but that might be a bit overkill.

m-haug avatar Aug 18 '22 07:08 m-haug

Sounds great, go for it!

reknih avatar Aug 18 '22 08:08 reknih

AFAIK, biblatex supports full ISO8601, including date ranges, in date fields, but that might be a bit overkill.

a) I don't believe biblatex supports the full specification, and b) generally-speaking, biblatex is very well-designed, based on practical experience.

Anyway, on the CSL end, this is one outcome of discussions of what we would need there.

https://github.com/retorquere/json-schema-edtf

It's basically the level 1 subset of EDTF, and one addition (season intervals) that we thought we needed.

We felt the uncertainty, season, and range stuff was pretty useful in EDTF. Not sure RFC 3339 supports those?

BTW, one of the crates that has been released from the citeproc-rs project:

https://lib.rs/crates/edtf

bdarcus avatar Mar 24 '23 22:03 bdarcus