Date
Attendees
Agenda
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.
SMIF OWL-UML
SKOS
RDF/S
6) For next week.
Proceedings:
Discussed the new hasCoverageArea property. A statistical program also has a coverage area, or possibly more than one, which we are missing in the ontology. What we don't have is a link from the program to one or more coverage areas, some of which may be subsets of the overall coverage area. We might need subproperties of hasCoverageArea for (1) the top level or broadest coverage area possible for the program, and (2) smaller ones that don't all nest but that roll up to the broader one. For example, CPI overall reflects the total US but there are subordinate or more finely grained CPI measures for MSAs or for products, and so we need to be able to nest these and relate them back to the overall coverage for the program. Same is true for employment, which is more complicated, which includes breakdowns by demographics for the US unemployment rate, and then there are local area unemployment statistics for states and counties, and for some cities (MSAs).
We need to amend the definition of StatisticalProgram to include coverage area, and change the property on an economic indicator from applies to to has coverage area. We should also consider how to structure subproperties of hasCoverageArea as needed. A statistical program has an output which is a report on the statistical measure - also missing.