Carles, On Sun, May 15, 2011 at 1:52 PM, Carles Pina <[email protected]> wrote:
... >> So you all agree that: >> >> a) the CSL 1.0.1 schema should require that the cs:updated element holds >> either a xsd:dateTime timestamp or have no content >> >> and >> >> b) that for styles in the git repo, cs:updated should be blank. So we should >> delete any existing timestamps, and make sure they aren't added for further >> commits. > > I would not do it, I expect the cs:updated to have the timestamp in > the repository, so it's easy to clone, users can just browse the > repository using the github interface and download the ready-to-use > style, etc. Except that the github interface lists updated date-times for all files by default already. And how do you respond to my previously noted problems? To repeat ... There are a variety of issues with forcing style authors to update the cs:updated values manually: - it's tedious - it's error prone (easy to forget to do, most basically) - it mixes content and metadata (the metadata changes the sha1 value) > I would update the cs:updated when pushing with the pushing date, no? You mean like pre-commit or pre-push script? That solves some of my issues above, but not all of them. Bruce ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
