search

edmcouncil / fibo

The Financial Industry Business Ontology (FIBO) defines the sets of things that are of interest in financial business applications and the ways that those things can relate to one another. In this way, FIBO can give meaning to any data (e.g., spreadsheets, relational databases, XML documents) that describe the business of finance.
https://spec.edmcouncil.org/fibo/
MIT License
330 stars 68 forks source link

Initialize your use of GitHub by adding all materials ASAP if not sooner. #12

Closed DennisWisnosky closed 6 years ago

DennisWisnosky commented 10 years ago

@ElisaKendall @MikeHypercube @ajvizedom @dsnewman @rivettp @lonniev @DennisWisnosky

Each Core Team member must -- open an issue for the task of getting all the materials you are holding that belong in the repository in there. The description of the issue should include mention of which materials you are going to be putting in. -- assign it to yourself. -- Start working on it by uploading your materials.

unixmonkeys commented 10 years ago

@DennisWisnosky I think I was added to this in error.

ajvizedom commented 10 years ago

@dfnewman -- thanks for letting us know. Correcting it now.

ajvizedom commented 10 years ago

@DennisWisnosky @dsnewman @ElisaKendall @lonniev @MikeHypercube @rivettp Just a couple of comments for all: -- Once you've created your own issue/task, in order to work on it you' ll have to go through the initial steps (creating your own fork, making a local clone on your own machine) that we walked through on Monday. It can be confusing the first time. I can help if you get stuck or confused (so can Lonnie, obviously, but he may be less available right now). -- If you encounter non-mechanical issues that would benefit from team discussion (such as folder organization choices, figuring out who has what or what format to store as the one everyone works of off, or whether something should be in the repository or not, for example), you can always open an issue for those things (mention (using the '@' prefix) each person you want to see and/or weigh in on the issue). -Amanda

rivettp commented 10 years ago

Not quite sure of the complete scope of what materials you're looking for. I see that the submission files I worked on: the ODM XMI and UML XMI are already in GitHub. Anything else you're looking for? Once I get the EA model from @MikeHypercube I can generate the OWL for that - I assume that should that be uploaded - where should I put that?

ajvizedom commented 10 years ago

@rivettp @MikeHypercube @DennisWisnosky

My two cents: I would say: what should be in there is anything anyone else on the project might need, ever! Plus anything needed to trace or reconstruct provenance. :-)

I don't have any useful opinion about where the OWL-from-EA artifacts should go. Very possibly somewhere that doesn't have an intuitive top-level folder right now. I'm sure I covered best the artifact types I already understand (plus the releases since they need to be archived and available as a whole, and since I've just had the pleasure of the consumer-side experience of trying get all the materials in one and view it and understand what's there). Maybe this is some of what @lonniev intended with top-level folder "Source Models?"

MikeHypercube commented 10 years ago

I’ll figure out where I think these should go, and the structure will be reviewed before this is merged into the Master stream.

Mike

Mike Bennett Head of Semantics and Standards EDM Council Tel: +44 20 7917 9522 Cell: +44 7721 420 730 www.edmcouncil.orghttp://www.edmcouncil.org Semantics Repository: www.hypercube.co.uk/edmcouncilhttp://www.hypercube.co.uk/edmcouncil

From: ajvizedom [mailto:notifications@github.com] Sent: Wednesday, February 12, 2014 1:31 PM To: EnterpriseDataManagementCouncil/FIBO Cc: Mike Bennett Subject: Re: [FIBO] Initialize your use of GitHub by adding all materials ASAP if not sooner. (#12)

@rivettphttps://github.com/rivettp @MikeHypercubehttps://github.com/MikeHypercube @DennisWisnoskyhttps://github.com/DennisWisnosky

My two cents: I would say: what should be in there is anything anyone else on the project might need, ever! Plus anything needed to trace or reconstruct provenance. :-)

I don't have any useful opinion about where the OWL-from-EA artifacts should go. Very possibly somewhere that doesn't have an intuitive top-level folder right now. I'm sure I covered best the artifact types I already understand (plus the releases since they need to be archived and available as a whole, and since I've just had the pleasure of the consumer-side experience of trying get all the materials in one and view it and understand what's there). Maybe this is some of what @lonnievhttps://github.com/lonniev intended with top-level folder "Source Models?"

— Reply to this email directly or view it on GitHubhttps://github.com/EnterpriseDataManagementCouncil/FIBO/issues/12#issuecomment-34899588.