Data Portal @ linkeddatafragments.org

Matches in ScholarlyData for { ?s ?p ?o. }

• authorList hasItem item-3.
• authorList hasItem item-4.
• authorList hasLastItem item-4.
• item-1 type ListItem.
• item-1 hasContent tobias-kaefer.
• item-1 next item-2.
• item-2 type ListItem.
• item-2 hasContent juergen-umbrich.
• item-2 next item-3.
• item-2 previous item-1.
• item-3 type ListItem.
• item-3 hasContent aidan-hogan.
• item-3 next item-4.
• item-3 previous item-2.
• item-4 type ListItem.
• item-4 hasContent axel-polleres.
• item-4 previous item-3.
• 42 creator aidan-hogan.
• 42 creator axel-polleres.
• 42 creator birte-glimm.
• 42 creator markus-kroetzsch.
• 42 type InProceedings.
• 42 label "OWL: Yet to arrive on the Web of Data?".
• 42 sameAs 42.
• 42 abstract "Seven years on from OWL becoming a W3C recommendation, and two years on from the more recent OWL 2 W3C recommendation, OWL has still experienced only patchy uptake on the Web. Although certain OWL features (like owl:sameAs) are very popular, other features of OWL are largely neglected by publishers in the Linked Data world. This may suggest that despite the promise of easy implementations and the proposal of tractable profiles suggested in OWL’s second version, there is still no “right” standard fragment for the Linked Data community. In this paper, we (1) analyse uptake of OWL on the Web of Data, (2) gain insights into the OWL fragment that is actually used/usable on the Web, where we arrive at the conclusion that this fragment is likely to be a simplified profile based on OWL RL, (3) propose and discuss such a new fragment, which we call OWL LD (for Linked Data).".
• 42 hasAuthorList authorList.
• 42 isPartOf proceedings.
• 42 keyword "linked data".
• 42 keyword "owl 2 rl".
• 42 keyword "owl ld".
• 42 keyword "owl".
• 42 keyword "semantic web".
• 42 title "OWL: Yet to arrive on the Web of Data?".
• authorList type List.
• authorList hasFirstItem item-1.
• authorList hasItem item-1.
• authorList hasItem item-2.
• authorList hasItem item-3.
• authorList hasItem item-4.
• authorList hasLastItem item-4.
• item-1 type ListItem.
• item-1 hasContent birte-glimm.
• item-1 next item-2.
• item-2 type ListItem.
• item-2 hasContent aidan-hogan.
• item-2 next item-3.
• item-2 previous item-1.
• item-3 type ListItem.
• item-3 hasContent markus-kroetzsch.
• item-3 next item-4.
• item-3 previous item-2.
• item-4 type ListItem.
• item-4 hasContent axel-polleres.
• item-4 previous item-3.
• 5 creator arnaud-le-hors.
• 5 creator martin-nally.
• 5 creator steve-speicher.
• 5 type InProceedings.
• 5 label "Linked Data Basic Profile for Application Integration".
• 5 sameAs 5.
• 5 abstract "Linked Data, as defined by Tim Berners-Lee’s 4 rules, is usually associated with the Semantic Web but it also represents an opportunity to address some of the integration challenges the IT industry has been wrestling with for many years in a new way which is more powerful and which is based on open standards. In the context of the Semantic Web which aims at creating a web of data similar to the web of documents, Linked Data is used to expose information on the Internet in a machine readable format which conveys the semantic of the data along with the data itself. This approach provides a powerful infrastructure for publishing information such as public records and the processing of that information by various types of applications. These applications include search engines, which can return more accurate results and reasoning engines, which can infer new information from the one being exposed. Such examples include pharmaceutical applications as well as the now famous IBM Watson system that defeated the best Jeopardy champions. But IBM has been using Linked Data as an architectural model and implementation technology for application and service integration in various domains including Application Lifecycle Management (ALM) and Integration System Management (ISM). This paper explains why Linked Data, which builds on the existing World Wide Web infrastructure, presents some unique characteristics, such as being distributed and scalable, that may allow the industry to succeed where other application integration approaches have failed. It discusses lessons we have learned along the way and some of the challenges we have been facing in using Linked Data to integrate enterprise applications. Finally, we discuss several areas that could benefit from additional standard work and discuss several commonly applicable usage patterns along with proposals on how to address them using the existing W3C standards in the form of a Linked Data Basic Profile. This includes techniques applicable to clients and servers that read and write linked data, a type of container that allows new resources to be created using HTTP POST and existing resources to be found using HTTP GET (analogous to things like Atom Publishing Protocol).".
• 5 hasAuthorList authorList.
• 5 isPartOf proceedings.
• 5 keyword "Linkeddata".
• 5 keyword "alm".
• 5 keyword "application_integration".
• 5 keyword "enterprise_application".
• 5 keyword "standards".
• 5 keyword "usage_patterns".
• 5 title "Linked Data Basic Profile for Application Integration".
• authorList type List.
• authorList hasFirstItem item-1.
• authorList hasItem item-1.
• authorList hasItem item-2.
• authorList hasItem item-3.
• authorList hasLastItem item-3.
• item-1 type ListItem.
• item-1 hasContent arnaud-le-hors.
• item-1 next item-2.
• item-2 type ListItem.
• item-2 hasContent martin-nally.
• item-2 next item-3.
• item-2 previous item-1.
• item-3 type ListItem.
• item-3 hasContent steve-speicher.
• item-3 previous item-2.
• 6 creator giovanni-bartolomeo.
• 6 creator stefano-salsano.
• 6 type InProceedings.
• 6 label "A Spectrometry of Linked Data".
• 6 sameAs 6.
• 6 abstract "Entity mining is still a troublesome open problem. In past years many approaches served to automate equivalence links generation using schema matching or various heuristics based on the recognition of similar property values. Using the equivalences already deployed in the Linked Data cloud, we introduce a methodology to detect and analyze the composition of clusters of coreferences mostly representative of an entity for the Linked Data community.".
• 6 hasAuthorList authorList.
• 6 isPartOf proceedings.
• 6 keyword "Entity".
• 6 keyword "Identity".
• 6 keyword "Linked Data".
• 6 title "A Spectrometry of Linked Data".
• authorList type List.
• authorList hasFirstItem item-1.

• first
• previous
• next