forked from JATS4R/old-website
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
48 lines (38 loc) · 2.73 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
<!doctype html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="chrome=1">
<title>JATS4R - JATS for Reuse</title>
<link rel="stylesheet" href="stylesheets/styles.css">
<link rel="stylesheet" href="stylesheets/pygment_trac.css">
<script src="javascripts/scale.fix.js"></script>
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<!--[if lt IE 9]>
<script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
<div class="wrapper">
<header>
<p class="header"><img src="images/jats4rlogo.png" alt="JATS4R - JATS for Reuse"></p>
<p class="header">JATS for Reuse</p>
<ul>
<li><a class="buttons github" href="https://github.com/JATS4R"> GitHub Profile </a></li>
</ul>
</header>
<section>
<h3>
<a name="welcome-jats4r" class="anchor" href="#welcome-jats4r"><span class="octicon octicon-link"></span></a>Welcome to JATS4R</h3>
<p>JATS4R aims to help standardisation of xml used in scientific publishing workflows. We take specific areas of interest (such as licenses or author contributions) and work to define best practice tagging guidelines, along with tools that can help publishers identify whether their content is compliant with those best practices. </p>
<p>By doing this, we hope to make the research literature more accessible for data miners, and to lower costs when content needs to be exchanged or moved at scale, by bringing more consistency to the way the literature is tagged. </p>
<p>If you want to get involved, you can check out our <a href="https://groups.google.com/forum/#!forum/jats4r">mailing list</a>. Members can access our meeting notes in our <a href="https://drive.google.com/a/elifesciences.org/?tab=co#folders/0B2wDI5EMHiJ-anNYaV9hRHZ6dEE">Google Drive</a>. You can see examples of best practice tagging as they emerge under the JATS4R <a href="https://github.com/JATS4R">github organization</a>.</p>
Our <a href="images/JATS4Rworkflowplan.png">workflow</a> will be to iterate through a list of areas in JATS where we can improve tagging standards, agree on best practice, implement tools to help publishers identify whether their XML is compliant, disseminate best practice tagging gudielines, publish reports on compliance - where it can be determined, move to the next topic on the list. We are currently assembling our inital set of areas that we want to focus on, and we will publish those here.
</section>
<footer>
<p><small>Hosted on <a href="http://pages.github.com">GitHub Pages</a></small></p>
</footer>
</div>
<!--[if !IE]><script>fixScale(document);</script><![endif]-->
</body>
</html>