-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rework Crunchbase example to latest revisions of FIBO #2008
Comments
hi @ElisaKendall, I would be very glad to do it! I think the most efficient way is if you submit a PR against https://github.com/VladimirAlexiev/crunchbase-fibo: files Or do you prefer to do it in some other way? PS: I'd appreciate a suggestion for a journal where it could be published. Thanks! |
@VladimirAlexiev I'll think about the journal, but will work on this in your crunchbase git repo. I'll likely need your assistance to test it though. I will send email once I've made some progress so that you can take a look :). On places to publish, I'll also think about that. Possibly an EU conference since you are there. Thanks! |
@VladimirAlexiev I think I've made a first pass for you, but you need to give me permission to write to a separate branch in your crunchbase-fibo repo in order to push the changes out :) |
@ElisaKendall can you fork my repo to |
@VladimirAlexiev hmmm - I cloned it and created a branch. I was attempting to push my branch to the remote repo, not push anything into the main branch, but I don't have permission to do that. Would it be ok to simply push the branch or do I really need to fork it? |
@ElisaKendall |
@VladimirAlexiev Ok - done. We use branches for our FIBO work, but only because there are a small number of contributors that work with a larger SME community. Let me know if this was enough for you to be able to address any other discrepancies you've found. I recommend updating this and other demos with the Q1 2024 FIBO release to catch things up with where we are, if possible. |
I am loosely following this thread without really understanding the purpose or details, but I am curious why a fork is needed in order to support whatever additional definitions or specifications may be needed to satisfy the business requirements of Crunchbase (which is not a database technology but more a business content repository).
( Forks do create specifications and code bases that are separate and will ultimately diverge )
Just curious — I don’t really have a dog in this hunt :)
…-Jeff
On Apr 13, 2024, at 11:24 PM, Elisa Kendall ***@***.***> wrote:
@VladimirAlexiev <https://github.com/VladimirAlexiev> Ok - done. We use branches for our FIBO work, but only because there are a small number of contributors that work with a larger SME community.
—
Reply to this email directly, view it on GitHub <#2008 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB72TFWGQKST6QQAOCJIOV3Y5IOJNAVCNFSM6AAAAABGCKAOS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJTHEZDQOJQGU>.
You are receiving this because you are subscribed to this thread.
|
Thanks @ElisaKendall ! Normally you'd make a branch for each task/feature. But since here is only one task (to update), it's ok that you did it in your Master.
|
|
This is a really great example. Any chance we can update it to use the latest revisions to FIBO, including migration of some ontologies to the OMG's Commons Ontology Library 1.1 standard? I would be happy to walk through that with you :).
Originally posted by @ElisaKendall in #1816 (comment)
The text was updated successfully, but these errors were encountered: