OntoNet 2009/06/12

Duc, Tom, Boon, Joe

Work has clear, useful, publishable divisions into three areas; lots of ramifications back and forth, but separates reasonably:

Ontologies: Domain, application, scenario knowledge, workloads, etc
- Duc will drive this area
- Develop usable ontologies, sample workloads and topologies
  - TITAN scenarios, Air Force, Sensors
  - Any non-militaristic domains? Anyone? Anyone? Bueller?
- Publishable: Development methodology, Wikipedia extraction, standards integration (e.g., sensors), competency/coverage/evaluation methods, domains/workloads
Reasoning: Matching and aggregation
- Joe will drive this area
- Matching and aggregation algorithms, implementations
- Publishable: Algorithms, implementations,
Networking: Dissemination, forwarding algorithms, simulation studies
- Tom will drive this area
- Developing core network protocol building blocks to leverage for OntoNet implementation, studying protocol network behaviors
- Studying ETX trees under mobility
- Comparing epidemic protocols vs SMF vs flood
- Potential significant code contributions to ns-3, research community
- Publishable: ETX tree performance under mobility; gossip performance/tradeoffs vs flood, SMF; relationship between Trickle snooping and CDS

Should both utilize TITAN/Groupwise project examples and contribute development/guidance back to those efforts

Will need all three parts integrated for full, comprehensive system

Publication goals

Multiple relevant deadlines in October w/ massive KR/AI/ontology conference co-location fest in Toronto next May:

To do:

Spend a couple minutes thinking about how to manage your bibliography; you don't want to be scrambling to write up BibTeX entries at the last minute, so at the least keep a list of those as you go. Google Scholar can help figure out venue given authors or titles, but it needs to be checked for LaTeX & extraction errors.
- Joe uses simple wiki pages
- Evan uses a complex mediawiki setup
- Kyle uses a blog
Read some introductory material about the Semantic Web; track down [1]
- If you log into the Drexel library proxy or access it via a Drexel IP (not ACIN), you should have full access to the CACM archives
Start reading on gossip/epidemic/anti-entropy protocols
- Track down & read [2], backburner [3] and [4] slightly for [5]
Start reading on ETX and network metrics
- Track down and read [5], then [6]
  - [6] is more commonly available as MobiCom paper, which is identical
Check out published PacketBB spec, start thinking about ETX-based tree construction and SMF in ns-3
Hop into ns-3 weekly IRC chat as available
Save the planet.

To do:

Track down:
- Gruninger and Fox. Methodology for the Design and Evaluation of Ontologies.
- Uschold. Building Ontologies: Towards a Unified Methodology.
- Fox and Gruninger. Ontologies and Enterprise Modelling.
- van der Vet and Mars. Bottom-Up Construction of Ontologies.
- Staab, Studer, Schnurr, Sure. Knowledge Processes and Ontologies.
We should look around for more recent papers on ontology development and knowledge engineering as well.
Check out main OWL reasoners/tools:
- Jena: Java RDF/OWL parser, includes rule engine for inference
- Pellet: Java tableau reasoner
- FaCT++: C++ tableau reasoner
- Racer: C++
Check out ontology development tools: Protege, SWOOP
- No pressure to use these...
Start thinking about scenario/domain ontologies
- Put down thoughts on TITAN based data/ontologies
- Sit down w/ Joe about sensor standards/SSHWG
- Sit down w/ Joe about Air Force example/Wikipedia extraction
Integration with or support of TITAN PDS/BCW/ICS efforts?

To do:

tjkopena's wiki
	Onto Net / 20090612	Edit Page \| Page History \| Wiki Help Print \| Search:

20090612