The xml parser crash when loading a file with a Models tag

[levkevi]

When trying to load a file with a Models tag, the parser crash.

Here's an example file with the problematic tag.

models_are_problematic.txt

[levkevi]

It should be fixed in #363

[zerox1212]

Thanks. Do you know if there is a list of "non-node" XML tags in the spec somewhere?

[oroulet]

What are model tags? does anyone have documentation for that? Maybe this is where we should save xml files used as references? would be great for modeler

[levkevi]

I don't know but I compiled a data model file to a node file using this tool:

https://github.com/OPCFoundation/UA-ModelCompiler

You might find something looking at the code.

[oroulet]

What is a data model file?

On Wed, Nov 16, 2016, 15:16 levkevi notifications@github.com wrote:

I don't know but I compiled a data model file to a node file using this tool:

https://github.com/OPCFoundation/UA-ModelCompiler

You might find something looking at the code.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/FreeOpcUa/python-opcua/issues/362#issuecomment-260957227, or mute the thread https://github.com/notifications/unsubscribe-auth/ACcfzp8jN7rs4i9p0T8fIRvI5OvbNMyBks5q-xAqgaJpZM4KzFIi .

[zerox1212]

I think it's this: https://github.com/OPCFoundation/UA-ModelCompiler/blob/master/ModelCompiler/UA%20Model%20Design.xsd

Example: https://github.com/OPCFoundation/UA-.NET/blob/master/SampleApplications/Samples/Common/Sample/SampleDesign.xml

[levkevi]

I can confirm, this is the file that @zerox1212 linked.

You usually define your models using those files and then compile it to make the nodeset xml file (the file format the modeler uses)

[zerox1212]

Looks like OPC Foundation uses this model format to generate nodes and code (classes). Seems like a different approach than python modeler.

[oroulet]

What do you mean? The xsd defines the xml format. Is there another file somewhere?

On Wed, Nov 16, 2016, 23:14 Andrew notifications@github.com wrote:

Looks like OPC Foundation uses this model format to generate nodes and code (classes). Seems like a different approach than python modeler.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/FreeOpcUa/python-opcua/issues/362#issuecomment-261089604, or mute the thread https://github.com/notifications/unsubscribe-auth/ACcfzmNK0wNANH8q-aDaAhzFI62vgmIwks5q-4BSgaJpZM4KzFIi .

[bitkeeper]

Hard to find some information:

• The only real use of UAModelDesign so far looks in the OPCFoundation ModelCompiler (and even that tool generates also UANodeSet as output)
• Other tools use UANodeSet
• In https://opcfoundation.org/UA/schemas/1.02/UANodeSet.xsd the Models element is missing and in newer https://opcfoundation.org/UA/2011/03/UANodeSet.xsd it is present.
• Unknown if there are any tool for designing the model based on UAModelDesign ?

@levkevi what do you mean with 'you usually define your models ...' ? By hand or tool ?

Looks like the UAModelDesign is more 'object-oriented' approach of describing the namespace. More easy to parse; object/objectype contain its members as nested childs, instead of nodeid refs to other nodes.

[oroulet]

Does it specify nodeids too? I could not find any , and I am not an expert in xsd...

[levkevi]

@bitkeeper I was told that it was typed by hand.

@oroulet It doesn't specify the nodeid, you have to compile it with their tool (the one linked in their repo) to generate the Node file.