Randy proposed something here:
http://www.opcfoundation.org/forum/viewtopic.php?p=15659#15659

I agree what he has proposed there but we should have something in the spec about this issue to allow generic applications to follow some rules or at least best practice.

Matthias will create a proposal where for each Namespace of the namespace array there is an object with meta data which can contain things like a version number and the type of nodes represented by the namespace (e.g. standard information model, types / instances etc.)
BrowseName could be namespace index for the namespace index part and the URI for the string part.

Proposal should

• Provide a namespace meta data object per namespace
• Provide a folder with namespace meta data below server object
• Meta data object should contain
  • Version
  • Static (Flag)
  • Type (Flag)
  • Instance (Flag)
• Meta data object is detected through browse name
  • ns index = namespace index
  • text = namespace URI

The namespace meta data object can provide methods to import / export XML files for a namespace

Uploaded proposal to Sharepoint
Shared Documents/UA Specifications/Drafts for Review v1.2
OPC UA Part 5 - Information Model 1.02.17 Body MD.doc

We should move this mantis issue to Part 5!

We need to discuss where to put the instances to. I proposed three possible options in a comment.

I sent a Part 5 update with the discussed changes to Wolfgang for integration into his latest Part 5 version.

Fixed in version 1.02.19 of PART 5.

Mantis issue needs to be moved tp Part 5!!!

Reopened to move to part 5

Fixed in version 1.02.20

Reviewed, edited and agreed to in telecon today.