The ooi.gateway2azure.article from it-p-lodz-pl

Contributes to #60
----------- Overall evaluation -----------
SCORE: 1 (weak accept)
----------- Reviewer's confidence -----------
SCORE: 2 ((low))
----------- Relevance to ICCS -----------
SCORE: 4 (good)
----------- Quality of abstract -----------
SCORE: 2 (poor)
----------- Introduction and motivation -----------
SCORE: 4 (good)
----------- Literature review and related work -----------
SCORE: 2 (poor)
----------- Description & originality of the own contribution -----------
SCORE: 3 (fair)
----------- Results and presentation -----------
SCORE: 3 (fair)
----------- Conclusions and future work -----------
SCORE: 3 (fair)
----------- Readability, quality of the English -----------
SCORE: 5 (excellent)
----------- Quality of the figures -----------
SCORE: 3 (fair)
----------- Conformance to the LNCS template -----------
SCORE: 3 (fair)
----------- Candidate for best paper -----------
SCORE: 2 (No)
----------- Candidate for special issue of Journal of Computational Science -----------
SCORE: 3 (Don't Know)
----------- Comments for the authors ----------- The abstract is too detailed. It should be simplified to
describe the idea in a more general manner.
The proposed solutions comparison should be summarized in a more transparent manner like a table or
a chart.
The papier is missing the "related works" section.

Prepare AZURE.DeviceCapabilityModel.md

Description of the Device Capability Model (DCM)
Description of the Device Template (DT)
Documents syntax representing DCM
Documents syntax representing DT
Processing of the mentioned documents

ICCS21 - high-resolution graphics

Create graphics
Add graphics to the folder
Improve graphics

Final language corrections

mp review
ps review
prepare word document to get external language support
apply external feedback

Introduction - add information about OOI

It is in the title so it must be explained the relationship.

Review the sketch of the paper

This workout will be described in the article: OOI/Azure Interoperability.

md conversion to latex

Scope

cmd file
latex template
add reference to the bibtex - consolidate with #23

Work out Markdown\60.GatewayImplementation.md

Review ICCS 2021 notification for paper 136

REVIEW 1
REVIEW 2
REVIEW 3
Plan final work

Workout Markdown\10.DocumentHeader.md

Scope

clenup
abstract
harmonize with the Latex\Manuscript..tex

Conduct research on .Reserch\AZURE.Connectivity.md

create document Reserch\AZURE.Connectivity.md
work on the content using IoT Central documentation
work on the content using Device Provisioning Service (DPS) documentation
work on the content using IoT Hub documentation
select other services if helpful

Work out the integration domain model using UML class diagram

Remove CV from the authors list

CV is busy and cannot contribute. Details on Temas.

Research on publication journal

Consider publishing in:

Telemetry vs process data

Review the Azure documentation
Review the OOI documentation
Review the available definitions and descriptions provided by the Science Direct.
prepare description and comparison
Add suitable references

Create Repository Website

Use GitHub pages

Forked from #1

Work out the solution UML models

work out solution architecture diagram in the Enterprise Architect
work out the integration domain model in the Enterprise Architect
prepare description of the models (contributes to #14)
Finally, export diagram as a high-resolution graphics

Define OPC UA PubSub application role

The types of devices are defined in https://github.com/it-p-lodz-pl/OOI.Gateway2Azure.Article/blob/master/.Reserch/AZURE.Connectivity.md#get-connected-to-azure-iot-central

Standalone device
Gateway device
Edge device

The issue contributes to #8

Revert formatting to default

Because publication in JACS is still on the table, we need to remove reference to this journal from the preprint.
After making a decision final formatting must be applied.

PubSub architecture drawbacks

Describe the PubSub Architecture Part 1, 6.6 Synergy of models

The specification states "PubSub and Client-Server are both based on the OPC UA Information Model. " but in Figure 8 – Integrated Client-Server and PubSub models there is Address Space. From this statement, someone could derive that the AS and IM are the same terms (are synonyms), but parts 3 and 5 states something different.
Parts 3, 4, 5 of the OPC UA spec describes interoperability between OPC UA Client and OPC UA Server Address Space, and it makes sense because the client uses many services (including but not limiting to 7.11 Subscription Service Set against Address Space exposed by the server.
There are no similar services available for Subscribers, therefore the Publisher dependency on the Address Space doesn't make any sense - the specification doesn't describe interoperability between Subscriber and Address Space.
Additionally, the Publisher dependency on Address Space makes it impossible to support interoperability between the Cyber-Physical Network based on PubSub and cloud-based services. Instead, interoperability must be deployed based on a Server concept alone.
Subscriber and published should mirror the functionality. Why only the Publisher is an embedded module of the OPC UA server.
One box cannot represent OPC UA Server, OPC UA Application, and Publisher at the same time - the fig is inconsistent.

Work out Markdown\30.AzureTechnologyFeatures.md

Create repo TODO list

Preface

All related work to prepare the repository for further development.
Follow community recommended standards

Scope:

IEEE Transactions on Software Engineering

Consider publishing an extended version

Work out Markdown\70.Conclusion.md

Scope

Middleware definition and ref

review the Google
review Microsoft Azure definition
TODO

Blocker for #37

Work out Markdown\20.Introduction.md

Work out Markdown\40.OOITechnologyFeatures.md

Prepare Abstract

Scope

Refine Markdown\10.DocumentHeader.md
Review
Copy to Latex\Manuscript..tex
Final review

Forked from #25

Prepare md files against the article structure.

Prepare zip package and submit

prepare .zip package
submit
close this milestone
close project

Set up folders structure

Primery format is Latex.
Research and proprietary material is worked out in markdown

Final review of the latex text

Find reference for real-time systems

Needs to find proper reference defining the real-time systems.

IEEE Transactions on Industrial Informatics - consider publication of an extended version

IEEE Transactions on Industrial Informatics

Work out the section Azure to Sensors Connectivity Deployment

Scope

workout a description of the SolutionArchitecture.png
workout a description of the IntegrationScenario.png
describe main design decisions
consider the PS notes as follows

PS notes

Deployment phases:

Device/Service association
Device/Application association
Establishing session

Honestly, I'm getting the impression that it's a bit like the discussed network protocol analysis. It's being done behind the scenes by the Azure's black box. All we have is SDK which handles establishing the secure communication channel and then with the other thing we have which is either SAS/X.509 which provides:

Identity of the device
Authorization for specified resources

So unless there's a greater scheme behind these I missed it'd all be just "Establishing connection context". Unless you mean mixed flow of Azure configuration interweaved with actual device in runtime?

Establishing a semantic-context

We are not directly establishing semantic context, the message properties are mapped after they surface from IoT Hub to IoT Central (if such template is assigned) somewhere in the cloud. From the device perspective, its identity is the context. Also, it is under the "Establishing session" part but semantic context is defined before the session starts being established... assuming session means active connection here.

Security management - establishing security-context
Authentication

Aren't these the same thing in this IoT Hub's context?

Originally posted by @Drutol in #7 (comment)

Work out Markdown\50.Sensors2AzureConnectivityDeployment.md

Architecture - Domain model presenting the relationship between the: Azure, PubSub Gateway, Device, Design, and development tools
Connectivity - Describe the reactive nature of the Azure monitoring process data (telemetry) services.
Deployment phases
PS Review
convert to latex
add bibligraphy
integrate with other sections.
final latex text formating
fnal review

Prepare the article scope and template

update the Readme.md
create master document containing all relevant sections in markdown

References

List of available resources related to the topic in concern as a bibtex file.

Research on Azure.Security

Collect all valuable information related to gateway security.

Review the documentation:

Service Bus
IoT Hub
Device Provisioning Services
IoT Central

it-p-lodz-pl / ooi.gateway2azure.article Goto Github PK

ooi.gateway2azure.article's People

Contributors

Watchers

ooi.gateway2azure.article's Issues

Functionality

Relationship

Decision

Scope

Scope

Scope

Preface

Scope:

Scope

Scope

Scope

PS notes

Recommend Projects

Recommend Topics

Recommend Org