RiC-CM 1.0 and RiC FAD translation ito Italian
Pierluigi Feliciati
<Questo documento è digitale e vorrei che (digi) tale restasse. 1 sheet of paper A4 = 7,5g of CO2 and 10 L of water!! >
Hope, Aaron (MPBSDP)
Thanks for your message Pierluigi – I look forward to reading your introduction and the annex on LOD and AI.
Cheers,
Aaron
Aaron Hope, PhD | Senior Archivist | Archives of Ontario
134 Ian Macdonald Blvd. | Toronto ON M7A 2C5
From: records_in_c...@googlegroups.com <records_in_c...@googlegroups.com>
On Behalf Of Pierluigi Feliciati
Sent: Thursday, November 28, 2024 5:05 AM
To: Records_in_C...@googlegroups.com
Subject: [Records in Contexts users] RiC-CM 1.0 and RiC FAD translation ito Italian
CAUTION -- EXTERNAL E-MAIL - Do not click links or open attachments unless you recognize the sender.
--
You received this message because you are subscribed to the Google Groups "Records_in_Contexts_users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Records_in_Context...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/Records_in_Contexts_users/CAOZaAH3LD3XHzPVYrmTac8vA2ZorkwHvZz5itnoQjkzkV296tw%40mail.gmail.com.
Hope, Aaron (MPBSDP)
Hello RiC user group,
Apologies for the late notice, but I wanted to share the call for papers below, which pertains to the Association of Canadian Archivists conference next June. I mention it because one of the suggested topics is “How have archives adopted linked data and Records-in-Context?” (see the fourth bullet point under PROCESSES: Technologies and Techniques).
I am not involved in the organization of this conference, though I am preparing a proposal for submission based on the Archives of Ontario’s experiences with RiC so far. I thought perhaps a panel discussion might be possible if more participants are involved. Note, however, that the deadline for submission is 11 December.
Cheers,
Aaron Hope
As we approach our 50th anniversary, we want to take the opportunity to celebrate what ACA has accomplished, how the profession has changed over time, and how the concepts of archives and records have shifted and evolved. This anniversary is also an opportunity to critically look at the current state of archival work. Where do we go from here? How has ACA impacted communities, other disciplines, and generations both within and adjacent to archives? Let's imagine what our profession will look like for ACA at 100. Let this conference be a gathering place for new generations of archivists, established professionals, stakeholders, and community members. We encourage collaborative proposals that include these various perspectives.
9-12 June 2025
Richcraft Hall, Carleton University, Ottawa, ON
Proposals Deadline:
December 11, 2024, 11:59 pm PT
The 2025 ACA Program Team invites proposals that reflect on the theme of ACA at 50: Critical Reflections, Envisioning the Future.
- Types of Proposals:
Traditional Session: Presentation of research papers, case studies, and thought pieces. Usually 20 minutes per speaker followed by a question period. - Panel Discussion: Presentation of research papers, case studies, and programs or projects, followed by a discussion period.
- Roundtable: Presentations of programs, projects, and tools, with open discussion.
- Focused Debate on Specific Topic: Brief presentations with debate to follow.
- Sprint Session on Specific Challenge: Presentation of a challenge to registered group of participants. Timed exercise to brainstorm a solution to a problem.
- Performance: Presentation of a short film, video, dance, song, or performance with a discussion period.
- Storytelling session
Workshops: In-person interactive workshops, 1.5 – 3 hrs in length. Participation can be limited to a specific number if necessary. All workshops will be given on the first day of the conference, June 9th. - Other format: Please share your ideas! (e.g. fishbowl).
Suggested Conference Topic Areas:
PEOPLE: Personal and Professional Identities
- How have the concepts of archives and archivists evolved since ACA's Inception?
- What specific role do archivists have in stewarding cultural memory?
- In what ways have excluded and underrepresented communities been welcomed into the field, and how might we work toward even greater inclusion?
- What do we envision our role to be in another 50 years?
- Additional keywords: community archives; knowledge; identity; dreams/envisioning; records and recordkeeping.
PROCESSES: Technologies and Techniques
- How have new technologies and workflows facilitated efficiency in archival practice?
- What are the opportunities and concerns central to artificial intelligence?
- How are collecting institutions navigating the exponential growth of born-digital fonds?
- How have archives adopted linked data and Records-in-Context?
- How do we contend with expanding ideas of the 'record' in a digital age - e.g. social media - and how are institutions taking it upon themselves to keep these records?
- What technologies/techniques might we imagine into the future of archival work?
- Additional keywords: technologies; media; ethics and legalities; processes and procedures; records and recordkeeping.
POWER: Turning Disconnection into Collaboration
- How are Indigenous Archives making their holdings accessible to their communities?
- What explicit and implicit barriers prevent access to Indigenous documentary heritage in non-Indigenous Archives and Indigenous Archives?
- How do Canada's and the World's archives work together?
- Is the vision of the 'Total Archives' still realistic?
- Why do certain communities reject acquisitions by traditional archival institutions, and what might we learn from these resistances?
- What role do power and privilege play in determining which records and stories are deemed archival and worthy of preservation?
- Additional keywords: reconciliation; archival ecosystems; records and recordkeeping.
While panels and presentations related to people, processes and power will be highlighted at the 2025 ACA Conference - with proposals approaching these topics in an intersectional manner especially encouraged - the Program Team will consider submissions exploring other areas.
The Call for Student Papers and a Call for Posters will be announced in early 2025. Scholarships are available to students and are administered by the ACA Foundation.
Feel free to direct questions to:
Patti Harper,
Chair, ACA 2025 Conference Program Team
Program Team Members:
Gracen Brilmyer
Cindy Custodio
Daniel German
Laura Hernandez
Shadio Hussein
Grace Isibor
Tracey Lauriault
Lisa Lawlis
Lisa Mullins
Rohini Singh
Adele Torrance
Gillian I Leitch, PhD
(She/Her)
Executive Director
t: 613-383-2009 c: 613-862-0021
Hope, Aaron (MPBSDP)
Hello RiC User Group,
I have a question about inferencing when using RiC-O alongside our datasets. When I import the RiC-O rdf file into my triplestore it is very helpful in doing certain things, such as allowing inverse relationships to be established between entities. However, another thing it does is to infer triples that make entities become instances of their super-classes. It likewise infers all the super-properties above the particular properties that are used explicitly. So, for example, a corporate body like the Highway Standards Branch in the government of Ontario is inferred to be also a Group, an Agent, and a Thing (green nodes in this visualization):
A particular object property, like the one asserting that the Highway Standards Branch is the successor (rico:isSuccessorOf) of the Highway Engineering Division results in four super-properties being inferred: rico:followsInTime, rico:isAgentAssociatedWithAgent, rico:followsOrFollowed, and rico:isRelatedTo.
This inferencing tends to clutter up the visualizations, since it shows super-classes and super-properties that are redundant for simple data exploration. Is there any easy way to configure visualizations to exclude these higher level classes and properties? The triplestore I’m using here is GraphDB.
Thanks for any tips!
Aaron Hope
Richard Williamson
https://graphdb.ontotext.com/documentation/10.8/inference.html
Id:cax_sco
c1 <rdfs:subClassOf> c2 [Constraint c1 != c2 ]
x <rdf:type> c1
-------------------------------
x <rdf:type> c2
Id: scm_rng1
p <rdfs:range> c1
c1 <rdfs:subClassOf> c2
-------------------------------
p <rdfs:range> c2
--
You received this message because you are subscribed to the Google Groups "Records_in_Contexts_users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Records_in_Context...@googlegroups.com.
Ivo Zandhuis
In the GraphDB v10.6 instance I use, I noticed a textbox "Advanced graph
configurations" after selecting "Visual graph" in the left hand menu. By
clicking on "Create graph config" you're able to configure a
visualisation. In the tab "Graph expansion" you can enter a SPARQL query
to define which nodes and edges you would like to visualise. Note that I
have not used it, so I might be on the wrong track, but this feels like
the right place to tinker.
Best regards,
Ivo Zandhuis
Richard Williamson schreef op 2025-03-27 16:27:
>> Highway Standards Branch is the successor (rico:isSuccessorOf) of
>> the Highway Engineering Division results in four super-properties
>> being inferred: rico:followsInTime, rico:isAgentAssociatedWithAgent,
>> rico:followsOrFollowed, and rico:isRelatedTo.
>>
>> This inferencing tends to clutter up the visualizations, since it
>> shows super-classes and super-properties that are redundant for
>> simple data exploration. Is there any easy way to configure
>> visualizations to exclude these higher level classes and properties?
>> The triplestore I’m using here is GraphDB.
>>
>> Thanks for any tips!
>>
>> Aaron Hope
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Records_in_Contexts_users" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to
>> Records_in_Context...@googlegroups.com.
>> To view this discussion visit
>>
> https://groups.google.com/d/msgid/Records_in_Contexts_users/YT2PR01MB942984BCCB8A56AE472F0F96F9A42%40YT2PR01MB9429.CANPRD01.PROD.OUTLOOK.COM
> --
> You received this message because you are subscribed to the Google
> Groups "Records_in_Contexts_users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to Records_in_Context...@googlegroups.com.
> To view this discussion visit
> [2].
>
>
> Links:
> ------
> [1]
> https://groups.google.com/d/msgid/Records_in_Contexts_users/YT2PR01MB942984BCCB8A56AE472F0F96F9A42%40YT2PR01MB9429.CANPRD01.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer
> [2]
> https://groups.google.com/d/msgid/Records_in_Contexts_users/CAOapDiLuW%2Bba%2BQbz6sZwjN%3DOhB8KOrz_0HzsgRG0Wm%2B6TYH6vQ%40mail.gmail.com?utm_medium=email&utm_source=footer
---
Ivo Zandhuis, PhD
Freelance consultant - Digital • Heritage • Humanities
Research Fellow - International Institute of Social History
Hope, Aaron (MPBSDP)
Thanks again!
Aaron
-----Original Message-----
From: records_in_c...@googlegroups.com <records_in_c...@googlegroups.com> On Behalf Of Ivo Zandhuis
Sent: Wednesday, April 2, 2025 8:57 AM
To: Records_in_C...@googlegroups.com
Subject: Re: [Records in Contexts users] Inferencing and visualizations using RiC-O
CAUTION -- EXTERNAL E-MAIL - Do not click links or open attachments unless you recognize the sender.
In the GraphDB v10.6 instance I use, I noticed a textbox "Advanced graph configurations" after selecting "Visual graph" in the left hand menu. By clicking on "Create graph config" you're able to configure a visualisation. In the tab "Graph expansion" you can enter a SPARQL query to define which nodes and edges you would like to visualise. Note that I have not used it, so I might be on the wrong track, but this feels like the right place to tinker.
Best regards,
Ivo Zandhuis
Richard Williamson schreef op 2025-03-27 16:27:
> Hello Aaron,
>
> Great that you took this up, I am sure there will be others interested
> in this! I have not really used GraphDB myself, but it seems that its
> inference rules are configured in '.pie' files that one can select:
>
> hdb.ontotext.com%2Fdocumentation%2F10.8%2Finference.html&data=05%7C02%
> 7Caaron.hope%40ontario.ca%7Cf432f58063bc46601db008dd71e5e8c7%7Ccddc122
> 9ac2a4b97b78a0e5cacb5865c%7C0%7C0%7C638791954458842859%7CUnknown%7CTWF
> pbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsI
> kFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=TzFAS7Dol%2BWkhEZGu
> %2BiDLEqmGO1lR6gKuR7uLJxMAlE%3D&reserved=0
> ps.google.com%2Fd%2Fmsgid%2FRecords_in_Contexts_users%2FYT2PR01MB94298
> 4BCCB8A56AE472F0F96F9A42%2540YT2PR01MB9429.CANPRD01.PROD.OUTLOOK.COM&d
> ata=05%7C02%7Caaron.hope%40ontario.ca%7Cf432f58063bc46601db008dd71e5e8
> c7%7Ccddc1229ac2a4b97b78a0e5cacb5865c%7C0%7C0%7C638791954458883009%7CU
> nknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiO
> iJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=i0m6iq7
> mA1bP5KVbERj4IPnhT78coIV4xIHlhsHiJ4k%3D&reserved=0
>
> --
> You received this message because you are subscribed to the Google
> Groups "Records_in_Contexts_users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to Records_in_Context...@googlegroups.com.
> To view this discussion visit
> ps.google.com%2Fd%2Fmsgid%2FRecords_in_Contexts_users%2FCAOapDiLuW%252
> Bba%252BQbz6sZwjN%253DOhB8KOrz_0HzsgRG0Wm%252B6TYH6vQ%2540mail.gmail.c
> om&data=05%7C02%7Caaron.hope%40ontario.ca%7Cf432f58063bc46601db008dd71
> e5e8c7%7Ccddc1229ac2a4b97b78a0e5cacb5865c%7C0%7C0%7C638791954458903565
> %7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsI
> lAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=PYj
> 4Uxby5dhBgQ9sPwWRYMeaLQKeEVyXxUpL6f9dJhk%3D&reserved=0
>
>
> Links:
> ------
> [1]
> ps.google.com%2Fd%2Fmsgid%2FRecords_in_Contexts_users%2FYT2PR01MB94298
> 4BCCB8A56AE472F0F96F9A42%2540YT2PR01MB9429.CANPRD01.PROD.OUTLOOK.COM%3
> Futm_medium%3Demail%26amp%3Butm_source%3Dfooter&data=05%7C02%7Caaron.h
> ope%40ontario.ca%7Cf432f58063bc46601db008dd71e5e8c7%7Ccddc1229ac2a4b97
> b78a0e5cacb5865c%7C0%7C0%7C638791954458917931%7CUnknown%7CTWFpbGZsb3d8
> eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTW
> FpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=j6PABjQeNhzWJ19UOGMXFSIAi%2F
> aNkjjIe5irJOJaEYA%3D&reserved=0
> [2]
> https://grou/
> ps.google.com%2Fd%2Fmsgid%2FRecords_in_Contexts_users%2FCAOapDiLuW%252
> Bba%252BQbz6sZwjN%253DOhB8KOrz_0HzsgRG0Wm%252B6TYH6vQ%2540mail.gmail.c
> om%3Futm_medium%3Demail%26utm_source%3Dfooter&data=05%7C02%7Caaron.hop
> e%40ontario.ca%7Cf432f58063bc46601db008dd71e5e8c7%7Ccddc1229ac2a4b97b7
> 8a0e5cacb5865c%7C0%7C0%7C638791954458933370%7CUnknown%7CTWFpbGZsb3d8ey
> JFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFp
> bCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=fjDIzMm2FOnc3Uq%2FEAYAfGw7jdHo
> f9Q6m%2FLvKlChEzY%3D&reserved=0
---
Ivo Zandhuis, PhD
Freelance consultant - Digital • Heritage • Humanities Research Fellow - International Institute of Social History
You received this message because you are subscribed to the Google Groups "Records_in_Contexts_users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to Records_in_Context...@googlegroups.com.
Hope, Aaron (MPBSDP)
Hello again RiC User Group,
I am sorry to trouble you again so soon, but I have a question about modelling successor relationships when these relate to people holding positions. It would seem inappropriate to use the rico:hasSuccessor object property to represent a relationship between
person A and person B when they succeed each other in a certain position, because the position is just one aspect of their life (it’s not like person B is succeeding person A’s whole life and activities, unless, perhaps in the case of a monarch or similar).
Doing so would, in my opinion, also leave unclear in what respect person B is succeeding person A.
However, if the position itself remains unchanged, it’s not possible to use rico:hasSuccessor between two separate instances of the rico:Position class.
The only option I can think of is to use two instances of the rico:PositionHoldingRelation class with dates assigned that indicate person B took over the position after person A’s end date, but this still feels incomplete since the succession isn’t explicitly
stated (and the domain of rico:hasSuccessor makes clear that it applies only to agents).
Thanks for any ideas – I’m probably just missing something obvious!
Cheers,
Aaron Hope
CLAVAUD Florence
Executive member of ICA/EGAD ; lead of RiC-O development team
Conservatrice générale du patrimoine | General curator
Responsable du Lab aux Archives nationales de France| head of the Lab, Archives nationales de France
Envoyé : vendredi 4 avril 2025 16:58
À : Records_in_C...@googlegroups.com <Records_in_C...@googlegroups.com>
Objet : [Records in Contexts users] Successor relationships between people holding positions
To unsubscribe from this group and stop receiving emails from it, send an email to Records_in_Context...@googlegroups.com.
Merci de nous aider à préserver l'environnement en n'imprimant ce courriel et les documents joints que si nécessaire.
CLAVAUD Florence
Envoyé : vendredi 4 avril 2025 18:09
À : Records_in_C...@googlegroups.com <Records_in_C...@googlegroups.com>
Objet : [Records in Contexts users] RE: Successor relationships between people holding positions
Hope, Aaron (MPBSDP)
Thank you Florence – extremely helpful and exactly what I was looking for. I do think the rico:asConcernsPosition property you suggested would be a good addition.
I’m looking forward to version 1.1. My thanks to you and all of EGAD for your work on this!
Cheers,
Aaron
From: records_in_c...@googlegroups.com <records_in_c...@googlegroups.com>
On Behalf Of CLAVAUD Florence
Sent: Friday, April 4, 2025 12:35 PM
To: records_in_c...@googlegroups.com
Subject: [Records in Contexts users] RE: Successor relationships between people holding positions
CAUTION -- EXTERNAL E-MAIL - Do not click links or open attachments unless you recognize the sender.
Just to add I was meaning "For now, there is no rico:asConcernsPosition" object property in RiC-O, with domain AgentTemporalRelation (just a rico:asConcernsActivity)."