Please create an account to participate in the Slashdot moderation system


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 internet speed test! ×

Journal mdupont's Journal: Introspector announces ILDASM/Redland as next Milestone

The Introspector project has realigned itself with a new set of goals that are achievable. After more than a year of research into the semantic web and the dotgnu system, I have concluded that the main goals of the introspector can be reached much more quickly with much easier goals.

The original goal of the introspector was the extraction of metadata from the GCC. The DotNet system presents you with much more metadata then you could ever want.

The dotgnu/pnet system is GPLed and has tools to be able to disassemble, to assemble and run C/IL binaries from DotNet.

RDF is the cornerstone of the semantic web, Redland is an great library for processing RDF.

The new introspector module will allow you to convert your IL code into RDF for semantic markup and also to be able to assemble RDF back into dot net binaries.

The later versions will also allow the tracing of the execution of your programs in rdf.

These features will unite the semantic web and the dotnet world. Programs and Executions can be treated as data, Data can be treated as Logical statements and fed into proof engines.

Also, you will be able to transform your rdf and xml files into the Introspector rdf for translation into binaries.

The end result will also be the ability to semantically mark up IL code for converting it into a new language, opening up a new world of semantic progamming to DotNet.

See the simple plan here :

See the Original kick off here :

This discussion has been archived. No new comments can be posted.

Introspector announces ILDASM/Redland as next Milestone

Comments Filter:

(1) Never draw what you can copy. (2) Never copy what you can trace. (3) Never trace what you can cut out and paste down.