The warnings must be reviewed:

• NodeId is not defined. References to node with NodeId: ns=1;i=37 is omitted during the import
• NodeId is not defined. References to node with NodeId: ns=1;i=39 is omitted during the import.
• NodeId is not defined. References to node with NodeId: ns=1;i=44 is omitted during the import.

After confirmation report using Mantis.

Contributes to #8

Release new version

• Update Readme files
• Create release front page
  • Getting Started
  • Version information
• Build solution to create deliverable and publish the installation package
• Update and publish the code help documentation
• Publish release
• Update the repository front page
• Update the GitHub pages documentation
• Close this issue and the parent milestone

Describe the bug

Looks like the generated DI model is missing some nodes.

To Reproduce

asp and using model compiler on the generated ASP

Expected behavior

<ObjectType SymbolicName="Prefix3:ConnectionPointType" Category="DI ConnectionPoint" BaseType="Prefix3:TopologyElementType" IsAbstract="true">
    <Description>Represents the interface (interface card) of a Device to a Network.</Description>
    <Children>
      <Object SymbolicName="Prefix3:NetworkAddress" TypeDefinition="Prefix3:FunctionalGroupType" ModellingRule="Mandatory">
        <Description>The address of the device on this network.</Description>
      </Object>
      <Object SymbolicName="Prefix3:ProfileIdentifier" TypeDefinition="Prefix3:ProtocolType" ModellingRule="MandatoryPlaceholder">
        <BrowseName>&lt;ProfileIdentifier&gt;</BrowseName>
      </Object>
    </Children>
    <References>
      <Reference>
        <ReferenceType>Prefix3:ConnectsTo</ReferenceType>
        <TargetId>Prefix3:NetworkIdentifier</TargetId>
      </Reference>
    </References>
    <ClassName />
  </ObjectType>

There is a reference on Prefix3:NetworkIdentifier but no definition of NetworkIdentifier.

NetworkIdentifier is defined in the source NodeSet file as

  <UAObject NodeId="ns=1;i=6599" BrowseName="1:&lt;NetworkIdentifier&gt;" SymbolicName="NetworkIdentifier" ParentNodeId="ns=1;i=6308">
    <DisplayName>&lt;NetworkIdentifier&gt;</DisplayName>
    <References>
      <Reference ReferenceType="HasTypeDefinition">ns=1;i=6247</Reference>
      <Reference ReferenceType="HasModellingRule">i=11508</Reference>
      <Reference ReferenceType="ns=1;i=6030" IsForward="false">ns=1;i=6308</Reference>
    </References>
  </UAObject>

Screenshots

Describe the problem

All recovered models must be tested against compliance with the Model Compiler.

Check out the current version of the Model Compiler 2.1.1-Bravo.

Describe the solution you'd like

To test you must prepare scripts calling the Model Compiler and executed them for all recovered models.
The preliminary script template shall be as follows

set COMPILER=OOI.ModelCompilerUI
"%1\%COMPILER%" -d2 "<ModelName>.xml" -cg "<ModelName>[.csv]" -o "<ModelName>" -console

Test the template using the selected model and review it if needed. All problems must be reported.

Partially it contributes to mertyusaatag#14.
Partially it contributes to mpostol/OPC-UA-OOI#653.

• IEC61850

The solution

Test existing models and recover ModelDesign stuff using asp.exe. It is an aggregating issue. Add models to be tested and mention this issue to provide crossreference.

Describe problem

The maml documentation must be added to the project of the Sandcastle Help File Builder.
The word documentation keep as is.

Describe the solution you'd like

There should be one common HTML documentation.

List of tasks to be accomplished

• Generate file
• Add the file to shfb project
• Regenerate the documentation

Contributes to mpostol/.github#11

The Internship is a continuation of my research addressing the Object-Oriented Internet concept. A more in-depth description you may find at Object Oriented Internet GitHub repository.

The Internship focus on selected topics related to Domain-Specific Languages, like validation, semantic diff, and conversion (translation). The work will be conducted against models gathered in this repository

I am expecting from contributors:

• to prepare and maintain the research environment
  • prepare scripts that allow automating the execution of existing command-line tools for the Windows operating system
  • using the prepared scripts and existing tools to convert models in the repository expressed in the UANodeSet to ModelDesign domain-specific language (detailed knowledge of the UANodeSet and ModelDesign language is not required)
  • using the prepared scripts and existing tools validate the models and report any errors if exist
• to manage the research results
  • create your fork of the repository UA-Nodeset
  • prepare appropriate scripts executing tools against all models gathered in the repository UA-Nodeset
  • pull request the results to the UA-Nodeset repository
• prepare a final description of the results

Describe problem

Selected models are to be tested using the mentioned version of the asp tool.

List of tasks to be accomplished

• DI
• ADI
• MachineVision

Scope

• create UAModelDesignerSolution.uamdsl files
• create *.aml files
• copy *.aml files to the docs folder
• add *.aml files to the existing on-line help documentation

additionally

• add documentation link to the README.md
• report any warning added to the *.log files
• check the foldes structure

Describe the problem

Check if online help documentation is working for each model. The link to the documentation is in the main README.md.

Contributes to #98

List of models that the task is to be applied to

• ADI
• AML
• AutoID
• CAS
• CNC
• CommercialKitchenEquipment
• CSPPlusForMachine
• DEXPI
• DI
• FDI
• FDT
• GDS
• I4AAS
• IA
• IEC61850
• IJT
• IOLink
• ISA-95
• ISA95-JOBCONTROL
• Machinery
• MachineTool
• MachineVision
• MDIS
• MTConnect
• OpenSCS
• PackML
• PADIM
  • IRDI
  • PADIM
• PlasticsRubber
• PLCopen
• PNEM
• POWERLINK
• PROFINET
• Pumps
• Robotics
• Safety
• Scales
• Sercos
• TMC
• Weihenstephan

Synchronized with the origin

Occasionally PR all modifications in the origin repository

Describe problem

The file contains mainly the text from the origin.

Describe the solution you'd like

It must be rewritten to containing the content description and main goals of this repository.

List of tasks to be accomplished

• Content
• Models recovery procedure and tools
• References to the ebook about the Information Model design and deployment
• Synchronization with the origin procedure

It contributes to mertyusaatag#4

• change the name of the UITests.md to Apply2AllModels.md
• add issue header
• pr to mertyusaatag

The following warning must be investigated in more details:

• Models element cannot be null or empty Added default model http://opcfoundation.org/UA/schemas/FDT/1.0/

Check if it is required.

Contributes to #8

• unlock issues button
• add issue templates

Blocker for the mpostol/OPC-UA-OOI#574

Describe the bug

Partially it contributes to mertyusaatag#14
Partially it contributes to mpostol/OPC-UA-OOI#653.

Describe problem

Check if we need ModelDesign for this folder. There are many subfolders so there is a concern about how many models are required.

After checking forward the result to @mertyusaatag for further development.

Release planned 2.1.0-Bravo

Information Model Validation

In this release, we have tested

• UA-ModelCompiler 3.0.0-Delta
• asp 6.5.0-Kilo
• ASMD 4.5.3--Echo

Scope

• Create the release draft
• Create and update VersionHistory.md (is to be prepared base on the external work)
• Create release front page using VersionHistory file
• Publish release
• Update the repository front page
• Update the GitHub pages documentation
• Close this issue and the parent milestone

All related work to prepare the repository for further development.

Follow community recommended standards

Scope:

• .gitignore
• Repository description
• social preview
  community-health-file)
• sponsor button
• Make release
• Add license file
• Code of conduct
• Contributing or use [default one](https://help.github.com/en/github/building-a-strong-community/creating-a-default
• README.md
• Wiki or GitHub pages
• Info in the master project if applicable

Blocker for the mpostol/OPC-UA-OOI#574

Hi @mpostol

When i generate the ModelDesign format for Machine Vision specification i notice that many namespaces are created in the model design specification. The output file contains up to 180 namespaces such as at the end of the file

<ObjectType xmlns:q180="http://opcfoundation.org/UA/MachineVision" SymbolicName="q180:VisionSystemType">

Not sure this behavior is expected? Is there any reason to do that?
Opc.Ua.MachineVision.ModelDesign.xml.zip

Describe the bug

asp shall generate the outcome in separate folders for all models.

To do

• modify the script
• generate the models (test the script)
• pr the result to @mertyusaatag

It contributes to mpostol/OPC-UA-OOI#653.

Describe the bug

Tried with the DI model to generate modelDesign with asp. It appears that publication dates do not have a correct encoding; As a result of that the ModelCompiler stops with an exception.

To Reproduce

Steps to reproduce the behavior:

%ASPDIR%\asp "..\Opc.Ua.Di.NodeSet2.xml" -e "publish\Opc.Ua.Di.Model.xml" -s XMLstylesheet -n "http://opcfoundation.org/UA/DI/" %MODELCOMPILER% -d2 "publish\Opc.Ua.Di.Model.xml" -cg "publish\Opc.Ua.Di.Model.csv" -o2 "publish"

The ModelDesign file contains

 <Namespaces>
    <Namespace Name="Name0" Prefix="Prefix0" InternalPrefix="http://opcfoundation.org/UA/" XmlNamespace="http://opcfoundation.org/UA/" XmlPrefix="Prefix1" FilePath="" Version="1.04.8" PublicationDate="20/11/2020">http://opcfoundation.org/UA/</Namespace>
    <Namespace Name="Name2" Prefix="Prefix2" InternalPrefix="http://opcfoundation.org/UA/DI/" XmlNamespace="http://opcfoundation.org/UA/DI/" XmlPrefix="Prefix3" FilePath="" Version="1.03.0" PublicationDate="09/03/2021">http://opcfoundation.org/UA/DI/</Namespace>
  </Namespaces>

Expected behavior

Obviously publication date should be something like PublicationDate="2021-03-09T00:00:00Z"

Screenshots

Additional context

Perhaps it is because my machine has a french Locale? It could be the difference with your machine. Anyway, the encoding of the XML file should be independant of the locale of the machine, right?

Best regards

The repository must have a license

For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.

Check out Licensing a repository to get details.

• Depends on OPCFoundation#79
• Blocker for the mpostol/OPC-UA-OOI#574

Describe the solution you'd like

• Review the result created by @mertyusaatag
• Create Tag.

List of models that the task is to be applied to

• ADI
• AML
• AnsiC
• AutoID
• CAS
• CNC
• CommercialKitchenEquipment
• CSPPlusForMachine
• DEXPI
• DI
• DotNet
• FDI
• FDT
• GDS
• I4AAS
• IA
• IEC61850
• IJT
• IOLink
• ISA-95
• ISA95-JOBCONTROL
• Machinery
• MachineTool
• MachineVision
• MDIS
• MTConnect
• OpenSCS
• PackML
• PADIM
• PlasticsRubber
• PLCopen
• PNEM
• POWERLINK
• PROFINET
• Pumps
• Robotics
• Safety
• Scales
• Sercos
• TMC
• Weihenstephan

Scope

• possibility to import NodeSet file
• possibility to convert NodeSet to ModelDesign
• validation against the schema and compliance with the specification (Part 3 and Part 5) of the NodeSet file

Contributes to #8

Describe problem

Prepare working space and recover the model from existing UANodeSet

List of tasks to be accomplished

• Create cmd file
• Generate ModelDesign using the newest available asp.exe
• Add htm documentation to the existing one
• Generate Word documentation

Notes

This model is required by the document PACKML UNIT/MACHINE IMPLEMENTATION GUIDE

• possibility to import NodeSet file
• possibility to convert NodeSet to ModelDesign
• validation against the schema and compliance with the specification (Part 3 and Part 5) of the NodeSet file

Contributes to #8