Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Excessive verbosity in Vorto tutorial #2028

Closed
andrew-from-pretoria opened this issue Oct 16, 2019 · 7 comments
Closed

Excessive verbosity in Vorto tutorial #2028

andrew-from-pretoria opened this issue Oct 16, 2019 · 7 comments
Milestone

Comments

@andrew-from-pretoria
Copy link

In the tutorial at https://github.com/eclipse/vorto/blob/development/docs/tutorials/create_mapping_pipeline.md , this sentence can be improved:

"As mentioned earlier, we are going to design an architecture, that makes our application being able to consume data from any geolocation sensor vendor, with the help of Vorto Mapping Specifications."

Suggested version:

"As mentioned earlier, we are going to use the Vorto Mapping Specifications to design an architecture that allows our application to consume data from any geolocation sensor vendor."

@somesh-kumar
Copy link
Contributor

somesh-kumar commented Oct 17, 2019

@andrew-from-pretoria , thinking of changing the sentence to "Let's design an architecture, that makes our application being able to consume data from any geolocation sensor vendor, with the help of Vorto Mapping Specifications."

The How? in my opinion is quite important, which in this case is the mapping engine. What do you feel?

@andrew-from-pretoria
Copy link
Author

@somesh-kumar How about: "One of the challenges faced in IoT is that vendors use their own payload representations. JSON and CSV are two examples of payload representations. Vorto Mapping Specifications together with Normalisation Middleware is a mechanism we will use to normalise the various payload representations. Once this has been done, our application will be able to consume data originating from any geolocation sensor vendor. To achieve this, a Vorto Mapping specification must first be written for each expected payload representation."

@aedelmann
Copy link
Contributor

aedelmann commented Oct 17, 2019

Replace representation with format and it’s good to go :)
This will fit together with the image update u provided.

@andrew-from-pretoria
Copy link
Author

Adding aedelmann's suggestion: "One of the challenges faced in IoT is that vendors use their own payload formats. JSON and CSV are two examples of payload formats. Vorto Mapping Specifications together with Normalisation Middleware is a mechanism we will use to normalise the various payload formats. Once this has been done, our application will be able to consume data originating from any geolocation sensor vendor. To achieve this, a Vorto Mapping specification must first be written for each expected payload format."

@andrew-from-pretoria
Copy link
Author

@somesh-kumar I do not rights to make the changes. Will you upload the changes?

@aedelmann
Copy link
Contributor

You can fork the project, make the changes and make the Pull Request.

@ghost
Copy link

ghost commented Jan 17, 2020

@kolotu, I will take

@kolotu kolotu assigned ghost Jan 17, 2020
ghost pushed a commit to bosch-io/vorto that referenced this issue Jan 23, 2020
Change is make
@kolotu kolotu added this to the 0.13 milestone Jan 24, 2020
@kolotu kolotu closed this as completed Jan 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants