On Mon, Sep 10, 2012 at 7:08 PM, Sebastian Karcher <[email protected]> wrote: >> * field assignments (which item type should, or shouldn't, have >> which fields). Aurimas prepared a map for Zotero: >> http://aurimasv.github.com/z2csl/typeMap.xml . It would be great if we >> could standardize the fields exposed to the CSL processors among the >> different reference managers (on a per item type basis). My hope is >> that we can clean up Zotero's metadata model in the coming year >> (tickets as compiled by the Zotero user community can be found at >> https://github.com/ajlyon/zotero-bits/issues ), and offer the result >> as a guideline for other reference managers. > This is, imho, really the top priority - with different fields/item > we'll get inconsistent outputs - cf. e.g. publishers for journals. > Happy to help work on this.
The ball for this is really in the court of the Zotero team, though. I don't think you, me, Avram, Grégoire (Gracile) and others can do much more prep work for Simon and Dan, and I'm pretty sure we're all available to give input once they start work on it. But it seems to be a few months out at least (post-November). >> - There are still quite a few open CSL tickets ( >> https://github.com/citation-style-language/schema/issues ). Some have >> solutions that require a backwards incompatible release (i.e. CSL 1.1) >> and style upgrades, while other tickets have stalled due to the >> absence of good ideas or due to disagreement. I don't expect too much >> progress here, unless people step in and reboot the discussions. > > I think some of them are pretty important. My top two are: > https://github.com/citation-style-language/schema/issues/36 > https://github.com/citation-style-language/schema/issues/94 > > The first one is pretty major, but I'd really like to see 94 in one of > the smaller releases. I'm actually hoping that we might be able to come up with a consistent solution that addresses both custom fields, custom locator labels (https://github.com/citation-style-language/schema/issues/94), and custom identifiers (https://github.com/citation-style-language/schema/issues/33). A recent thought of mine was to create some sort of distinct name-space for custom variables, e.g.: <text custom-variable="my-own-field"/> That way you would have complete freedom to define custom variable names, and there wouldn't be conflicts with the 'core' set of official CSL variables. Regardless of the particular solution chosen, it might help if we make a fresh start with the entire discussion. I think nobody will dispute the usefulness of having custom fields, but I'm very keen to learn, in the precisest terms possible, what implications Bruce, Dan, Simon, and others foresee when it comes to custom variables (e.g. with regards to syncing). That would help me understand what the considerations should be when thinking of solutions. (a pointer would suffice as well, if this already has been discussed) Rintze ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
