mpostol on SemanticData-6.1.3
Import simple NodeSet2 file is … (compare)
mpostol on master
Enhance/Improve BrowseName pars… Merge pull request #544 from mp… (compare)
mpostol on master
Enhance/Improve BrowseName pars… Enhance/Improve BrowseName pars… Enhance/Improve BrowseName pars… and 2 more (compare)
EventSource- Report new issue related to
EventSourceand collect all your findings and proposals. It is good starting point for further investigation and decision making. Lets do nothing with your application for now. We can state that this feature is not available on mono and that's all. Let me know how it works for you. We should also check the feature against official .NET Standard compatibility table.
CommonServiceProviderif it is supported by the
Autofacyou should only make sure that you have registered all contract providers I need and it can be marked as fixed as far as I follow this issue.
@Drutol Let me return to portability issue in context of the
EventSource type, because it is important for this project.
EventSource is used in many assemblies and also external projects. It has been assumed that it is main tracing diagnostic data source. As I understand you have not composed it because of portability issue. There is official compatibility table:
How this table relates to your findings ? I will appreciate your comment. Main assumption for the project is that the library based on .NET Standard 2.0 is portable.
While https://raw.githubusercontent.com/dotnet/standard/master/docs/versions/netstandard2.0_ref.md does indeed mention the
EventSource as a part of .NetStandard2.0 it's worth checking the docs page https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.tracing.eventsource?view=netframework-4.7.2 where they state:
Provides the ability to create events for event tracing for Windows (ETW).
I was browsing the https://github.com/dotnet/corefx repository and I've found inconsistencies when it comes to this class, with some
I've also found this: https://github.com/dotnet/corefx/blob/c8c882c7366f2facfca4c8069de79da477dcf05b/src/System.Diagnostics.Tracing/ref/System.Diagnostics.Tracing.cs where implementation is just dummy one like in Mono. My guess is that runtime specific implementation comes in when on Windows and on other platforms it's just dummy class implemented only to be compliant with the specification.
Being only for Windows it's hardly portable as ETW is only Windows thing. I also personally consider them being very clunky to use, but that's just my opinion.
Provides the ability to create events for event tracing for Windows (ETW).
@Drutol I see, but in the ReferenceApplication I am not using ETW, even I am not aware about ETW. It seems that it is just typo copy/pasted from the very beginning. I am pretty sure it has nothing in common with Windows ETW. It seems we must treat the ETW shortcut as a general term. Let me summarize:
Starting with .NET Framework 4.6- it doesn't make any sense in context of this abstract definition. It seems it is copy/paste problem.
I will appreciate any information referring limitation of the mentioned implementations
Xamarin.Android 8.0 and
Mono 5.4 - empty implementation should be recognized as an error for sure.
Let me also note that ETW is a sink, but we are talking about the source and the source could be associated with many different sinks. I have implemented the sink as a file (no ETW at all it works on XP) and I know an implementation for Azure again nothing in common with ETW, but in any case
EventSource is used as the source.
@Drutol I have reported the problem:
Thank you for the feedback. Inform me in case you will find something more.
But wouldn't it be better to be even more abstract and go for a solution that supports
EventSource as well as myriad of other providers? Regardless of what we do
EventSource won't work on Mono while with abstract logging interface it would be left to end user's discretion.
EventSource is designed to interface with the underlying operating system's logging infrastructure, e.g. Event Tracing for Windows (ETW.aspx)) or LTTng on Linux.
EventSource is an implementation which is enforced upon end user and while it allows to attach some additional sinks it's still an implementation... OS dependent at that.
If you are sure it doesn't work on mono just report it will see the answer. Now we are talking about two things:
I am pretty sure that
EventSource is a generic solution and can be implemented on any platform somehow that make sense.
Anyway, thank you for feedback.
Export model. Scope: add UAModelDesingn generator implementing IModelFactory, Unit Tests, add command line application (tool).
SemanticDatabranch and merged to master after accomplishing this milestone. The release is planned.
asp.exe) allows export to ModelDesign XML format.
@joesan sorry for the delay, but I haven't got notification from this thread.
The answer is yes with the Ver 1.1. of the protocol.
The binaries are available here:
Networking -Internet of Things (IoT) Communication
There is a note:
This release contains modifications required to start interoperability testing against PubSub protocol version 1.10.
Standardization of the new version of the protocol is still in progress
AMENDMENT 6 - UADP Header Layouts (DOC/ZIP)
Now I am working on the protocol description using ABNF
available on the Network branch.
This update comprises the following changes:
Let me inform you that CAS OPC UA Address Space Model Designer has been just published on GitHub as the open-source:
For now, it is a stand-alone project, but any ideas related to harmonization with your needs are welcome. Further development and priorities will be derived from community feedback. The old installation package is still available on the commsvr.com web-page:
I am also in the process of moving the CommServer software family to open source. The master plan is available here:
Any questions, suggestions, and proposals are welcome.
I am excited to share that my article titled
Object-Oriented Internet Reactive Interoperability is to be published in Lecture Notes in Computer Science series, on behalf of Springer.
It is not about OPC UA but it refers to this standard pointing out further development directions. From these proposals, a question may be derived
Do we need the OPC UA Rel. 2.0?
Contact me by message to get a preprint version of the article. I am going to prepare an article to aggregate your comments and summarize what is missing.
Consider addressing this topic during
OPC Day 2020 - International - is coming soon.
I have released the new version 4.3 of the Address Space Model Designer. In this release, many bugfixes have been applied. Check it out and let me know how it works for you. This version is available here:
Now on my road map is version 5.0. The scope is defined by the milestone
I am proud to announce the public preview of our article titled: Object-Oriented Internet -Azure Interoperability. It is a preprint for early review. We will consider your contribution to be applied to the final version of the article. The proposals are backed by proof of concept reference implementations confirming the possibility to integrate selected cloud services with the cyber-physical system interconnected as one whole atop of the OPC UA PubSub.
Check out more details from Research Gate:
It is a preprint for early review. We will consider your contribution to be applied to the final version of the article.
Let me inform you that I have just released the new version
6.1.2 of the
Object-Oriented Internet library. This release comprises the following code and documentation changes:
In this release, many bugfixes have been applied and released as the NuGet packages.
The open-access Object-Oriented Internet (OOI) umbrella project targets multi-vendor plug-and-produce machines interoperability scenarios targeting all aspects of the machine-centric global village concept aimed at providing reusable deliverables, training, best practice rules, prototyping, compliance testing and dissemination of valuable results.
I am a researcher who is passionate about applying knowledge and experience in building a machine-centric global village. Let's build it with you and for you. To join our effort and create an organization context I have launched the Object-Oriented Internet Partnership Program.
To be involved you may
More detailed description is covered by the Object-Oriented Internet Makes OPC UA PubSub to Cloud Interoperability Possible
OPC UA - Cloud Metadata Export community feedback request to push appropriate responses to the community requests.
To encourage the OPC UA adaptation idea conducted as an open-access community-driven activity, I have just added a new project:
It has been just added to the road map as a feature request. I am looking for community feedback aimed at improving the scope and goals of the project.
The Cloud Metadata Export project is to be conducted as part of the open-source Object Oriented Internet initiatives. Let's work on it with you and for you. To join our effort and create an organizational context the Object-Oriented Internet Partnership Program has been launched.
Consider joining as a sponsor, contributor, or end-user. Details are covered by the section How to be involved. Your experience, knowledge, and direct participation is needed to make sure the work will continue as expected.
I am waiting for your advice. What do you think about it?
Thanks for your cooperation. Let's stay in touch.