1<!DOCTYPE html> 2<!--[if lt IE 8 ]><html class="no-js ie ie7" lang="en"> <![endif]--> 3<!--[if IE 8 ]><html class="no-js ie ie8" lang="en"> <![endif]--> 4<!--[if (gte IE 8)|!(IE)]><!--><html class="no-js" lang="en"> <!--<![endif]--> 5<head> 6 7<!--- Basic Page Needs 8 ================================================== --> 9<meta charset="utf-8"> 10<title>Linguistic Linked Open Data</title> 11<meta name="description" content=""> 12<meta name="author" content=""> 13 14<!-- Mobile Specific Metas 15 ================================================== --> 16<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1"> 17 18<!-- CSS 19 ================================================== --> 20<link rel="stylesheet" href="css/default.css"> 21<link rel="stylesheet" href="css/layout.css"> 22<link rel="stylesheet" href="css/media-queries.css"> 23 24<!-- Script 25 ================================================== -->
26<script src="js/modernizr.js"></script>
vendor: 2 bytes, line 26
26
27<script src="http://ajax.googleapis.com/ajax/libs/jquery/2.1.1/jquery.min.js"></script>
27 28 29<!-- Favicons 30 ================================================== --> 31<link rel="shortcut icon" href="favicon.ico" > 32 33</head> 34 35<body> 36 37<!-- Header 38 ================================================== --> 39<header> 40 41 <div class="row"> 42 43 <div class="twelve columns"> 44 45 <!-- <div class="logo"> 46 <a href="index.html"><img alt="" src="images/logo.png"></a> 47 </div>--> 48 49 <nav id="nav-wrap"> 50 51 <a class="mobile-btn" href="#nav-wrap" title="Show navigation">Show navigation</a> 52 <a class="mobile-btn" href="#" title="Hide navigation">Hide navigation</a> 53 54 <ul id="nav" class="nav"> 55 56 <li class="current"><a href="/">Home</a></li> 57 <!--<li><span><a href="blog.html">Blog</a></span> 58 <ul> 59 <li><a href="blog.html">Blog Index</a></li> 60 <li><a href="single.html">Post</a></li> 61 </ul> 62 </li> 63 <li><span><a href="portfolio-index.html">Portfolio</a></span> 64 <ul> 65 <li><a href="portfolio-index.html">Portfolio Index</a></li> 66 <li><a href="portfolio.html">Portfolio Entry</a></li> 67 </ul> 68 </li>--> 69 <li ><a href="/about">About</a></li> 70 <li ><a href="/llod-cloud">LLOD Cloud</a></li> 71 <!--<li><a href="contact.html">Contact</a></li> 72 <li><a href="styles.html">Features</a></li>--> 73 74 </ul> <!-- end #nav --> 75 76 </nav> <!-- end #nav-wrap --> 77 78 </div> 79 80 </div> 81 82</header> <!-- Header End --> 83 <section id="intro"> 84 85 <!-- Flexslider Start--> 86 <div id="intro-slider"> 87 88 <div class="row"> 89 <div class="twelve columns"> 90 <div class="slider-text"> 91 <h1>Linguistic Linked Open Data<span>.</span></h1> 92 <p>Information about the current status of the growing cloud 93 of linguistic linked open data.</p> 94 </div> 95 </div> 96 </div> 97 </div> <!-- Flexslider End--> 98 99 </section> <!-- Intro Section End--> 100 101 <!-- Diagram Section 102 ================================================== --> 103 <section id="llod-diagram"> 104 105 <div class="row"> 106 107 <div id="diagram" class="align-center"> 108 <a href="llod-cloud"> 109 <object type="image/svg+xml" data="//lod-cloud.net/clouds/linguistic-lod.svg"> 110 <img src="https://lod-cloud.net/clouds/linguistic-lod.png"/> 111 </object> 112 </a> 113 <h2><b><a href="llod-cloud">Interactive and Previous Versions</a></b></h2> 114 </div> 115 </div> 116 117 </section> <!-- Tweet Section End--> 118 119 120 <!-- Info Section 121 ================================================== --> 122 <section id="info"> 123 <div class="row"> 124 <div class="twelve columns align-center"> 125 <h1>What is LLOD?</h1> 126 </div> 127 128 129 <div class="twelve columns"> 130 <p> 131 <b>Linguistic Linked Open Data</b> is a movement about publishing 132data for linguistics and natural language processing using the following principles: 133 </p> 134 <ul class="disc"> 135 <li>Data should be <em class="blue">openly</em> license using licenses such as 136the <a href="https://creativecommons.org/">Creative Commons</a> licenses.</li> 137 <li>The elements in a dataset should be uniquely identified by 138 means of a <em class="blue">URI</em>.</li> 139 <li>The <em class="blue">URI</em> should resolve, so users 140 can access more information using web browsers.</li> 141 <li>Resolving an LLOD resource should return results using <em class="blue">web 142 standards</em> such as HTML, <a href="http://www.w3.org/RDF/">RDF</a> or <a href="http://json-ld.org/">JSON-LD</a> (Content Negotiation 143 may be used to show different versions to different users).</li> 144 <li><em class="blue">Links to other resources</em> should be included to help users 145 discover new resources and provide semantics.</li> 146 </ul> 147 148 <p>The primary benefits of LLOD have been <a href="http://www.springer.com/cda/content/document/cda_downloaddocument/9783642317811-c1.pdf">identified</a> as:</p> 149 150 <ul class="disc"> 151 <li><em class="blue">Representation</em>: Linked graphs are a more 152 flexible representation format for linguistic data</li> 153 <li><em class="blue">Interoperability</em>: Common RDF models can 154 easily be integrated</li> 155 <li><em class="blue">Federation</em>: Data from multiple sources 156 can trivially be combined</li> 157 <li><em class="blue">Ecosystem</em>: Tools for RDF and linked 158 data are widely available under open source licenses</li> 159 <li><em class="blue">Expressivity</em>: Existing vocabularies 160 such as <a href="http://www.w3.org/2001/sw/wiki/OWL">OWL</a>, 161 <a href="http://lemon-model.net">lemon</a> and 162 <a href="http://persistence.uni-leipzig.org/nlp2rdf/">NIF</a> help 163 express linguistic resources.</li> 164 <li><em class="blue">Semantics</em>: Common links express what you 165 mean.</li> 166 <li><em class="blue">Dynamicity</em>: Web data can be continuously 167 improved.</li> 168 </ul> 169 170 </div> 171 </div> 172 173 </section> <!-- Info Section End-->
173 174 175 176 <!-- Works Section 177 ================================================== --> 178 <section id="works"> 179 180 <div class="row"> 181 182 <div class="twelve columns align-center"> 183 <h1>Resources for LLOD.</h1> 184 </div> 185 186 <div id="portfolio-wrapper" class="bgrid-quarters s-bgrid-halves"> 187 188 <div class="columns portfolio-item"> 189 <div class="item-wrap"> 190 <a href="http://linguistics.okfn.org"> 191 <img alt="" src="images/okfn.jpg"> 192 <div class="overlay"></div> 193 <div class="link-icon"><i class="fa fa-link"></i></div> 194 </a> 195 <div class="portfolio-item-meta"> 196 <h5><a href="portfolio.html">OKFN</a></h5> 197 <p>The Open Linguistics Working Group (OWLG)</p> 198 </div> 199 </div> 200 </div> 201 202 <div class="columns portfolio-item"> 203 <div class="item-wrap"> 204 <a href="http://www.lider-project.eu/"> 205 <img alt="" src="images/lider.png"> 206 <div class="overlay"></div> 207 <div class="link-icon"><i class="fa fa-link"></i></div> 208 </a> 209 <div class="portfolio-item-meta"> 210 <h5><a href="portfolio.html">LIDER</a></h5> 211 <p>Linked Data as an Enabler for Enterprise</p> 212 </div> 213 </div> 214 </div> 215 216 <div class="columns portfolio-item s-first"> 217 <div class="item-wrap"> 218 <a href="http://ldl2015.linguistic-lod.org/"> 219 <img alt="" src="images/ldl2015.jpg"> 220 <div class="overlay"></div> 221 <div class="link-icon"><i class="fa fa-link"></i></div> 222 </a> 223 <div class="portfolio-item-meta"> 224 <h5><a href="portfolio.html">LDL-2015</a></h5> 225 <p>The 4<sup>th</sup> Workshop on Linked Data in Linguistics (Beijing, July 2015).</p> 226 </div> 227 </div> 228 </div> 229 230 <div class="columns portfolio-item"> 231 <div class="item-wrap"> 232 <a href="http://linghub.lider-project.eu/"> 233 <img alt="" src="images/linghub.png"> 234 <div class="overlay"></div> 235 <div class="link-icon"><i class="fa fa-link"></i></div> 236 </a> 237 <div class="portfolio-item-meta"> 238 <h5><a href="portfolio.html">LingHub</a></h5> 239 <p>Linguistic Metadata Repository</p> 240 </div> 241 </div> 242 </div> 243 244 </div> 245 246 </div> 247 248 </section> <!-- Works Section End--> 249 250 <!-- Journal Section 251 ================================================== --> 252 <section id="journal"> 253 254 <div class="row"> 255 <div class="twelve columns align-center"> 256 <h1>More information about LLOD.</h1> 257 </div> 258 </div> 259 260 <div class="blog-entries"> 261 262 <!-- Entry --> 263 <article class="row entry"> 264 265 <div class="entry-header"> 266 267 <div class="permalink"> 268 <a href="http://wiki.okfn.org/Working_Groups/Linguistics/How_to_contribute"><i class="fa fa-link"></i></a> 269 </div> 270 271 <div class="ten columns entry-title pull-right"> 272 <h3><a href="http://wiki.okfn.org/Working_Groups/Linguistics/How_to_contribute">How to contribute to the LLOD cloud.</a></h3> 273 </div> 274 275 <div class="two columns post-meta end"> 276 <p> 277 <!--<time datetime="2014-01-31" class="post-date" pubdate="">Jan 31, 2014</time>
278 <span class="dauthor">By Sakura Haruno</span>--> 279 OWLG 280 </p> 281 </div> 282 283 </div> 284 285 <div class="ten columns offset-2 post-content"> 286<!-- <p> 287 If you wish to contribute to the linguistic linked data cloud and have your resource included in the cloud you must satisfy the following requirements. These requirement are derived from <a href="http://richard.cyganiak.de/2007/10/lod/#how-to-join">Richard Cyganiak and Anja Jentzsch</a>. 288 <a class="more-link" href="http://wiki.okfn.org/Working_Groups/Linguistics/How_to_contribute">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p>--> 289 <p> 290 If you wish to contribute to the linguistic linked data cloud and have your resource included in the cloud, please fill in the form at <a href="https://lod-cloud.net/add-dataset">LOD Cloud</a></p> 291 </div> 292 293 </article> <!-- Entry End --> 294 295 296 297 <!-- Entry --> 298 <article class="row entry"> 299 300 <div class="entry-header"> 301 302 <div class="permalink"> 303 <a href="http://www.w3.org/2015/09/bpmlod-reports/bilingual-dictionaries/"><i class="fa fa-link"></i></a> 304 </div> 305 306 <div class="ten columns entry-title pull-right"> 307 <h3><a href="http://www.w3.org/2015/09/bpmlod-reports/bilingual-dictionaries/">Guidelines for Linguistic Linked Data Generation: Bilingual Dictionaries</a></h3> 308 </div> 309 310 <div class="two columns post-meta end"> 311 <p> 312 BPMLOD 313 </p> 314 </div> 315 316 </div> 317 318 <div class="ten columns offset-2 post-content"> 319 <p> 320 This document guides the process of creating a linked data (LD) 321 version of a lexical resource, particularly a bilingual 322 dictionary. It contains advice on the vocabularies selection, 323 RDF generation process, and publication of the results. 324 <a class="more-link" href="http://www.w3.org/2015/09/bpmlod-reports/bilingual-dictionaries/">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p> 325 </div> 326 327 </article> <!-- Entry End --> 328 329 <!-- Entry --> 330 <article class="row entry"> 331 332 <div class="entry-header"> 333 334 <div class="permalink"> 335 <a href="http://www.w3.org/2015/09/bpmlod-reports/multilingual-dictionaries/"><i class="fa fa-link"></i></a> 336 </div> 337 338 <div class="ten columns entry-title pull-right"> 339 <h3><a href="http://www.w3.org/2015/09/bpmlod-reports/multilingual-dictionaries/">Guidelines for Linguistic Linked Data Generation: Multilingual Dictionaries (BabelNet).</a></h3> 340 </div> 341 342 <div class="two columns post-meta end"> 343 <p> 344 <!--<time datetime="2014-01-31" class="post-date" pubdate="">Jan 31, 2014</time> 345 <span class="dauthor">By Sakura Haruno</span>--> 346 BPMLOD 347 </p> 348 </div> 349 350 </div> 351 352 <div class="ten columns offset-2 post-content"> 353 <p> 354The process of creating a Linked Data (LD) version of a lexical resource, in particular BabelNet, is describe in these guidelines. These guidelines contain advice on the vocabularies selection, RDF generation process and publication of the results. This document describes the models used and the design decisions taken during the conversion of BabelNet into the well-known lemon representation. More in general, we will describe common patterns that naturally emerge when converting a lexical resource into RDF format. 355 <a class="more-link" href="http://www.w3.org/2015/09/bpmlod-reports/multilingual-dictionaries/">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p> 356 </div> 357 358 </article> <!-- Entry End --> 359 360 <!-- Entry --> 361 <article class="row entry"> 362 363 <div class="entry-header"> 364 365 <div class="permalink"> 366 <a href="http://www.w3.org/2015/09/bpmlod-reports/multilingual-terminologies/"><i class="fa fa-link"></i></a> 367 </div> 368 369 <div class="ten columns entry-title pull-right"> 370 <h3><a href="http://www.w3.org/2015/09/bpmlod-reports/multilingual-terminologies/">Guidelines for Linguistic Linked Data Generation: Multilingual Terminologies (TBX).</a></h3> 371 </div> 372 373 <div class="two columns post-meta end"> 374 <p> 375 <!--<time datetime="2014-01-31" class="post-date" pubdate="">Jan 31, 2014</time>
376 <span class="dauthor">By Sakura Haruno</span>--> 377 BPMLOD 378 </p> 379 </div> 380 381 </div> 382 383 <div class="ten columns offset-2 post-content"> 384 <p>This document describes proposed best practices for transforming multilingual terminologies, particulary those available in TBX format, into a Linked Data version. The best practices are exemplified using the well-known IATE resource. The document describes the models and vocabularies to be used and describes the conversion using a running example. 385 <a class="more-link" href="http://www.w3.org/2015/09/bpmlod-reports/multilingual-terminologies/">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p> 386 </div> 387 388 </article> <!-- Entry End --> 389 390 <!-- Entry --> 391 <article class="row entry"> 392 393 <div class="entry-header"> 394 395 <div class="permalink"> 396 <a href="http://bpmlod.github.io/report/nif-corpus/index.html"><i class="fa fa-link"></i></a> 397 </div> 398 399 <div class="ten columns entry-title pull-right"> 400 <h3><a href="http://bpmlod.github.io/report/nif-corpus/index.html">Guidelines for Linked Data corpus creation using NIF.</a></h3> 401 </div> 402 403 <div class="two columns post-meta end"> 404 <p> 405 <!--<time datetime="2014-01-31" class="post-date" pubdate="">Jan 31, 2014</time> 406 <span class="dauthor">By Sakura Haruno</span>--> 407 BPMLOD 408 </p> 409 </div> 410 411 </div> 412 413 <div class="ten columns offset-2 post-content"> 414 <p>This document describes best practices to follow for the generation of Linked Data text corpora, using the NLP Interchange Format (NIF). NIF is an RDF/OWL-based format that aims to achieve interoperability between NLP tools, language resources and annotations. It can be used to assign URIs to strings and annotate the resulting resources. The Brown corpus serves as example throughout these guidelines. 415 <a class="more-link" href="http://bpmlod.github.io/report/nif-corpus/index.html">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p> 416 </div> 417 418 </article> <!-- Entry End --> 419 420 <!-- Entry --> 421 <article class="row entry"> 422 423 <div class="entry-header"> 424 425 <div class="permalink"> 426 <a href="http://bpmlod.github.io/report/NIF-based-NLP-WebServices/index.html"><i class="fa fa-link"></i></a> 427 </div> 428 429 <div class="ten columns entry-title pull-right"> 430 <h3><a href="http://bpmlod.github.io/report/NIF-based-NLP-WebServices/index.html">Guidelines for developing NIF-based NLP services.</a></h3> 431 </div> 432 433 <div class="two columns post-meta end"> 434 <p> 435 <!--<time datetime="2014-01-31" class="post-date" pubdate="">Jan 31, 2014</time> 436 <span class="dauthor">By Sakura Haruno</span>--> 437 BPMLOD 438 </p> 439 </div> 440 441 </div> 442 443 <div class="ten columns offset-2 post-content"> 444 <p> 445 This document describes best practices to follow for the implementation of RESTful NLP web services that rely on the NLP Interchange Format (NIF). âNIF is an RDF/OWL-based format that aims to achieve interoperability between NLP tools language resources and annotations.â As a proof-of-concept, we have implemented NIF wrappers for the Stanford POS tagger and Stanford parser. 446 <a class="more-link" href="http://bpmlod.github.io/report/NIF-based-NLP-WebServices/index.html">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p> 447 </div> 448 449 </article> <!-- Entry End --> 450 451 <!-- Entry --> 452 <article class="row entry"> 453 454 <div class="entry-header"> 455 456 <div class="permalink"> 457 <a href="http://bpmlod.github.io/report/LLD-Exploitation/index.html"><i class="fa fa-link"></i></a> 458 </div> 459 460 <div class="ten columns entry-title pull-right"> 461 <h3><a href="http://bpmlod.github.io/report/LLD-Exploitation/index.html">Guidelines for LLD exploitation.</a></h3> 462 </div> 463 464 <div class="two columns post-meta end"> 465 <p> 466 <!--<time datetime="2014-01-31" class="post-date" pubdate="">Jan 31, 2014</time>
467 <span class="dauthor">By Sakura Haruno</span>--> 468 BPMLOD 469 </p> 470 </div> 471 472 </div> 473 474 <div class="ten columns offset-2 post-content"> 475 <p>This best practice describes how to exploit Linguistic Linked Data resources. The suggested steps for exploitation comprise: search and discovery of relevant resources, verifying the license of the dataset, navigating to the distribution of the data (download or SPARQL endpoint), extraction of the data that is relevant for a particular purpose or application. 476 <a class="more-link" href="http://bpmlod.github.io/report/LLD-Exploitation/index.html">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p> 477 </div> 478 479 </article> <!-- Entry End --> 480 481 <!-- Entry --> 482 <article class="row entry"> 483 484 <div class="entry-header"> 485 486 <div class="permalink"> 487 <a href="http://bpmlod.github.io/report/LLOD-aware-services/index.html"><i class="fa fa-link"></i></a> 488 </div> 489 490 <div class="ten columns entry-title pull-right"> 491 <h3><a href="http://bpmlod.github.io/report/LLOD-aware-services/index.html">LLOD aware services.</a></h3> 492 </div> 493 494 <div class="two columns post-meta end"> 495 <p> 496 <!--<time datetime="2014-01-31" class="post-date" pubdate="">Jan 31, 2014</time> 497 <span class="dauthor">By Sakura Haruno</span>--> 498 BPMLOD 499 </p> 500 </div> 501 502 </div> 503 504 <div class="ten columns offset-2 post-content"> 505 <p>This document recommends best practices for building Linguistic Linked Open Data (LLOD) aware web services. LLOD denotes the representation of linguistic resources in accordance with linked data principles. These principles include that entities are to be identified by HTTP URIs providing RDF-based information about the entity including links to related entities. LLOD-aware services consume, process and produce such resources. LLOD-aware services are services that consume resources available as Linked Data as Input and output an RDF resource that can in turn be published as Linked Data. 506 <a class="more-link" href="http://bpmlod.github.io/report/LLOD-aware-services/index.html">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p> 507 </div> 508 509 </article> <!-- Entry End --> 510 511 512 <!-- Entry --> 513 <article class="row entry"> 514 515 <div class="entry-header"> 516 517 <div class="permalink"> 518 <a href="http://lemon-model.net/learn/5mins.php"><i class="fa fa-link"></i></a> 519 </div> 520 521 <div class="ten columns entry-title pull-right"> 522 <h3><a href="http://lemon-model.net/learn/5mins.php">Getting started with lemon.</a></h3> 523 </div> 524 525 <div class="two columns post-meta end"> 526 <p> 527 <!--<time datetime="2014-01-31" class="post-date" pubdate="">Jan 31, 2014</time> 528 <span class="dauthor">By Sakura Haruno</span>--> 529 lemon-model.net 530 </p> 531 </div> 532 533 </div> 534 535 <div class="ten columns offset-2 post-content"> 536 <p> 537 Lemon is an RDF model for representing lexical information relative to ontologies. This guides helps you get starte with using the <em>lemon</em> model. 538 <a class="more-link" href="http://lemon-model.net/learn/5mins.php">Read More<i class="fa fa-arrow-circle-o-right"></i></a></p> 539 </div> 540 541 </article> <!-- Entry End --> 542 543 544 </div> <!-- Entries End --> 545 546 </section> <!-- Journal Section End--> 547 <!-- footer 548 ================================================== --> 549 <footer> 550 551 <div class="row"> 552 553 <div class="twelve columns"> 554 555<!-- <ul class="footer-nav"> 556 <li><a href="#">Home.</a></li> 557 <li><a href="#">Blog.</a></li> 558 <li><a href="#">Portfolio.</a></li> 559 <li><a href="#">About.</a></li> 560 <li><a href="#">Contact.</a></li> 561 <li><a href="#">
561Features.</a></li> 562 </ul>--> 563 564<!-- <ul class="footer-social"> 565 <li><a href="#"><i class="fa fa-facebook"></i></a></li> 566 <li><a href="#"><i class="fa fa-twitter"></i></a></li> 567 <li><a href="#"><i class="fa fa-google-plus"></i></a></li> 568 <li><a href="#"><i class="fa fa-linkedin"></i></a></li> 569 <li><a href="#"><i class="fa fa-skype"></i></a></li> 570 <li><a href="#"><i class="fa fa-rss"></i></a></li> 571 </ul>--> 572 573 <ul class="copyright"> 574 <li>Copyright © 2018 <a href="http://www.insight-centre.org/">Insight Centre for Data Analytics</a> at <a href="http://www.nuigalway.ie">National University of Ireland Galway</a></li> 575 <li>Site maintained by <a href="mailto:[email protected]">John P. McCrae</li> 576<!-- <li>Copyright © 2015 <a href="http://www.lider-project.eu/">LIDER project</a></li> --> 577 <li>Based on Sparrow theme from <a href="http://www.styleshout.com/">Styleshout</a></li> 578 </ul> 579<center> 580 <img src="/images/Insight-LOGO1.png" width="150px" style="padding-right:20px;"/> 581 <img src="/images/NUI_Galway_BrandMark_A_500.png" width="150px"/> 582</center> 583 584 </div> 585 586 <div id="go-top" style="display: block;"><a title="Back to Top" href="#">Go To Top</a></div> 587 588 </div> 589 590 </footer> <!-- Footer End--> 591 592 <!-- Java Script 593 ================================================== --> 594
594<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.min.js"></script>
594 595
595<script>window.jQuery || document.write('
595<script src="js/jquery-1.10.2.min.js"><\/script>')</script>
595 596
596<script type="text/javascript" src="js/jquery-migrate-1.2.1.min.js"></script>
596 597 598
598<script src="js/jquery.flexslider.js"></script>
598 599
599<script src="js/doubletaptogo.js"></script>
599 600
600<script src="js/init.js"></script>
600 601 602</body> 603 604</html> 605
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.