Here are all statements that are under one line
- 1 Interfaces
- 2 DataRepository
- 3 Declaration management
- 4 DataExtraction
- 5 Used Projects
- 6 RDF
- 7 Ontology
- 8 Used On Projects
- 9 Vizualization
- 10 OUTPUT
Introspector interfaces are Import and export routines that allow RDF statements to be extracted from InternalDataStructures? of programs.
We will build interfaces to the following projects for data extraction
[CLanG C] [CPlusPlus C++], ObjectiveC and JavaLang support from the GccProject http://gcc.gnu.org/
[CsharpLang C#], [MicrosoftIntermediateLang MSIL] and other language support via the DotGnuProject http://www.gnu.org/projects/dotgnu/
Glade is just one of the many forms that can be imported into Luxor http://luxor-xul.sourceforge.net/
The data repository will be a distributed RDFServer that stored and indexes the RDFFiles.
The Representation of the knowledge extracted by the introspector is simple : It is a list of identifiers, labels, ids. Things that have a semantic assigned to them, or that may be assigned to semantics. These things are nodes, items, blocks. Basically they are the foundation of knowledge. http://www.burningchrome.com/archives/unrev-ii/msg01818.html
the user should be able to declare new identifiers, replace them, and import and export them from the system
We need ways for users to declare new data structures. The data declarations of the introspector provide a common naming system for all related tools
we need new tools to extract RDF metdata out of various other systems. We support many different file formats for the introspector. more to come here, TODO : add a table of file formats We need to be able to dump out tabular text files of various names and types in the system. Depends on the QuerySystem? Doxygen like HTML output is important. We will support various XML format inputs and outputs. The main focus is moving towards RDF, because of the power of the rdf notation. But Using RDF to annotate XML trees make sense for representing the object structure.
NTriples are even simpler than n3. http://www.w3.org/2001/sw/RDFCore/ntriples/
I would like to use the BootLib? http://www.boost.org/
The introspector needs to be acessable from the bash command line.
The emacs interface promises many integration tools
* Rdf is appropiate for the introspector because of its simple syntax.
* The nodes of the compiler are naturally graphs.
* Rdf allows for information about resources to be added in when it is needed.
* MetaData is naturally stored in RDF.
* Rdf allows for the Ontology and Structure of the data to be added in after the fact.
I use Redland http://www.redland.opensource.ac.uk/ Redland is a RDF application framework with many SwigLanguageBindings?. http://www.redland.opensource.ac.uk/ We use redland to interface with C modules.
I have posted the first version of the introspector ontology here http://introspector.sourceforge.net/2003/08/16/introspector.n3 please review
Used On Projects
On this node, you can find examples of introspected projects :
The visualization tools will be Built upon the following ToolChain :
* Data Extraction of statements from the subject
* Data filtering of only relevant information from the program
* Breaking down the data set into pages and subgraphs
* Conversion of the statements to nodes and arcs
* emitting of the graph to the graph layout language * invoking of the layout engine
* importing the results of the layout
* creation of a planar graph
* drawing of that graph
* allowing the editing of the graph by the user
* exporting of the graph to other systems.
* saving of the graph data as a resource in the introspector
It should be easy for a user to create new code generators
Graph Layout Tools vcg graphvis tulip xvpodb and more
Petal2Dia : see this http://mail.gnome.org/archives/dia-list/2002-November/msg00111.html AutoDia is a great module from Arron http://droogs.org/autodia/