Hi!
Björn> I am rather new to this whole smi and mib stuff, so this question Björn> might be stupid: Björn> When converting RFC1213-MIB to xml with smidump (libsmi 0.4.1), the Björn> status attribute values in the resulting xml file are always equal to Björn> "current", though they should equal "mandatory" since RFC-1213 refers Björn> to SMIv1 (RFC1155) and not to SMIv2 (RFC2578). And why is status an Björn> attribute while access is a child node?
Björn> Have I gotten something completely wrong?
No, your questions are definetely not stupid. :-) However, the answers are probably not completely helpful to you...
1. The xml output driver in smidump is no longer being developed. We came to a point where we thought, that XML Schema definitions are the right representation of MIBs in the XML world, since they describe not information per se, but a grammar that in turn describes management instance data. Hence, there might be some representations in the xml output that are not perfectly reasonable but also not further developed. Sorry for this bad news. However, we would be willing to accept diff-style patches that lead to a better XML represenation. :-)
2. (For what we had in mind) a generated XML representation should be reasonable for XML applications. We did not just want to have an XML representation of SMI MIB modules. If we would want to develop applications that handle SMI MIB module items, then we would simply use the libsmi API and not convert it to XML with `smidump -f xml' and develop an XML application that again parses the XML representation. Thus we intended to end up with a non-ambiguous XML representation, accepting the fact that SMIv1/v2 differences are not reflected.
-frank
PS: Please note that RFC 1213 is updated by newer SMIv2 MIBs and SMIv1 in general is obsoleted by SMIv2 which is the representative Full Standard these days.