Presentation about usability of linked data, following LODLAM 2020 at the Getty. Discusses JSON-LD 1.1, IIIF, Linked Art, in the context of the design principles for building usable APIs on top of semantically accurate models, and domain specific vocabularies.
In particular a focus on the different abstraction layers between conceptual model, ontology, vocabulary, and application profile and the various uses of the data.
Standards and Communities: Connected People, Consistent Data, Usable Applicat...Robert Sanderson
Keynote presentation at JCDL 2019 at UIUC, on the interaction between standards (development and usage) and communities. Looking at Linked Open Data, digital library protocols, and evaluation of standards practices.
Sanderson CNI 2020 Keynote - Cultural Heritage Research Data EcosystemRobert Sanderson
There have been, and continue to be, many initiatives to address the social, technological, financial and policy-based challenges that throw up roadblocks towards achieving this vision. However, it is hard to tell whether we are making progress, or whether we are eternally waiting for the hyperloop that will never come. If we are to ever be able to answer research questions that require a broad, international corpus of cultural data, then we need an ecosystem that can be characterized with 5 “C”s: Collaborative, Consistent, Connected, Correct and Contextualized. Each of these has implications for the sustainability, innovation, usability, timeliness and ethical considerations that must be addressed in a coherent and holistic manner. As with autonomous vehicles, technology (and perhaps even machine “intelligence”) is a necessary but insufficient component.
In this presentation, I will frame and motivate this grand challenge and propose where we can build connections between the academy, the cultural heritage sector, and industry. The discussion will explore the issues, and highlight some of the successful endeavors and more approachable opportunities where, together, progress can be made.
Linked Art: Sustainable Cultural Knowledge through Linked Open Usable DataRobert Sanderson
An introduction to Linked Art - why we need it, what it is, and how it works. A great starting point if you're interested in linked open usable data in cultural heritage, especially art museums.
Illusions of Grandeur: Trust and Belief in Cultural Heritage Linked Open DataRobert Sanderson
What is the notion of trust, when it comes to publishing linked open data in the cultural heritage sector? This presentation discusses some aspects with relation to three primary questions: How do we trust what was said, trust that the institution said it, and trust what it means?
Invited seminar for UIUC's IS 575 class on metadata in theory and practice, about structural metadata practice in RDF/LOD. Touches on OAI-ORE, PCDM, Annotation, IIIF and Linked Art. Challenges explored are graph boundaries, APIs and context specific metadata.
IIIF and Linked Data: A Cultural Heritage DAM EcosystemRobert Sanderson
Presentation at DAMLA, November 15 2017, on the adoption of the IIIF image interoperability APIs across the Cultural Heritage sector for access to digital assets. How Linked Open Data then provides interoperable discovery solutions for that content.
Tiers of Abstraction and Audience in Cultural Heritage Data ModelingRobert Sanderson
A walk through of a framework based around the distinctions between Abstraction, Implementation and Audience for considering the value and utility of data modeling patterns and paradigms in cultural heritage information systems. In particular, a focus on CIDOC-CRM, BibFrame, RiC-CM/RiC-O, EDM, and IIIF, with the intent to demonstrate best practices and anti-patterns in modeling.
Standards and Communities: Connected People, Consistent Data, Usable Applicat...Robert Sanderson
Keynote presentation at JCDL 2019 at UIUC, on the interaction between standards (development and usage) and communities. Looking at Linked Open Data, digital library protocols, and evaluation of standards practices.
Sanderson CNI 2020 Keynote - Cultural Heritage Research Data EcosystemRobert Sanderson
There have been, and continue to be, many initiatives to address the social, technological, financial and policy-based challenges that throw up roadblocks towards achieving this vision. However, it is hard to tell whether we are making progress, or whether we are eternally waiting for the hyperloop that will never come. If we are to ever be able to answer research questions that require a broad, international corpus of cultural data, then we need an ecosystem that can be characterized with 5 “C”s: Collaborative, Consistent, Connected, Correct and Contextualized. Each of these has implications for the sustainability, innovation, usability, timeliness and ethical considerations that must be addressed in a coherent and holistic manner. As with autonomous vehicles, technology (and perhaps even machine “intelligence”) is a necessary but insufficient component.
In this presentation, I will frame and motivate this grand challenge and propose where we can build connections between the academy, the cultural heritage sector, and industry. The discussion will explore the issues, and highlight some of the successful endeavors and more approachable opportunities where, together, progress can be made.
Linked Art: Sustainable Cultural Knowledge through Linked Open Usable DataRobert Sanderson
An introduction to Linked Art - why we need it, what it is, and how it works. A great starting point if you're interested in linked open usable data in cultural heritage, especially art museums.
Illusions of Grandeur: Trust and Belief in Cultural Heritage Linked Open DataRobert Sanderson
What is the notion of trust, when it comes to publishing linked open data in the cultural heritage sector? This presentation discusses some aspects with relation to three primary questions: How do we trust what was said, trust that the institution said it, and trust what it means?
Invited seminar for UIUC's IS 575 class on metadata in theory and practice, about structural metadata practice in RDF/LOD. Touches on OAI-ORE, PCDM, Annotation, IIIF and Linked Art. Challenges explored are graph boundaries, APIs and context specific metadata.
IIIF and Linked Data: A Cultural Heritage DAM EcosystemRobert Sanderson
Presentation at DAMLA, November 15 2017, on the adoption of the IIIF image interoperability APIs across the Cultural Heritage sector for access to digital assets. How Linked Open Data then provides interoperable discovery solutions for that content.
Tiers of Abstraction and Audience in Cultural Heritage Data ModelingRobert Sanderson
A walk through of a framework based around the distinctions between Abstraction, Implementation and Audience for considering the value and utility of data modeling patterns and paradigms in cultural heritage information systems. In particular, a focus on CIDOC-CRM, BibFrame, RiC-CM/RiC-O, EDM, and IIIF, with the intent to demonstrate best practices and anti-patterns in modeling.
An introduction to the linked.art LOD data model, based on a carefully selected profile of CIDOC-CRM, and expressed as JSON-LD. It focuses on developer happiness and data usability, while trying to also maintain as much of the richness of CRM as possible.
A walkthrough of the CIDOC-CRM based, LOD data model developed and maintained at https://linked.art/ for describing cultural heritage resources and activities.
A Perspective on Wikidata: Ecosystems, Trust, and UsabilityRobert Sanderson
Brief and skeptical presentation about wikidata and its potential for use and abuse in the cultural heritage data ecosystem, presented at the PCC/LDAC forum on wikidata, November 12th, 2021.
US2TS Conference position paper on publishing and retrieving not just LOD, but LOUD -- Linked Open Usable Data.
APIs are the UIs of Developers, and need:
* Correct Abstraction level for the Audience
* Few Barriers to Entry
* Comprehensible by introspection
* Thorough Documentation with copy-able examples
* Few Exceptions, instead consistent patterns
Community Challenges for Practical Linked Open Data - Linked Pasts keynoteRobert Sanderson
A call to action to discuss and agree on practical considerations around the creation, publication and discovery of linked open data about historical activities and objects.
Text of approximately what I said: http://bit.ly/usable_lod
To be useful, Linked Open Data requires shared identities and the reuse of their identifiers (URIs). This presentation argues that exact identity matching is both theoretically and practically impossible, and proposes some practical considerations for how to create an actual web of data.
Presented as invited seminar at UC Berkeley, February 24th, 2017
Digital Share 2017 presentation about Linked Open Data at The Getty, starting from what LOD is, to why we're interested in it, and some of the practical approaches we're using to make it real.
A non-technical introduction to Linked Data, from a Cultural Heritage organization's perspective. This presentation is from the Provenance Index workshop at the Getty in 2016, with an emphasis on why Linked Data is valuable, as well as how it works in general. [Please see speaker notes for explanations of image slides]
American Art Collaborative Planning Grant Educational Briefings
Linked Data and Tools
Pedro Szekely - USC/Information Sciences Institute
September 30, 2014
Background for linked open data at the J Paul Getty Trust, followed by a summary of Linked Open Usable Data, and an initial walkthrough of the https://linked.art/ model.
Social Semantic Web on Facebook Open Graph protocol and Twitter AnnotationsMyungjin Lee
This Presentation show what the Social Semantic Web is and how Facebook Open Graph protocol and Twitter Annotations colligate with the Social Semantic Web.
This presentation was provided by Rob Sanderson of the J. Paul Getty Trust during the NISO Virtual Conference, Open Data Projects, held on Wednesday, June 13, 2018.
An introduction to the linked.art LOD data model, based on a carefully selected profile of CIDOC-CRM, and expressed as JSON-LD. It focuses on developer happiness and data usability, while trying to also maintain as much of the richness of CRM as possible.
A walkthrough of the CIDOC-CRM based, LOD data model developed and maintained at https://linked.art/ for describing cultural heritage resources and activities.
A Perspective on Wikidata: Ecosystems, Trust, and UsabilityRobert Sanderson
Brief and skeptical presentation about wikidata and its potential for use and abuse in the cultural heritage data ecosystem, presented at the PCC/LDAC forum on wikidata, November 12th, 2021.
US2TS Conference position paper on publishing and retrieving not just LOD, but LOUD -- Linked Open Usable Data.
APIs are the UIs of Developers, and need:
* Correct Abstraction level for the Audience
* Few Barriers to Entry
* Comprehensible by introspection
* Thorough Documentation with copy-able examples
* Few Exceptions, instead consistent patterns
Community Challenges for Practical Linked Open Data - Linked Pasts keynoteRobert Sanderson
A call to action to discuss and agree on practical considerations around the creation, publication and discovery of linked open data about historical activities and objects.
Text of approximately what I said: http://bit.ly/usable_lod
To be useful, Linked Open Data requires shared identities and the reuse of their identifiers (URIs). This presentation argues that exact identity matching is both theoretically and practically impossible, and proposes some practical considerations for how to create an actual web of data.
Presented as invited seminar at UC Berkeley, February 24th, 2017
Digital Share 2017 presentation about Linked Open Data at The Getty, starting from what LOD is, to why we're interested in it, and some of the practical approaches we're using to make it real.
A non-technical introduction to Linked Data, from a Cultural Heritage organization's perspective. This presentation is from the Provenance Index workshop at the Getty in 2016, with an emphasis on why Linked Data is valuable, as well as how it works in general. [Please see speaker notes for explanations of image slides]
American Art Collaborative Planning Grant Educational Briefings
Linked Data and Tools
Pedro Szekely - USC/Information Sciences Institute
September 30, 2014
Background for linked open data at the J Paul Getty Trust, followed by a summary of Linked Open Usable Data, and an initial walkthrough of the https://linked.art/ model.
Social Semantic Web on Facebook Open Graph protocol and Twitter AnnotationsMyungjin Lee
This Presentation show what the Social Semantic Web is and how Facebook Open Graph protocol and Twitter Annotations colligate with the Social Semantic Web.
This presentation was provided by Rob Sanderson of the J. Paul Getty Trust during the NISO Virtual Conference, Open Data Projects, held on Wednesday, June 13, 2018.
Linked Open Data is great for recommendations about publishing data, but we need five more stars for the consumer -- How can it be both complete and usable? Design principles for Linked Open Usable Data.
An introduction to Linked Open Usable Data (LOUD) through the lens of a zooming paradigm, and thoughts on how such a paradigm can help to address some grand challenges of LOUD, including search granularity, trust and reconciliation. Presented to the IDLab / Knowledge at Web Scale department of the University of Ghent in Feb '23
A talk about the gap between theory and practice with W3C Semantic Web and Dublin Core standards, and how the DC Tools Community can help collectively reduce the cost of that gap.
Given as part of the DC Tools Community workshop at LIDA2009 in Zadar, Croatia.
Presented January 18, 2010 to the ALCTS Committee on Cataloging: Description and Access (CC:DA) as an introduction to RDF data, and application profiles. Presenters were Jon Phipps, Karen Coyle and Diane Hillmann.
In this talk I review some of the early visions of the Semantic Web, some of the different views, and I follow through on a thread of how Semantic Web technology has been adopted in search engines (and other companies). I end with a challenge to the research community to keep pursuing this research, rather than letting industry take over the "low end" and keep new work from flourishing.
The current status of Linked Open Data (LOD) shows evidence of many datasets available on the Web in RDF. In the meantime, there are still many challenges to overcome by organizations in their journey of publishing five stars datasets on the Web. Those challenges are not only technical, but are also organizational. At this moment where connectionist AI is gaining a wave of popularity with many applications, LOD needs to go beyond the guarantee of FAIR principles. One direction is to build a sustainable LOD ecosystem with FAIR-S principles. In parallel, LOD should serve as a catalyzer for solving societal issues (LOD for Social Good) and personal empowerment through data (Social Linked Data).
A presentation given at the International Image Interoperability Framework event held at the New York Academy of Medicine in New York City on May 11, 2016.
Rob Sanderson
The Getty
Intelligent Expert systems can provide decisions for users for estimate from user preferences to find better destination from user profits. this present provides description of above system and suggest new approach for next researches.
A walk through of the Linked Art data model, API and community processes. Presented originally at the Rijksmuseum for the 5th Linked Art face to face meeting. Linked Art is a linked open usable data specification created by the community to describe artwork, museum objects, and related bibliographic and archival content.
LUX - Cross Collections Cultural Heritage at YaleRobert Sanderson
A brief presentation based on the CNI talk for the Linked Data for Libraries Discovery affinity group about LUX, Linked Open Usable Data and our discovery processes based on graphs rather than documents.
Data is our Product: Thoughts on LOD SustainabilityRobert Sanderson
Invited keynote presentation for the LINCS Project, June 23rd 2022 at the University of Guelph, Canada. It describes thoughts on a framework for sustainability of linked open usable data products in the cultural heritage domain.
Euromed2018 Keynote: Usability over Completeness, Community over CommitteeRobert Sanderson
Discussion of cultural heritage issues around usability and prioritization with completeness, and focus on bringing together communities rather than small and transient committees. Focus on Linked Open Usable Data, Annotations, JSON-LD, IIIF and Linked.Art.
Discussion of the needs around updating Shared Canvas data model for IIIF's Presentation API, and aligning with new work such as the Web Annotation specs.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
11. @azaroth42
rsanderson
@getty.edu
IIIF:Interoperabilituy
TheImportanceof
BeingLOUD
@azaroth42
Successful APIs …
• Solve actual challenges, documented as use cases
• Using data that is captured and available
• Allow consistent implementation of shared use cases
• Allow for addition of further functionality
• Can be productively used
• Via easy-to-implement services
• With easy-to-implement applications
• Provide interoperability between data and systems
• Are clearly documented with relevant examples
20. @azaroth42
rsanderson
@getty.edu
IIIF:Interoperabilituy
TheImportanceof
BeingLOUD
@azaroth42
IIIF Design Patterns
1. Scope design through shared use cases
2. Design for international use
3. As simple as possible, but no simpler
4. Make easy things easy, complex things possible
5. Avoid dependency on specific technologies
6. Use REST / Don’t break the web
7. Separate concerns, keep APIs loosely coupled
8. Design for JSON-LD, using LOD principles
9. Follow existing standards, best practices, when possible
10. Define success, not failure (for extensibility)
https://iiif.io/api/annex/notes/design_patterns/
21. @azaroth42
rsanderson
@getty.edu
IIIF:Interoperabilituy
TheImportanceof
BeingLOUD
@azaroth42
Is IIIF Actually LOUD?
• IIIF is JSON-LD ... used as if it were JSON
• IIIF APIs are focused on Presentation, not Semantics
• Usability considered more important than Precision
• Document structure / graph boundary is enforced by
the API specifications
• Presentation: Collection, Manifest
• Image: Info.json
• Discovery, Search: Stream/Results, Page
22. @azaroth42
rsanderson
@getty.edu
IIIF:Interoperabilituy
TheImportanceof
BeingLOUD
@azaroth42
Is IIIF Actually LOUD?
• Discovery (and paging) use W3C ActivityStreams
• Also not very Linked
• Also very successful
• Annotations are the only core affordance that cross
institutional boundaries
• Services and Extensibility are important facets that
rely on Linked Data
• Image and Presentation 3.0 use JSON-LD 1.1 as it
is intended to be used …
29. @azaroth42
rsanderson
@getty.edu
IIIF:Interoperabilituy
TheImportanceof
BeingLOUD
@azaroth42
Linked Art Model
A Linked Open Usable Data model, collaboratively designed
to work across cultural heritage organizations, that is easy
to publish and enables a variety of consuming applications.
Design Principles:
• Focused on Usability, not 100% precision / completeness
• Consistently solves actual challenges from real data
• Development is iterative, as new use cases are found
• Solve 90% of use cases, with 10% of the effort
30. @azaroth42
rsanderson
@getty.edu
IIIF:Interoperabilituy
TheImportanceof
BeingLOUD
@azaroth42
Linked Art Collaboration
Working to formalize the profile, funded by Kress & AHRC
• Getty
• Rijksmuseum
• Louvre
• Metropolitan Museum of Art
• Smithsonian
• MoMA
• V&A
• NGA
• Philadelphia Art Museum
• Indianapolis Art Museum
• The Frick Collection
• Harvard University
• Princeton University
• Yale Centre for British Art
• Oxford University
• Academica Sinica
• ETH Zurich
• FORTH
• Zeri Foundation (U. Bologna)
• Canadian Heritage Info. Network
• American Numismatics Society
• Europeana
I think Many Sporny perfectly captured the sentiment: When developers hear “RDF” or “the Semantic Web” or “SPARQL” they think: Not in my back yard, people have died from that stuff!
Michael Barth has six fundamental features for API evaluation, which relate directly to the value of the API as a standard for use. This seems like a good starting point for standards for digital interoperability.
Abstraction Level -- is the abstraction of the data and functionality appropriate to the audience and use cases. An end user of the "car" API presses a button or turns a key. A "car" developer needs access to engine directly.
Comprehensibility -- is the audience able to understand how to use it to accomplish their goals
Consistency -- if you know the "rules" of the API, how well does it stick to them? Or how many exceptions are there to a core set of design principles
Documentation -- How easy is it to find out the functionality of the API?
Domain Correspondence -- If you understand the core domain of the data and API, how closely does the understanding of the domain align with an understanding of the data?
And what barriers to getting started are there?
There are two more that I think are important.
Need to have the rules of the game before two systems can interact
Need to have the rules of the game before two systems can interact
The core functionality. Not just an image tag, but also not photoshop on the web.
Just enough information to present the context of the images in a way that the user can understand what they’re interacting with. Structure of the object and its metadata in a pre-processed form for rendering in a client … so not a semantic metadata API.
The community engagement with JSON-LD has been unprecedented, notably due to Google’s adoption of it and the usability focus of schema.org.
Intent of a profile is to select only the relevant parts of the lower level definitions that are needed.
Further restrict the model / ontology to ensure that the data is usable.
Less important for IIIF to be complete as it’s about presentation not semantics. But for semantic description…
E22 HumanMadeObject is the ontology term for the class of Human Made Objects in the conceptual model, and type is the relationship between things and their classes.
The label is a constructed piece of text to label the resource, in the absence of any other data. Intended for developers looking at the data, not intended for directly being displayed to “real” humans.
Turns out that there are two sorts of things that speak in numbers … computers, and librarians.
That should help. We use the Getty’s Art and Architecture Thesaurus.
That should help. We use the Getty’s Art and Architecture Thesaurus.
We know that this is the primary name, because it was called title, not alternate title.
We know that this is the primary name, because it was called title, not alternate title.
And now we’re at the 50’ foot view, with an activity in the middle and who, what, when and where around the outside.
Models for all of these other entities as well to capture useful knowledge for shared use cases.
No one has all of the knowledge, and to try to gather everything together and keep it persistently available and up to date is impossible below the scale of Google.
No one has all of the knowledge, and to try to gather everything together and keep it persistently available and up to date is impossible below the scale of Google.