The old-website from jats4r

Validator should report when an uploaded file is not well-formed

Right now, if you try to upload garbage, the validator happily reports that there are no problems.

List of organisations currently participating in JATS4R

change the wording on the left column and above the list of organizations on the site to "participating" as in: "List of organisations currently participating in JATS4R"?

Request from HW before we can add the logo to the site.

[CLOSED] updated xsl files - and added jats4r-infolevel-0.xsl which is the same a...

Issue by jeffbeckncbi
Friday Jan 23, 2015 at 14:29 GMT
Originally opened as https://github.com/JATS4R/validation/pull/6

...s jats4r-errlevel-0.xsl but reports all errors, warnings, and info statements instead of just errors

jeffbeckncbi included the following code: https://github.com/JATS4R/validation/pull/6/commits

Test validator in Firefox and other browsers

Issue by hubgit
Friday Jan 23, 2015 at 15:53 GMT
Originally opened as https://github.com/JATS4R/validation/issues/7

Allow the user to choose the validation level

Issue by hubgit
Friday Jan 23, 2015 at 15:54 GMT
Originally opened as https://github.com/JATS4R/validation/issues/8

May involve using a particular stylesheet or passing particular variables into the transformation.

open policy language for the digital commons group

http://www.w3.org/community/odrl/

Anyone heard of this group?
Should we be co-ordinating with them re our Licence recommendations?

Logos for participating organizations

Add twitter follow button

[CLOSED] Try to get validator running under Saxon CE

Issue by Klortho
Wednesday Nov 05, 2014 at 16:12 GMT
Originally opened as https://github.com/JATS4R/validation/issues/3

Better results presentation for the validator

This is a nice-to-have, but it came up at JATS-Con, so I want to record it here.

It would be nice if the messages that get reported could be interleaved with the actual source document. Off the top of my head, the one way I can think to do this would be to re-serialize the document on the fly, and keep track of where we are in the dom tree. When the xpath expression in the error message matches the node we are on, insert the message there.

The (big) drawback of this approach is that the serialized version of the document won't match exactly what they uploaded. There is no way for us to know, post-parsing, small lexical things like whitespace and, for example, whether single- or double-quotes were used for attribute values. Users might be confused by this.

Site redesign

UPDATE: See this site redesign wiki page for this sub-project's info.

Our site leaves a lot to be desired. I happened on a site today that I like a lot: http://todogroup.org, and I'd like to copy it, with style tweaks here and there as needed.

Need better feedback when the validator is busy

I got this feedback from a participant at JATS-Con. She tried out the validator with a very large file, and wasn't sure whether or not the thing was still working. Then, tried to switch to a different file, and wasn't sure if it was still working on the old file, or what.

To the extent possible, we should try to give the user better feedback on what's going on internally.

Produce XML/JATS learning resource

This is a placeholder for the discussion on the jats-admin list, Potential topics for XML learning -- to come up with some "getting started" resources for those new to JATS.

Accessibility issues for new wp site

Need a new logo for the site (and a tagline)

@Melissa37 mentioned that James could help us design a new logo.

[CLOSED] Jb branch

Issue by jeffbeckncbi
Thursday Jan 22, 2015 at 21:56 GMT
Originally opened as https://github.com/JATS4R/validation/pull/5

Updates to the license ERROR and WARNING tests based on discussions at the 2015-01-22 call.

If :
there MUST be a ;
there SHOULD be a .

If
it MUST be a 4-digit number.

jeffbeckncbi included the following code: https://github.com/JATS4R/validation/pull/5/commits

[CLOSED] update documentation to provide command line examples

Issue by IanMulvany
Wednesday Nov 19, 2014 at 13:22 GMT
Originally opened as https://github.com/JATS4R/validation/issues/4

I'm showing my relative ignorance here, as I'm very new to XSLT, I don't know how to run a validation.

From the documentation available at this blog post: http://blog.eight02.com/2011/05/validating-xml-with-iso-schematron-on.html I downloaded saxon9he.jar and then tried to run the following command:

➜ validation git:(master) ✗ java -jar saxon9he.jar -o:output.xsl -s:jats4r-errlevel-0.sch
No stylesheet file name

I freely admit that i don't know what I'm doing here, so perhaps some command line examples might help people like me?

[CLOSED] new xsl for error and warning messages

Issue by jeffbeckncbi
Wednesday Apr 01, 2015 at 20:48 GMT
Originally opened as https://github.com/JATS4R/validation/pull/10

jeffbeckncbi included the following code: https://github.com/JATS4R/validation/pull/10/commits

[CLOSED] Update Schematron files

Issue by jeffbeckncbi
Friday Mar 27, 2015 at 20:34 GMT
Originally opened as https://github.com/JATS4R/validation/pull/9

updated schematron files and generated XSL files with latest decisions

jeffbeckncbi included the following code: https://github.com/JATS4R/validation/pull/9/commits

[CLOSED] Try to get running under

Issue by Klortho
Wednesday Nov 05, 2014 at 16:12 GMT
Originally opened as https://github.com/JATS4R/validation/issues/2

Set up Google Analytics

We have some JS boilerplate code in our index.html page, but it is from the original site that we copied this look/feel from.

[CLOSED] Cosmetic changes: reformating schematrons

Issue by Klortho
Wednesday Apr 01, 2015 at 21:30 GMT
Originally opened as https://github.com/JATS4R/validation/pull/11

Hey, Jeff,
I worked on this a little bit today -- I am trying to put together instructions for how somebody else might use the schematrons without any prior infrastructure setup. I couldn't help myself, and gave all the schematrons a cosmetic once-over, here: just formatting and indenting.
Please take a look and merge this, if you don't mind the changes. Then, make sure you do a git pull in your local working repository so that you get these changes.
Thanks!

Klortho included the following code: https://github.com/JATS4R/validation/pull/11/commits

[CLOSED] Work on automating and documentation the validation procedures

Issue by Klortho
Thursday Apr 02, 2015 at 19:28 GMT
Originally opened as https://github.com/JATS4R/validation/pull/12

Here's a summary of the changes I made here:

I included a lot of third party library files in the lib subdirectory, so that somebody can get up and running with ease
I created two shell scripts:
- setup.sh needs to be run whenever you want to start working, on any new terminal window
- process-schematron.sh - to convert the schematrons into xslts
In order to automate the process-schematron, I changed the names of the output files a little bit to be more consistent. So, for example, jats4r-errlevel-0.xsl is now jats4r-level-errors-0.xsl. The "input-type" comes first (in this case, "level") and the "phase" comes last (in this case, "errors").
Finally, I reran my script, in order to regenerate the outputs. Note that my script uses different versions of some of the libraries than were used previously, so there might be some significant differences in the XSLT output. I tested them minimally, but not very thoroughly.

Klortho included the following code: https://github.com/JATS4R/validation/pull/12/commits

[CLOSED] branch test

Issue by jeffbeckncbi
Wednesday Oct 22, 2014 at 01:12 GMT
Originally opened as https://github.com/JATS4R/validation/pull/1

update to test branching

jeffbeckncbi included the following code: https://github.com/JATS4R/validation/pull/1/commits

jats4r / old-website Goto Github PK

old-website's People

Contributors

Stargazers

Watchers

Forkers

old-website's Issues

Recommend Projects

Recommend Topics

Recommend Org