You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently looked (briefly!) at FaBiO to try and determine its suitability for creating simple bibliography descriptions in a linked data project. The impression I had, based on what I found (and which may well be incorrect), was that FaBiO uses a layered structure that is more complex that we wanted to create. In the end, we are currenty looking at a small subset of BIBO. Here is an example of something I've created:
Both of which seemed to me to be somewhat more complex and harder to understand that the BIBO example above.
Maybe this is inherent in the intended use for FaBiO, but if I'm missing something here it would be good to have a discoverable example of something at a comparable level of complexity/comprehensibility.
(NOTE: in my experience, when building a linked data model for an application, one often has limited time to investigate the various possible ontologies to incorporate. It is probably the case that reading all the FaBiO documentation and internalizing the model structure details would tell me all I want to know. But... time! Just saying.)
The text was updated successfully, but these errors were encountered:
I recently looked (briefly!) at FaBiO to try and determine its suitability for creating simple bibliography descriptions in a linked data project. The impression I had, based on what I found (and which may well be incorrect), was that FaBiO uses a layered structure that is more complex that we wanted to create. In the end, we are currenty looking at a small subset of BIBO. Here is an example of something I've created:
The nearest equivalents for FaBiO that I found were:
http://www.sparontologies.net/examples#fabio_1
http://www.sparontologies.net/examples#frbr_1
Both of which seemed to me to be somewhat more complex and harder to understand that the BIBO example above.
Maybe this is inherent in the intended use for FaBiO, but if I'm missing something here it would be good to have a discoverable example of something at a comparable level of complexity/comprehensibility.
(NOTE: in my experience, when building a linked data model for an application, one often has limited time to investigate the various possible ontologies to incorporate. It is probably the case that reading all the FaBiO documentation and internalizing the model structure details would tell me all I want to know. But... time! Just saying.)
The text was updated successfully, but these errors were encountered: