The nodeset does not have all inverse references by design (the files are large enough as it is there is no justification for adding redundant information).

An application that imports a nodeset is expected to add inverse reverses when appropriate.

And how is an application that imports a nodeset, whether this published one or any other nodeset that conforms to the schema, supposed to know what "when appropriate" is?

Importers need to have rules based on ReferenceTypes.

i.e. always add inverse references except for:
TypeDefinition, HasModellingRule

You can look at the LoadPredefinedNodes function in the .NET Server Samples

Agreed to move this to Part 6 and add the rules stated for creating reverse references to the appendix that describes the nodeset

Added text to F.3 in 1.03 DRAFT 2

Agreed to changes in Carros meeting.