Explanations of the surveyed properties
Support for Semantic Web standards and schemas
Semantic Web standards used:
Which standards specific to the Semantic Web have been exploited in the project?
Schemas and ontologies used:
Which schemas and ontologies are used by the project?
Data access capabilities
supports heterogeneous data (yes or no):
the application uses data conforming to more then one schema, e.g. FOAF and RSS
supports data with diverse ownership (yes or no):
the application uses data which originated from more the one owner, e.g. two unrelated organisations, and some blogs
supports data form decentralised sources (yes or no):
(the application gets its data from mutliple physically distributed sources, e.g. one server in every departement)
supports updates to the data (offline/online/no):
the application allows updating the data.
offline: application has to shutdown to change data
online: data can be changed on-the-fly
Schema access capabilities
supports heterogeneous schemas (yes or no):
the application uses schemas which have been specified in different ways, e.g. a XML schema and an RDF Schema
supports schemas with diverse ownership (yes or no):
the application uses schemas which originated from different organisations, e.g. schemas from the W3C and from Microsoft
supports schemas form decentralised sources (yes or no):
the application uses schemas which are stored in different physically distributed places, e.g. a bio data schema stored and maintained in Japan, and chemical schema stored in Brazil.
supports updates to the schemas (offline/online/no):
the application allows updating the schema:
offline: application has to be shutdown to change the schema
online: the schema can be changed on-the-fly
Integration and alignment
How is data alignment and integration done (manually/automatic/semi-automatic/not needed):
if heterogenous data is supported, how is integration done?
manually: the data form the new source is edited by a human.
automatic: the data form the new source is integrated by using heuristics or any other means to avoid human inspection.
semi-automatic: after human inspection of the data from the new source, rules, scripts and other means are created to integrate the data.
not needed: all data sources use the same schema.
uses inferencing (Yes or no):
the application uses any form of inferencing to create new knowledge.
Supported content types
supports multimedia content (generally yes, generally no or specific kind of multimedia content):
the application supports any non-textual content, like pictures, audio or video files.
supports multilingual content (yes or no):
the application supports more then one language in its interface.
can additionally handle unstructured text (yes or no):
the application provides means to handle unstructutured text, e.g. some free form fields, and free form search
can additionally handle semi-structured text (Yes or no):
the application can handle text which incorporates some structured, but which may be deviating from a schema
Authoring support
is read only or allows editing (read only/editing):
Does the application enable the end-user to edit or write data?
enables collaboration between users (yes or no):
Does the application enable support between its different users?
Degree of openness
is an open system for external data (Yes or no):
the application provides means for importing or accessing external data, which is provided by the user.
preserves authorship and handles trust issues (yes or no):
the application keeps track of authorship, and/or employs a notion of trust.
supports mash-ups of the data (generally yes, generally no or specific kind of mashup):
the application supports mixing data form multiple sources on-the-fly.
exports data or is usable as source from other applications (yes or no):
the application allows exporting its data, or can be used as source by providing e.g. a SPARQL endpoint
uses semantics to be scalable (yes or no):
semantics are a key enabler of scalability for this project.
provides transport layer for semantic content (yes or no):
the application provides its own semantically enabled transport layer.
Implementation details
programming languages used:
Which concrete programming langagues have been used in the implementation?
libraries used:
Which concrete libraries have been used in the implementation?
Application classification:
these properties do not get filled in by the project authors, but by the people doing the survey,
as a result of the data of the individual project.
application domains:
In which specific domains does the application operate?
application type:
Which of the 6 application types, which are proposed in the master thesis, does this application implement?
functionality, which is based on semantics:
What application functionality would not be possible without semantics?
application architecture description:
short description of the overall architecture.
application architecture type:
which of the different architecture types, which are proposed in the master thesis, does this application implement?