|
CS 6795 Semantic Web Techniques |
|
|
Projects |
|
|
|
|
|
Choose one to three other persons in the
class as partners and propose a project topic. Please select your partner(s) and your
first, second and third choice of possible projects from the list below. We will allocate according to all preferences
and will allow justified modifications to the assigned topics. The project will consist of a written
report and a class presentation in which all partners will participate
equally. Each project asks you to
consider a tool (or a system of tools) to solve a problem, and to apply it to
a specific problem or task. It may ask
you to extend the range of the tool. Please answer the following questions in
your write up: What problem area does the tool address? Exactly what does the tool do? What are the
characteristics of an ideal solution to problems in this area? Does the tool offer an effective solution
to such problems? Why? Why not? Did the tool help you solve your chosen
problem/task? What other tools might have been applied? What other work and
ideas in the area are relevant? What extensions to the tool might be worth
considering? In addition, follow any
specific documentation hints in the description for your selected project. The written Project Report shall be about 5
single-spaced pages per participant, and should be built around key high-level
specification segments and examples (at least one simple, one medium-hard,
and one hard example). Please do NOT copy material from the Web (use citations
or point with URLs instead). The introduction should be short (maximally 3
sentences of ‘generalities’), quickly focus on how the approach of
the project relates to previous work, and preview the actual work being done.
The main documentation should start with an architecture overview (e.g., using
a diagram) and proceed to more and more specifics. The conclusions should
summarize the contributions and indicate what (immediate) future work could
be done. Appendices can be used for any medium-size (up to 3 pages each) specification
modules (in higher-level languages, e.g.
in Prolog, POSL, N3, RDFS, XML, XSD, RNC, RIF Presentation Syntax, OWL 2 Functional-Style
Syntax, ANTLR, or XSLT), test cases, sample I/O dialogs, and user guides / installation
instructions. Since such appendices can alternatively be separate files uploaded
at other parts of the Project Website, they do not count for the Project Report
page limit. In the part about how to use the implemented system, a small
number of (up to 3) half-page screenshot may be helpful (but are not
required). Longer (more than 3 pages each) code listings etc. (in programming languages, e.g. in Python, Java, C#, or
C++) must be uploaded separately on the Project Website (complete code
listings and implementation details are mandatory). The Project Report will
be assessed according to these criteria:
Quality of the work, effectiveness of the use of the tool, clarity of
the ideas presented, quality of the writing (grammar, spelling, organization,
formatting, references), ability to look beyond the
tool(s) and to discuss the problem and tool extensions. What you present in class will be based on
slides and a demo. Each project will
have 5 minutes of presentation per participant followed by 5 minutes of
questions from the audience and discussion for the entire project. Please prepare a one-page ‘virtual
handout’ that at the same time is a website entry page. It contains
just the main points of your project – a page we can view later to remind
ourselves of the ideas presented; perhaps present them over a tea/coffee to
our colleagues; and something that incites people to click on the specific
pages of your documentation website.
This virtual handout/entry page, like a poster, will be more effective
if it uses an eye-catcher and clearly presents just the main ideas, and not
every detail and nuance (these should be linked). Please upload all results of your work on
some of your UNB website(s): virtual handout/entry page, demo sources and
examples, presentation slides, as well as
written report. Weighting: Written 60%, Presentation 30%,
Handout 10%. Team members will receive
the same mark for the written report and virtual handout, but not necessarily
for the presentation. Fall 2011
Projects | Fall 2010 Projects | Fall 2009 Projects | Fall 2007 Projects | Fall 2006
Projects | Fall 2005 Projects | Fall 2002-4 Projects |
|
|
|
|
|
|
|
Maintained by Harold Boley