Frank Strauss wrote:

Hi!

Frank Fock writes:

Frank> I have implemented the SMI DTD v0.1 (which has expired for Frank> quite a while now) for my MIB Explorer product. Similar to Frank> smidump it can dump MIBs as XML. MIB Explorer supports Frank> SMIv1 and SMIv2 formats. SMIng is not supported. An Frank> example XML output can be found at Frank> http://www.mibexplorer.com/features/SNMP-NOTIFICATION-MIB.xml

[snip]

Yes. Just yesterday I've restarted to work on the document and to transform the DTD to an XML Schema. ;-) A work-in-progress version is at http://www.ibr.cs.tu-bs.de/projects/nmrg/draft-irtf-nmrg-smi-xml-01.txt. I send you this message just to let you know about this effort. The contained XML Schema is far from being complete and cleaned up.

I've made an attempt to replace your example's header by something like

<?xml version="1.0" encoding="US-ASCII"?>

<smi xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="smi.xsd">

and to check it with Xerces. I recognized a number of reported errors. But this may be due to errors in the Schema. I'll take a closer look later on.

Yes, you are right! I only checked whether the generated XML output was wellformed. I tried to validate it today with RXP and found some issues. I have fixed them and updated the (above) example. Now the example can be validated which shows that the DTD is valid too ;-)

There is also an online XML validator available which can be used for some testing: http://www.hcrc.ed.ac.uk/~richard/xml-check.html

Cheers, Frank

-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

Hi Frank,

Frank Strauss wrote:

I checked your example again using SAX2Count from Xerces against the current version of our XML Schema. There's just a minor issue that's not yet according to what the Schema says and the DTD `intends':

I must have missed the "create" attribute in the row element ;-)

There should be no `read-create' values for <access> elements. Instead, if a row can be created/deleted, the <row> element should have a `create="true"' attribute and the <access> elements should just contain the value `readwrite'.

I have fixed this now.

Furthermore, the <access> element values will be restricted in the XML Schema to the meaningful values `noaccess', `notifyonly', `readonly', and `readwrite', which we currently do not write with a hyphen.

I have used also 'notimplemented' for conformance refinements and 'writeonly' for SMIv1 MIBs.

Of course, this is just nit-picking at this point. I just wanted to let you know.

Thanks, it is always a good idea to do it the right way whenever possible!

Best regards, Frank

-- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.