AlpineBits
By Claudenir
Focus: create a standard for touristic events of the Alto Adige region.
The standard is based on formats such as XML/JSON
The standard is free and may be downloaded from the AlpineBits website.
It is not a service... it is a contract to use a particular format on data exchange.
Main motivation: to exchange knowledge in a common format,, so that all businesses and the government can consume this data. In the end, the businesses are competitors, but they collaborate on developing the standard, because it is advantageous for all of them.
------------------------------
Scope
Touristic events: events, event series, venues, organizers etc.
Touristic areas: lifts, trails,, slopes, mountain areas etc.
Additional information: agents, multimedia, metadata etc.
-------------------------------
Eventdata reference model
*He showed several models, some were class models, other instance models. This was very interesting to illustrate the usefulness of the approach.
The more complete model contains the following concepts: event, event series, venue, venue allocation, the roles of the people and organizations connected to the event, and target audience.
--------------------------------
They reuse as much as possible. For example, they use schema.org.
Reusing is important to guaranteeing acceptance by partners (people want to use popular solutions, which they are already familiar with).
However using the things they reuse alone is not enough, because this would keep the information too vague.
So their solution builds on top of the existing artefacts/tools
-------------------------------
They applied GitLab and created issues for everything they had to do for the project.
And they followed the good practice of having a structured development, using features path, development path and master path, leaving the master path as clean as possible.
The repository is public and thus available for the students to take a look
----------------------------------
One of the most important things in Claudenir's view is testing. You must have a way to guarantee the quality of the code, especially if you expect someone else to revise your code.
Here is the testing tools Alpine Bits make available.
--------------------------------------
Some requirements
minimize message size
one way to respresent information
(...)
-----------------------------------
Main use cases
By Claudenir
Focus: create a standard for touristic events of the Alto Adige region.
The standard is based on formats such as XML/JSON
The standard is free and may be downloaded from the AlpineBits website.
It is not a service... it is a contract to use a particular format on data exchange.
Main motivation: to exchange knowledge in a common format,, so that all businesses and the government can consume this data. In the end, the businesses are competitors, but they collaborate on developing the standard, because it is advantageous for all of them.
------------------------------
Scope
Touristic events: events, event series, venues, organizers etc.
Touristic areas: lifts, trails,, slopes, mountain areas etc.
Additional information: agents, multimedia, metadata etc.
-------------------------------
Eventdata reference model
*He showed several models, some were class models, other instance models. This was very interesting to illustrate the usefulness of the approach.
The more complete model contains the following concepts: event, event series, venue, venue allocation, the roles of the people and organizations connected to the event, and target audience.
--------------------------------
They reuse as much as possible. For example, they use schema.org.
Reusing is important to guaranteeing acceptance by partners (people want to use popular solutions, which they are already familiar with).
However using the things they reuse alone is not enough, because this would keep the information too vague.
So their solution builds on top of the existing artefacts/tools
-------------------------------
They applied GitLab and created issues for everything they had to do for the project.
And they followed the good practice of having a structured development, using features path, development path and master path, leaving the master path as clean as possible.
The repository is public and thus available for the students to take a look
----------------------------------
One of the most important things in Claudenir's view is testing. You must have a way to guarantee the quality of the code, especially if you expect someone else to revise your code.
Here is the testing tools Alpine Bits make available.
--------------------------------------
Some requirements
minimize message size
one way to respresent information
(...)
-----------------------------------
Main use cases
- Request-Response
- Publisher-Subscriber
- Batch exchanges
-----------------------------------
Interaction Types
- Request-Response
- Publisher-Subscriber
- Batch
- Streaming
------------------------------------
API Styles
- Tunnel Style - having one endpoint and everything else goes on the message
- URI Style (Partial REST)
- Hypermedia (Full REST)
- Query Style
- Event-driven Style
--------------------------------------
In general, the resources for AlpineBits developers are found here.
Nenhum comentário:
Postar um comentário