-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Contribution to JATS-Con 2015 #16
Comments
Submitted. |
Reopening, since the JATS4R abstract has made it into the JATSCon program: http://jats.nlm.nih.gov/jats-con/2015/schedule2015a.html . Further instructions: If you have not yet registered for the conference, you can do so here at any time: http://jats.nlm.nih.gov/jats-con/forms/JATSregistration.html Reviews: Reviewer 1:I applaud the effort to bring together interested parties to create a series of recommendations for tagging content in a manner that will allow it to be more easily reused. I wonder whether individual publishers will be the ones to implement the recommendations in their internal tagging, or if it will be up to an aggregator (such as PMC) to act as the implementer (when they receive content and take it through their own conversion process)? I'm sure the first is intended, but might the second be more practical, once an organization can cite the recommendations (rather than making it up themselves)? Reviewer 2:The issue of JATS reusability is one that interests and challenges a wide audience, and it's good to see work being put in to improve ease of reuse - what a huge task! Many people would benefit from learning about the approaches your group is taking and suggestions you have for best practices. As far as suggestions for the paper itself, mainly, I just wanted a little more. Is the Reviewer 3:Among NLM DTD's initial design principles was the easy adaptability of all other However, once we overcome the initial hurdle of the legacy content, on-going content can and should attempt to be consistent for the sake of XML consumers down the line. Working with a permissive DTD, the only way you can lead users in the right direction is through "best practices" documentation and potentially, when all that effort hits prime time, through optional Schematron rules which enforce these best practices. There is long road ahead for the JATS4Reuse workgroup, but the effort will eventually pay off when by employing specific practices coming out of this group, JATS will not only facilitate archiving but also interchange. As a side-effect of this re-usability effort, the JATS4Reuse group may propose modifications and/or |
Thanks for posting the reviews Daniel. This is useful info to help shape the paper. |
I created a Google doc for this here: Improving the reusability of JATS. Right now it is not much more than a skeleton. Please hack away. |
Beginnings of the slides are here Needs work and input form other presenters! |
It would be nice to prepare a JATS4R contribution to JATS-Con.
Submissions are due by November 14:
http://jats.nlm.nih.gov/jats-con/forms/JATSsubmission.html .
That fits with our original plan of having something ready by Open Access Week, which is three weeks earlier.
Google doc for draft of our paper: Improving the reusability of JATS
The text was updated successfully, but these errors were encountered: