Property:Processing error message
Jump to navigation
Jump to search
"Processing error message" is a predefined property containing a textual description of an error and is provided by Semantic MediaWiki. This property is pre-deployed (also known as special property) and comes with additional administrative privileges but can be used just like any other user-defined property.
A
Property "Has DataCatalouge" (as page type) with input value "{{{Catalogue}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has PositiveAspects" (as page type) with input value "The approach has several advantages over
existing methods such as ease of experimentation, incoherence
mitigation during the alignment process, and
the incorporation of a-priori confidence values.
In cases
where training data is not available, weights set manually
by experts still result in improved alignment quality.
The framework is not only useful for aligning concepts and
properties but can also include instance matching. For this
purpose, one would only need to add a hidden predicate
modeling instance correspondences. The resulting matching
approach would immediately benefit from probabilistic
joint inference, taking into account the interdependencies
between terminological and instance correspondences." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has future work" (as page type) with input value "The framework is not only useful for aligning concepts and properties but can also include instance matching. For this purpose, one would only need to add a hidden predicate modeling instance correspondences. The resulting matching
approach would immediately benefit from probabilistic joint inference, taking into account the interdependencies between terminological and instance correspondences." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has Requirements" (as page type) with input value "{{{Requirements}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Uses Methodology" (as page type) with input value "{{{Methodology}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has abstract" (as page type) with input value "In this contribution a system is presented, which provides access to distributed data sources using Semantic Web technology. While it was primarily designed for data sharing and scientific collaboration, it is regarded as a base technology useful for many other Semantic Web applications. The proposed system allows to retrieve data using SPARQL queries, data sources can register and abandon freely, and all RDF Schema or OWL vocabularies can be used to describe their data, as long as they are accessible on the Web. Data heterogeneity is addressed by RDF-wrappers like D2R-Server placed on top of local information systems. A query does not directly refer to actual endpoints, instead it contains graph patterns adhering to a virtual data set. A mediator finally pulls and joins RDF data from different endpoints providing a transparent on-the-fly view to the end-user. The SPARQL protocol has been defined to enable systematic data access to remote endpoints. However, remote SPARQL queries require the explicit notion of endpoint URIs. The presented system allows users to execute queries without the need to specify target endpoints. Additionally, it is possible to execute join and union operations across different remote endpoints. The optimization of such distributed operations is a key factor concerning the performance of the overall system. Therefore, proven concepts from database research can be applied." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has motivation" (as page type) with input value "{{{Motivation}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has Subproblem" (as page type) with input value "{{{Subproblem}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has Results" (as page type) with input value "Because ARQ is using a pipelining concept the response time is very good, even
when data has to be retrieved from a remote data source." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has conclusion" (as page type) with input value "In this contribution a mediator-based system for virtual data integration based on SemanticWeb technology has been presented. The system is primarily developed for sharing scientific data, but because of its generic architecture, it is supposed to be used for many other Semantic Web applications. In this paper query federation based on SPARQL and Jena/ARQ has been demonstrated in detail and several concepts for query optimization which is currently on the agenda have been discussed. Additional contributions can be expected after the implementation of additional features mentioned before." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has PositiveAspects" (as page type) with input value "{{{PositiveAspects}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Proposes Algorithm" (as page type) with input value "{{{ProposesAlgorithm}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has Description" (as page type) with input value "For the following sample queries, real-world data of sunspot observations recorded at
Kanzelh¨ohe Solar Observatory (KSO) have been used. The observatory is also a partner
in the Austrian Grid project.
The queries are shown in Fig. 2. Query 1 retrieves the first name, the last name,
and optionally the e-mail address of scientists who have done observations. Query 2
retrieves all observations ever recorded by Mr. Otruba." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has relatedProblem" (as page type) with input value "{{{RelatedProblem}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has ExperimentSetup" (as page type) with input value "The tests were performed with the following setup: the mediator (and also the test client) where running on a 2.16 GHz Intel Core 2 Duo with 2 GB memory and a 2 MBit link to the remote endpoints. All endpoints were simulated on the same physical host running two AMD Opteron CPUs at 1.6 GHz and 2 GB memory." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has Limitations" (as page type) with input value "{{{Limitations}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has NegativeAspects" (as page type) with input value "{{{NegativeAspects}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has Challenges" (as page type) with input value "{{{Challenges}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has future work" (as page type) with input value "Other future work will be the support for DESCRIBE-queries and IRIs as subjects. In
future, the mediator should also use an OWL-DL reasoner to infer additional types for
subject nodes specified in the query pattern. Currently, types have to be explicitly specified
for each BGP (more precisely for the first occurrence: the algorithm caches already
known types). OWL-DL constraints like for example a qualified cardinality restriction
on obs:byObserver with owl:allValuesFrom obs:Observer would allow
the mediator to deduce types of other nodes in the query pattern." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Property "Has abstract" (as page type) with input value "Links build the backbone of the Linked Data Cloud. With the steady growth in the size of datasets comes an increased need for end users to know which frameworks to use for deriving links between datasets. In this survey, we comparatively evaluate current Link Discovery tools and frameworks. For this purpose, we outline general requirements and derive a generic
architecture of Link Discovery frameworks. Based on this generic architecture, we study and compare the features of state-of the-art linking frameworks. We also analyze reported performance evaluations for the different frameworks. Finally, we derive insights pertaining to possible future developments in the domain of Link Discovery." contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.