Attendees: Andreas G., Lutz, Hansjörg, Josef, Raphael, Philipp (minute taker)
Absent: Josef
2017-12-11Telko.md - accidentally merged already due to DecisionsMade.md
- ...
Provide deliverables on basis of Lutz' suggestions (Tool + Schema)
- Wasn't able to provide a json schema until now because of illness
- JSON Schema has priority no.1 from now on
- Provided a Data Model which includes the description of the OIH datasets.
- Provided a UML diagram on basis of the previous elaborations and the provided by Lutz.
- Lutz: Field (String, enumartion etc.) so specify the sort of the address.
- Lutz: The Fields like street, streetNumber, unit, etc. can be modeled as attributes within the addresses
- The idea behind the object
relationsshall be generic
TBD Provide the regulations on how to design a generic domain model
- What is the purpose of the
regulations? What exactly is meant byregulations? - Define regulations per domain and/or define them for all models (such as UML, JSON etc.)
- Regulations for the different domains have to be written down
- Overarching regulation:
Header (OIH Dataset)is set for all domains
Fixed GoToMeeting every two weeks - when?
- To be determined
Alternative date at the 3rd KW'18 - possible?
- To be determined
- Provide a JSON Schema Lutz till early 19.12.2017
- Reconcilation of Hansjörg's results and afterwards provide the results on GitHub Lutz, Hansjörg, Josef (Suggested) till 15.12.2017
- Provide the regulations on how to design a generic domain model by @lashauer @hschmidthh @JosefBraeuer till 15.12.2017
- Write down concrete attributes and update UML diagram Hansjörg till 15.12.2017
- Supplement from a subsequent converstion: the UML diagrams for addresses and products will be converted into the provisioned JSON 'tree structure' Hansjörg, Josef till late 19.12.2017
- Remove ZenHub broadcast functionality about its Board activities - for Slack Raphael till 15.12.2017
- Next appointment 19.12.2017 at 10:00 am