Skip to content

Latest commit

 

History

History
54 lines (45 loc) · 4.2 KB

2017-12-21WorkgroupCall.md

File metadata and controls

54 lines (45 loc) · 4.2 KB

Protocol

Attendees: Lutz, Hansjörg, Josef, Raphael Guests: Frank, Philipp (minute taker) Absent: Andreas G.

Workshop Protocol (from 19.12.2017)

  • Agreed on protocol. Will be merged into master.

Walkthrough results on GitHub

  • JSON schema addresses - organization by Hansjörg
    • This schema decribes the object organization
    • Arrays of objects to represent the multiplicities e.g. an organization can have varying numbers of addresses
  • JSON schema addresses - person by Hansjörg
    • This schema decribes the object person
  • JSON schema addresses - relation by Hansjörg
    • This schema decribes the object relation
    • Used to describe the different relation types e.g. organization to organization
  • JSON schema addresses - sharedDefinitions by Hansjörg
    • The schema includes definitions which are used in the three other JSON schemas, e.g. category
  • JSON schema products by Josef
    • Create consistent wording between UML and JSON
  • Regulations by Lutz
    • Suggestion by Lutz: Always describe the first letter of a class in uppercase
    • Regulations which need to be fulfilled in order to create a new master data model that is contributed to the open integration hub
    • DataModels.md has been expanded and includes rules and regulations (some of them are derived from Hansjörgs RulesandRegulations.md
    • Mandatory if a dataset is pushed into the open integration hub: ApplicationDataRecord
    • Snippets are used to explain and illustrate certain statements

Provision results of our 1st milestone

  • Provision an entry page to our MS1 results, for our repo - use permanent links.

Align the files and folders naming syntax

  • Source Code (currently json schemas) is located within a src folder in the root
  • All files (excluding source code files) will be named in Camel Case format

1st Workshop in 2018

  • We stick with the 17th Jan. '18 - Hafenamt

Contribute to the next milestone

  • Expanding the prototype by including a smart data framework (datahub) component on the elastic.io platform
  • Test models with real data and adjust the model
  • Feedback by the architects & developers for further discussions
    • Adjust the existing results to the feedback

Next Steps

  • Create consistent wording between UML and JSON Josef till late 21.12.2017
  • Create consistent wording across all master data model files Hansjörg, Lutz, Josef till 21.12.2017
  • Find a date for regular status calls - postponed till Andreas G. is back from vacation
  • Exporting the final results for milestone 1 into the needed format latest 03.01.2018
  • Next appointment on 02.01.2018 at 14:00 am
  • Next workshop takes place on the 17th of January 2018 at Altes Hafenamt - Cloud Ecosystem