...
Given our dependency on those things, do we run the risk of the AB saying that our submission is dependent on another spec that has not yet been through the process? Elisa asked them this at the time, and they said they would help us to avoid that pitfall. The main risk is capacity to get this done. But, not a procedural roadblock. We will be unhappy if these TC37 related specs do not work their way through the process in good time. The language representation ontology and the country (codes) representation ontology that Elisa has developed, is proposed to move to the other AB driven spec. These classes did already exist in legacy FIBO. The proposed new ontologies will not use the abstractions that are provided in FIBO e.g. as kinds of code, kinds of scheme and so on, as Information Constructs. From Elisa's perspective, the ability to disambiguate between concepts e.g. information constructs, is superfluous. Foundations will continue to look after the higher level disambiguation between otherwise similar looking concepts, outside of what FBC needs to develop in the current iteration.
Action items
- July 27th is preliminary draft spec to OMG
Jira Legacy showSummary false server jira.edmcouncil.org JIRA serverId 6465cde0-d6c9-34a0-a506-4d4ac3461fe5 key FBC-4 - MB to revisit his recommendations and suggest a better parent by default this would be moved to Legal document, which sounds fine.
Jira Legacy showSummary false server jira.edmcouncil.org JIRA serverId 6465cde0-d6c9-34a0-a506-4d4ac3461fe5 key FBC-10 - Need a list of definitive, high level services we can use to differentiate these kinds of entities and who regulates them. So e.g. if someone is regulated by a given regulation, then it means they are a bank holding company.
Jira Legacy showSummary false server jira.edmcouncil.org JIRA serverId 6465cde0-d6c9-34a0-a506-4d4ac3461fe5 key FBC-9