This document discusses the key components of an RSS news aggregator project including the motivations, objectives, technical framework, and issues with existing keyword-based search approaches. It outlines the proposed solution of using concept maps and ontologies to represent news semantics and allow retrieval based on partial meaning matching rather than exact keyword matching. Details are provided on collecting news from RSS feeds, representing it based on user-submitted keywords, eliminating duplicates, and enabling semantic search through correlation computation between concept vectors.

2. 2

 Motivations
 Problem Definition
 Objectives - Project Goals

 Frame Work
 Model Description
 Problem Solving

 New Technology

3. 3
 They have to subscribe to various RSS feeds
 Aggregators has in general categories
 Categories can contain out of scope news as Mrs. “Monica
Lewinsky” news when viewing the politics category.
 Aggregators search results are based on keywords rather
than concepts, thus not all the top news are revealed.
 Search engines allow limited number of keywords. (e.g.
Google’s input string is limited to 2048 bytes and 10
individual words) By Eric Tholomé, Director, Developer Products *
* http://googlecode.blogspot.com/2009/08/well-earned-retirement-for-soap-search.html

4. 4

 Viruses & JavaScript's can be in the enclosure of the feed.

 RSS feeds has different versions
 News element can be included in more than RSS feed
 Two different news topics may refer to similar concept

 Searching with keywords is done linguistic toward keywords, plus
some other ranking algorithms - by Joseph Novak, Alberto Canas *
 End-users may not be able to describe their interest with few
keywords – by Joseph Novak, Alberto Canas *
* http://www.stanford.edu/dept/SUSE/projects/ireport/articles/concept_maps/The Theory Underlying Concept Maps.pdf

5. 5
 Collect news from various desired RSS feeds
 News represented from submitted keywords
 Retrieval is based on the concept of keywords
 Eliminate duplicates linguistically & semantically
 Retrieval by partial match of meaning rather than exact match of
keywords
Retrieve from
any RSS Feed
Retrieve and represent
by the semantics of keywords
Eliminate linguistically
And semantically duplicates
Retrieval by partial
meaning rather than
Keywords match

6. 6
Concept
map
User
Keywords
RDF
File
RSS Feeds OWL ontology
generator layer
RSS OWL
Ontology
MAIN Concept
OWL Ontology
Fuzzy Sensing Layer
Feature vectors
transformation
Semantic matching by
correlation computation
Write
Match
RDF
Jena
Store
API
Jena’s query
SPARQL API

7. 7
Concept map constriction
 Well constructed concept map characteristics by Joseph Novak *
 Convert concept map to XML
Owl ontology generator
Fuzzy sensing layer
Representation layer
* http://www.stanford.edu/dept/SUSE/projects/ireport/articles/concept_maps/The Theory Underlying Concept Maps.pdf

8. 8
Description
Describe the project in non-technical terms
Use following slides for discussing status,
schedules, budget, etc.
-for more info…
List location or contact for specification (or other related documents)

9. 9
Competitive Analysis
Competitors
 You may want to allocate one slide per competitor
Strengths
 Your strengths relative to competitors
Weaknesses
 Your weaknesses relative to competitors

10. 10
Competitive Analysis, Cont.
Competitors
 Strengths
 Weaknesses
-for more info…
List location or contact for competitive analysis (or other related documents)

11. 11
Technology
New technology being used
 Benefits
Standards being adopted
 Benefits
Standards specifically being ignored
 Drawbacks & benefits
DYA: define your acronyms!

12. 12
Team Resources
State assumptions about resources allocated to
this project
 People
 Equipment
 Locations
 Support & outside services
 Manufacturing
 Sales

13. 13
Procedures
Highlight any procedural differences from usual
projects of this type
Discuss requirements, benefits, and issues of using
new procedures
-for more info…
List location or contact for procedures document (or other related documents)

14. 14
Schedule
Review high-level schedule
-for more info…
List location or contact for detailed schedule (or other related documents)

15. 15
Current Status
High-level overview of progress against schedule
 On-track in what areas
 Behind in what areas
 Ahead in what areas
Unexpected delays or issues

16. 16
Related Documents
Marketing plan
 Location or contact name/phone
Budget
 Location or contact name/phone
Post-mortem
 Location or contact name/phone
Submit questions
 Location or contact name/phone