On 6/9/15 4:48 AM, Aurimas Vinckevicius wrote: > > Seems to me like the cost of correctly composing and parsing EDTF > across a number of citeprocs and clients in various languages is much > higher. >
This was my initial thought as well, but upon reflection, it seems that any client that's going to support even some of EDTF's advanced features is probably going to store the date as an EDTF string anyway. I think we would do exactly that in Zotero. The alternative would just move all of EDTF's complexity to the local database schema (though some might need to be pulled out anyway for efficient searching). As for composing and parsing, that's what libraries are for. But, yes, we'll need to find or build a good JS library. ------------------------------------------------------------------------------ _______________________________________________ xbiblio-devel mailing list xbiblio-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
