1) Use Case reminder
2) Where we are on our road map.
3) Open Action Items
4) JIRA Issues Review - https://jira.edmcouncil.org/projects/IND/issues/IND-17?filter=allopenissues
5) Todays content discussion.
6) For next week.
Discussed the definition of program as a 'coordinated set of activities designed to achieve some objective'. It doesn't have to be associated with a business, but needs to have an objective. Then StatisticalProgram should be a subclass of program. It should be linked to objective, design, and process/activities (occurrences in FIBO), and the design is the selection of the activities. Possibly use min 0 restrictions rather than requiring them.
From Oct. 23: One way of thinking about a program is that it involves some set of activities, and some group of processes are developed to carry out those activities. So a program would be a coordinated set of activities. Then you can tie that back to some set of constraints on the activities and/or requirements.
Then we continued discussing the relationship of some set of laws and/or regulations (requirements) to a program, for example for a compliance program. Dan thinks that a law/regulation is something like a specification with a set of compliance points - how do you account for a law or standard and some set of constraints to relate them to a set of variables in a data set. What is it that says 'this variable' allows you to determine compliance with that law'?
For many laws, the ultimate goal is compliance, not enforcement, so how do you connect these things at a high level? In practice, many agencies uncover violations, but in theory they really want to compel compliance. Yet, the definitions are not clear with respect to how you define the population of individuals or organizations to which a law or regulation applies, how do you design the regulations that implement the law (that have enforcement capability) to connect to the population "from the top down", and then meaningfully link the laws to the data? How do you design the regulations to make designing the related data collection program feasible and meaningful. How can we design data collection to understand what a violation is? And of course, violations change over time because regulations change over time... and how does this impact the data?