forked from BioSchemas/bioschemas.github.io
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
124 lines (114 loc) · 9.15 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
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
---
redirect_from:
- projects/
- review/
- examples/
- about/
layout: default
---
<div id="landing" itemscope itemtype="http://schema.org/Organization">
<meta itemprop="logo" content="http://bioschemas.org/images/square_logo2.png"/>
<meta itemprop="url" content="http://bioschemas.org"/>
<meta itemprop="email" content="[email protected]"/>
<meta itemprop="name" content="Bioschemas Community"/>
<div class="container-flow">
<div class="alert alert-success" role="alert">
<i class="fas fa-exclamation-circle"></i> COVID-19 <br/>
Please see the following links for details of COVID-19 responses involving Schema.org:
<ul>
<li>To aid data discovery on COVID-19, we have released 5 updated profiles:
<ul>
<li><a href='/profiles/ChemicalSubstance'>ChemicalSubstance</a></li>
<li><a href='/profiles/Gene'>Gene</a></li>
<li><a href='/profiles/MolecularEntity'>MolecularEntity</a></li>
<li><a href='/profiles/Protein'>Protein</a></li>
<li><a href='/profiles/Taxon'>Taxon</a></li>
</ul>
</li>
<li>Schema extended to include <a href="https://schema.org/CovidTestingFacility">CovidTestingFacility</a>. See <a href="http://blog.schema.org/2020/03/schema-for-coronavirus-special.html">blog post</a> for details.</li>
<li>Galaxy now includes Schema markup for their tools. See this <a href="https://github.com/galaxyproject/galaxy/pull/9261">pull request</a> for details.</li>
</ul>
</div>
<div class="row">
<div class="col-md-8">
<h1>What is Bioschemas?</h1>
<p>Bioschemas aims to improve the Findability of data in the life sciences. It does this by encouraging people in the life sciences to use Schema.org markup in their websites so that they are indexable by search engines and other services. Bioschemas encourages the consistent use of markup to ease the consumption of the contained markup across many sites. This structured information then makes it easier to discover, collate, and analyse distributed data.
</p>
<p>Bioschemas is making two main contributions:</p>
<ol>
<li>Proposing <a href="/types">new types and properties</a> to Schema.org to allow for the description of life science resources.</li>
<li><a href="/specifications">Profiles</a> over the Schema.org types that identify the essential properties to use in describing a resource.</li>
</ol>
<p>
Bioschemas started as a community effort in November 2015. It operates as an open community initiative with <a href="/people/">representatives</a> from a wide variety of institutions. You are welcome to <a href="/howtojoin/">join the community</a>.</p>
<h2>Schema.org</h2>
<p>
<a href="https://schema.org">Schema.org</a> is a community effort supported by the main search engines, and is already widely implemented across the web.
</p>
<p>
Schema.org provides a way to add semantic markup to web pages. It describes ‘types’ of information, which then have ‘properties’. The types are things that we can talk about and the properties are the things that we can say about the type.
For example, <a href="https://schema.org/Event">Event</a> is a type that has properties like <a href="https://schema.org/startDate">startDate</a>, <a href="https://schema.org/endDate">endDate</a>, and <a href="https://schema.org/description">description</a>.</p>
<p>If types or properties needed in the life sciences are missing, then Bioschemas is developing proposals for <a href="/types">new types and properties</a> to be included into Schema.org.
</p>
<h2>Bioschema Profiles</h2>
<p>To simplify the marking up of web resources, and to provide consistency of markup within the life sciences community, Bioschemas are defining <a href="/specifications">profiles</a> over types that state which properties must be used (minimum), should be used (recommended), and could be used (optional). The profiles also state the cardinality of usage of a property, and identify domain ontologies to use for the value of properties.</p>
<p>For example, if we look at the <a href="https://schema.org/Dataset">schema.org/Dataset</a> type there are over 90 properties available to use. The <a href="/specifications/Dataset/"> Bioschemas profile over Dataset</a> brings this down to a more manageable number, with 5 mandatory properties and 8 recommended properties. Many of the other properties have little relevance for a Dataset. The dataset markup properties that Bioschemas specifies as mandatory will also make them findable by <a href="/software/index.html#googleDatasetSearch">Google's Dataset Search tool</a>.</p>
<p>The Bioschemas community are defining profiles over relevant existing Schema.org types, e.g. <a href="/specifications/DataCatalog/">DataCatalog</a>, <a href="/specifications/drafts/Course/">Course</a>, and <a href="/specifications/Tool/">SoftwareApplication</a>, and over the new types being defined for the life sciences, e.g. <a href="/specifications/Gene/">Gene</a>, <a href="/specifications/Protein/">Protein</a>, <a href="/specifications/Taxon/">Taxon</a>.</p>
<h2>Funding</h2>
<p>
The Bioschemas Community have received funding through the ELIXIR-EXCELERATE grant and ELIXIR Implementation Studies. Full details of funding can be on our <a href="/funders/">funding page</a>.
</p>
<img style="max-width: 60%;" src="/images/excelerate_whitebackground.png"/>
<img style="max-width: 30%; float: right;" src="/images/Elixir-logo.png"/>
</div>
<div class="col-md-4 right-column">
<section class="upcoming-events">
<h3>Upcoming events</h3>
{% assign sorted_meetings = site.meetings | sort: 'start_date' %}
{% assign count = 0 %}
{% for meeting in sorted_meetings %}
{% assign currentDate = site.time | date: '%F' %}
{% assign meetingDate = meeting.start_date | date: '%F' %}
{% assign endDate = meeting.end_date | date: '%F' %}
{% if currentDate <= meetingDate %}
<div class="event" itemscope itemtype="http://schema.org/Event">
<strong><a href="{{ meeting.url }}"><span class="title" itemprop="name">{{ meeting.name}}</span></a></strong>{% if meeting.tbc %} <span class="badge badge-warning">TBC</span>{% endif %}
<p> <strong>{{ meeting.dates }}</strong> </p>
<p>
<span itemprop="location">{{ meeting.venue }}</span>
</p>
<meta itemprop="startDate" content="{{meeting.start_date}}"/>
<meta itemprop="endDate" content="{{ meeting.end_date }}"/>
</div class="event">
{% assign count = count | plus: 1 %}
{% elsif meetingDate <= currentDate and currentDate <= endDate %}
<div class="event" itemscope itemtype="http://schema.org/Event">
<strong><a href="{{ meeting.url }}"><span itemprop="name">{{ meeting.name}}</span></a></strong>{% if meeting.tbc %} <span class="badge badge-warning">TBC</span>{% endif %}
<p> <strong>{{ meeting.dates }}</strong> </p>
<p>
<span itemprop="location">{{ meeting.venue }}</span>
</p>
<meta itemprop="startDate" content="{{meeting.start_date}}"/>
<meta itemprop="endDate" content="{{ meeting.end_date }}"/>
</div class="event">
{% assign count = count | plus: 1 %}
{% endif %}
{% if count == 3 %}
{% break %}
{% endif %}
{% endfor %}
</section>
<hr>
<section>
<h3>Latest presentation</h3>
<iframe src="https://docs.google.com/presentation/d/e/2PACX-1vQGjhnyEOSTpLstq0dl85HUwT554Ph-4OdyGMCt6fzMwxTLlP2hDKt8E8fArN7eNbRRX3IFANGCkuOP/embed?start=false&loop=false&delayms=3000" frameborder="0" width="350" height="225" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe>
</section>
<hr>
<section>
<a class="twitter-timeline" data-height="450" data-theme="light" data-link-color="#2BB673" href="https://twitter.com/BioSchemas?ref_src=twsrc%5Etfw">Tweets by BioSchemas</a>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
</section>
</div>
</div>
</div>
</div>