No, you're not missing anything, except that adding what you suggest does have a cost. On Jun 9, 2015 6:41 AM, "Aurimas Vinckevicius" <aurimas....@gmail.com> wrote:
> If I understand correctly, we're talking about the CSL JSON format here, > correct? If so, I don't think it makes a lot of sense semantically to > supply dates as a complex string within the JSON format. JSON gives you all > the flexibility you need to supply date ranges, approximate dates, > date-times, time zones, whatever else you want to support. It's just a > matter of adding some more clearly defined and directly accessible > properties. Am I missing something here? > > On Mon, Jun 8, 2015 at 11:27 PM, Bruce D'Arcus <bdar...@gmail.com> wrote: > >> I think what you see in citeproc-js is shaped by practical decisions >> Zotero made. As in, was better to be loose with the expectations here. >> >> But I've always favored defining CSL dates as EDTF. Not sure what the >> implementers would think about that though, as a requirement. >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> xbiblio-devel mailing list >> xbiblio-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel >> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > xbiblio-devel mailing list > xbiblio-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel > >
------------------------------------------------------------------------------
_______________________________________________ xbiblio-devel mailing list xbiblio-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
