Preeliminar Presentation: semanticMedia.ppt
Example: “Find an image of John Smith (the one at www.cs.umd.edu/~jsmith) in which he is camping”
As multimedia content become more popular, people collect greater amounts of multimedia files, ranging from personal pictures to work-related presentations. As these collections grow they tend to do it in a unorganized fashion which makes them harder to use, (e.g. try looking for that particular picture of the ocean that you took during the summer vacation of 1998). On the other hand, we have already experimented the difficulties of manually marking up personal documents with semantic meaning for the computer. These brings the oportunity of linking these two tasks in a painless manner for the user. One single tool could be used to organize, mantain and publish multimedia documents annotated with semantic markup.
SemanticMedia is intended to be a basic application targeted to non-computer scientist mor knowledge engineers that allows users to do exactly what we describe above, in a basic but user-friendly fashion. Among the advantages of this kind of tool, besides the direct utility for personal users, is that they serve as an incentive for the creation of semantic content. Also future extensions of this tool would facilitate automatic inferencing and categorization of multimedia content.
Features:
Limitations:
Querying System for Online Images Based on the PNG Format and Embedded Metadata
Features
Limitations:
General architecture of the system:
The ontology is based on the ABC and MPEG7 Ontology.
ABC was motivated by the recognition that many existing metadata approaches are based on a resource-centric traditional cataloguing approach which assumes that the objects being described, and therefore their attributes, are more or less stable. Such an approach is inadequate for modeling the creation, evolution, transition, usage and rights of objects over time or for supporting advanced queries such as who was responsible for what, when and where?
MPEG-7 ontology to describe multimedia learning objects.
Some extensions were made to these ontologies. The final version of our ontology can be found here.
The server is implemented in java. Is a web server, it receives client requests for:
Then, it gives these requests to the reasoner, and presents the results back in a web page.
Architecture of Reasoner:
The Reasoner uses is DAMLJessKB, Jess and Jena and a Jess-DAML+OIL Translator. The reasoner receives a daml file; it translates these daml assertions to a jess format using DAMLJessKB (DAMLJessKB executes Jena as a parser). If the request is an addition to the KB, the facts are loaded to Jess and the persistent KB is updated (currently, the KB is stored in a txt file that stores the facts in jess format). If the request is a query, the query is presented to jess and a results file is produced in jess format. This jess-file is sent to the Jess-DAML+OIL Translator.
This is a Jess+DAML+OIL Translator, implemented in Java. Source code available here.
The daml files (original and output) seem different. But if we compare the Triple graph according to the RDF Validator, we can see that they are equivalent.
The full implementation including DAMLJessKb, Jena, Jess, can be found here.
Tools:
Ontologies and Standards:
Papers:
We welcome your suggestions.
Have you ever heard of
OntoLog? It uses RDF to markup audio and video. -- DavidMihalcik
Thanks, David. We'll look at it.