Ed, As Adam suggested, Arches v4 will allow users to use the CRM ontology or opt not to use a formal ontology at all. In practice, what this means is that Arches v4 provides tools to ensure that graphs conform to the classes and properties of the CRM. Users are free to use other ontologies such as LIDO (or no ontology) with Arches, but they'll need to ensure their graphs are internally consistent with the ontology. Arches v4 is designed so that it should be straightforward for a developer to add support for additional ontologies.
Hope this helps. Cheers, Dennis On Friday, September 30, 2016 at 8:43:37 AM UTC-7, Edmund Lee wrote: > > Thanks Adam, > > I am, I'll admit, out of my comfort zone here, but is there any mileage in > considering the existing mappings to the CIDOC CRM ontology available at > http://www.cidoc-crm.org/crm_mappings.html ? Does Arches (or could > someone with some Arches development expertise) set things up so that an > Arches database could provide data in another standardised format, if there > is an existing mapping to the CRM to assist them? > > All the best > Ed > > On Thursday, September 29, 2016 at 5:28:26 PM UTC+1, Adam Cox wrote: > >> Hi George and Ed, >> >> The short answer is that I don't believe there are currently any plans to >> support these ontologies; by default Arches uses the CIDOC-CRM. >> >> To be more specific, this depends on the version of Arches. In version >> 3, enforcing any ontology is completely up to the user, so you could create >> graphs that are based on LIDO just as easily as if you are making them for >> the CIDOC CRM. >> >> In version 4, CIDOC-CRM will come loaded in the database, and users will >> be able to choose whether to enforce that ontology when making new resource >> graphs or not (if you choose the latter, you will have no restrictions on >> how you construct the graphs. >> >> There is no UI in v4 for editing or creating new ontologies (LIDO, for >> example) but with a bit of behind the scenes work you could load it into >> your database. Then you would have the option of creating a resource graph >> that conforms to CIDOC-CRM, or LIDO, or non at all. >> >> Hope that makes sense! What's nice is that if one organization endeavors >> to load a brand new ontology into version 4, they should be able to easily >> translate their work into something that anyone can replicate. >> >> Adam >> >> >> >> On Thu, Sep 29, 2016 at 5:29 AM, Edmund Lee < >> [email protected]> wrote: >> >>> Hello George, >>> >>> Thanks for the post. I am sure there are others here better placed to >>> answer this from a technical standpoint, but to help get this question >>> answered, could you say a bit more about what support for these standards >>> would allow you and other potential Arches users to do? >>> >>> All good wishes >>> >>> Ed >>> >>> >>> On Wednesday, September 28, 2016 at 3:21:17 AM UTC+1, George Simeonov >>> wrote: >>> >>>> Greetings to all! >>>> >>>> Please tell me, >>>> Do you know if there are any plans in near future to have support in >>>> Arches for the following specifications? >>>> >>>> * LIDO - Lightweight Information Describing Objects - ATHENA >>>> <http://www.athenaeurope.org/getFile.php?id=535> >>>> * OAI-PMH Protocol >>>> >>> -- >>> -- To post, send email to [email protected]. To unsubscribe, >>> send email to [email protected]. For more information, >>> visit https://groups.google.com/d/forum/archesproject?hl=en >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Arches Project" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
