Re: (CL Net SNMP) cl-net-snmp without ZEBU

[Chun T. (binghe) <bin...@gm...>]

Hi,

>
>>>       This works great.  Obviously MIP parsing is desirable, but so
>>> many of my other tools don't bother that its easy to use the  
>>> OIDs.  I
>>> keep lists of the things myself in several tools.
>>
>> I decide throw ZEBU and switch to other LALR parser tools. On
>> LispWorks, I can use the "parsergen" tool which shiped with LW, and
>> for other Lisps, the cl-yacc and cl-lexer can work.
>
>        Is ASN.1 parsable with a META parser, or is it too tricky?

Sorry, not quite know about "META" parser, I'm newbie in this area.

I've read most of ASN.1 specifications, it's too complex, even the  
subset use by SNMP. At begin I want to write a ASN.1 compiler which  
"transform" ASN.1 type definitions into CLOS and Lisp code which do  
encode/decode, but soon found it's too hard for me. So now I only get  
SNMP Object ID definitions from SNMP MIB files, this can be done by a  
pure LALR parser.

>
>
>> The most important part of my design is A expert system built on
>> KnowledgeWorks(R) or LISA (lisa.sourceforge.net), and ResearchCyc. I
>> want to use AI theory to detect whether/when a remote device is  
>> health
>> or not, then give SA alerts (SMS, Mail, GTalk, ...) and even  
>> operation
>> advice... In this part, OPS5/CLIPS_like forward-chain rules is more
>> fit than the Prolog_like backward-chain rules. The GBBopen project  
>> may
>> also be used to solve something...
>
>        I agree that LISA or some similar tool would be very useful
> here.  My main interest in PROLOG is that I find it (or rather,
> unification) is a really nice database.  With careful rules you can
> extract data in sophisticated ways I find more pleasant than
> SQL+postprocessing.

There's a book called "Knowledge Representation" by John F. Sowa. I  
suggest you read it (if haven't)

PROLOG is good for backward-chain logic, which can basically be  
expressed by SQL's VIEW. (And a forward-chain logic can be expressed  
as SQL's TRIGGER) The problem is: you cannot write all your "data" in  
PROLOG source code files, as many FACTs, there must be a external  
storage for PROLOG logic engine to get/put FACTs.

So far as I know, SWI-Prolog can use facts which be stored in SQL  
databases by a ODBC interface. And LispWorks' KnowledgeWorks(R) can  
use CommonSQL to access data in SQL databases. For LISA, don't know  
that.  If you choose a PROLOG or other similar tools to do a SA job,  
it's better to choose one which can support external data source.

>
>
>> A little crazy, like you? ^_^
>
>        It's uncanny!  Except for a few technology choices (I favor
> Hunchentoot over CL-HTTP), we want to do a lot of the same things.

The Web interface part is not the key part, use whatever is good.

I do not have a full plan but just write part by part from bottom to  
top, it's the Lisp way to do a big project.

>
>
> --
> wm
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> CL-Net-SNMP-General mailing list
> CL-...@li...
> https://lists.sourceforge.net/lists/listinfo/cl-net-snmp-general