W3C | Semantic Web Case Studies
Case studies include descriptions of systems that have been deployed within an organization, and are now being used within a production environment. Use cases include examples where an organization has built a prototype system, but it is not currently being used by business functions. The list is updated regularly, as new entries are submitted to W3C. There is also an RSS1.0 feed that you can use to keep track of new submissions. Please, consult the separate submission page if you are interested in submitting a new use case or case study to be added to this list. (), by , , Activity area:Application area of SW technologies:SW technologies used:SW technology benefits: A short overview of the use cases and case studies is available as a slide presentation in Open Document Format and in PDF formats.
» Linked Data for the Uninitiated (Part 1) | DOCUMENTING CAPPADOCIA
This two-part post is my follow-up to LAWDI 2012, officially known as the first Linked Ancient World Data Institute. It brought together a multi-disciplinary group of digital scholars at NYU’s Institute for the Study of the Ancient World (ISAW) whose interests incorporate the Ancient Medierranean and Near East. This essay is cross-posted on the GC Digital Fellows blog The Linked Data Cloud as of September 2011. In preparation for LAWDI 2012, I wrote a post called “Linked Data: A Theory,” pondering the concepts behind Linked Data, but it was clear to me from the beginning that I needed a more sturdy vocabulary and concrete skills in order to put these ideas into practice. Linked Data is a philosophy applied to web development. Linked Data is often incorporated into conversations about Open Access, a crucial movement intended to counteract academia’s traditional exclusionary practices by making scholarship freely available to the public. Open Data How the Web Operates
Linked Data Basics for Techies - OpenOrg
Intended Audience This is intended to be a crash course for a techie/programmer who needs to learn the basics ASAP. It is not intended as an introduction for managers or policy makers (I suggest looking at Tim Berners-Lee's TED talks if you want the executive summary). It's primarily aimed at people who're tasked with creating RDF and don't have time to faff around. It will also be useful to people who want to work with RDF data. Please Feedback-- especially if something doesn't make sense!!!! If you are new to RDF/Linked Data then you can help me! I put a fair bit of effort into writing this, but I am too familar with the field! If you are learning for the first time and something in this guide isn't explained very well, please drop me a line so I can improve it. cjg@ecs.soton.ac.uk Warning Some things in this guide are deliberately over-simplified. Alternatives If you don't like my way of explaining things, then there's other introductions out there; (suggest more!) Structure Merging URI vs URL a
SPARQL 1.1 Protocol
4.1 Security There are at least two possible sources of denial-of-service attacks against SPARQL protocol services. First, under-constrained queries can result in very large numbers of results, which may require large expenditures of computing resources to process, assemble, or return. Another possible source are queries containing very complex — either because of resource size, the number of resources to be retrieved, or a combination of size and number — RDF Dataset descriptions, which the service may be unable to assemble without significant expenditure of resources, including bandwidth, CPU, or secondary storage. Since a SPARQL protocol service may make HTTP requests of other origin servers on behalf of its clients, it may be used as a vector of attacks against other sites or services. SPARQL protocol services may remove, insert, and change underlying data via the update operation. Different IRIs may have the same appearance.
The Linking Open Data cloud diagram
Linked Data: Evolving the Web into a Global Data Space
LOD2 | Interlinked Data
Seeing Standards
Poster of visualization (PDF, 36in x 108in) Metadata standard glossary, poster form (PDF, 36in x 41in) Metadata standard glossary, pamphlet form (PDF) The sheer number of metadata standards in the cultural heritage sector is overwhelming, and their inter-relationships further complicate the situation. This visual map of the metadata landscape is intended to assist planners with the selection and implementation of metadata standards. Each of the 105 standards listed here is evaluated on its strength of application to defined categories in each of four axes: community, domain, function, and purpose. The standards represented here are among those most heavily used or publicized in the cultural heritage community, though certainly not all standards that might be relevant are included. Content: Jenn Riley Design: Devin Becker Work funded by the Indiana University Libraries White Professional Development Award Copyright 2009-2010 Jenn Riley
sameAs
OntoWiki — Agile Knowledge Engineering and Semantic Web
CubeViz -- Exploration and Visualization of Statistical Linked Data Facilitating the Exploration and Visualization of Linked Data Supporting the Linked Data Life Cycle Using an Integrated Tool Stack Increasing the Financial Transparency of European Commission Project Funding Managing Multimodal and Multilingual Semantic Content Improving the Performance of Semantic Web Applications with SPARQL Query Caching
Une nouvelle norme pour le thésaurus (1) : Pourquoi une nouvelle no...
Linked Data Platform 1.0
5.1 Introduction This section is non-normative. Many HTTP applications and sites have organizing concepts that partition the overall space of resources into smaller containers. To which URLs can I POST to create new resources? This document defines the representation and behavior of containers that address these issues. This document includes a set of guidelines for creating new resources and adding them to the list of resources linked to a container. The following illustrates a very simple container with only three members and some information about the container (the fact that it is a container and a brief title): Example 1 # The following is the representation of # # @base < @prefix dcterms: < This example is very straightforward - there is the containment triple with subject of the container, predicate of ldp:contains and objects indicating the URIs of the contained resources. Example 2 Example 3 Example 4 Example 5
Protege Ontology Library
OWL ontologies Information on how to open OWL files from the Protege-OWL editor is available on the main Protege Web site. See the Creating and Loading Projects section of the Getting Started with Protege-OWL Web page. AIM@SHAPE Ontologies: Ontologies pertaining to digital shapes. Frame-based ontologies In the context of this page, the phrase "frame-based ontologies" loosely refers to ontologies that were developed using the Protege-Frames editor. Biological Processes: A knowledge model of biological processes and functions that is graphical, for human comprehension, and machine-interpretable, to allow reasoning. Other ontology formats Dublin Core: Representation of Dublin Core metadata in Protege.
