Based on my comprehensive research, here’s the expanded section on Vocabularies and Authority Files:
\nVocabularies and Authority Files
\nGetty Vocabularies (as LOD)
\nThe Getty Vocabularies are comprehensive, multilingual controlled vocabularies for cultural heritage, available as Linked Open Data with extensive technical infrastructure:
\nArt & Architecture Thesaurus (AAT)
\n\t•\tContent: 57,390+ hierarchical concepts covering generic terms for art, architecture, decorative arts, materials, techniques, styles, and conservation
\n\t•\tScope: Work types, roles, materials, styles, cultures, techniques (e.g., amphora, oil paint, sintering)
\n\t•\tMultiple languages with ongoing expansion for multilingual and multicultural coverage
\n\t•\tURI pattern: http://vocab.getty.edu/aat/[ID]
\n\t•\tExample: http://vocab.getty.edu/aat/300198841 (rhyta)
\nUnion List of Artist Names (ULAN)
\n\t•\tContent: 367,590+ records with names, biographical information, and relationships
\n\t•\tCovers: Artists, architects, firms, studios, repositories, patrons, both named and anonymous entities
\n\t•\tIncludes variant names across languages and time periods
\n\t•\tURI pattern: http://vocab.getty.edu/ulan/[ID]
\n\t•\tExample: http://vocab.getty.edu/ulan/500115493 (Albrecht Dürer)
\n\t•\tLinks to biographical information at: http://vocab.getty.edu/ulan/[ID]-agent
\nGetty Thesaurus of Geographic Names (TGN)
\n\t•\tHierarchical geographic vocabulary
\n\t•\tCurrent and historical place names with coordinates
\n\t•\tMultiple language variants
\n\t•\tURI pattern: http://vocab.getty.edu/tgn/[ID]
\n\t•\tExample: http://vocab.getty.edu/tgn/7011179 (Siena)
\n\t•\tGeographic info at: http://vocab.getty.edu/tgn/[ID]-place
\nCultural Objects Name Authority (CONA)
\n\t•\tFocus: Architecture, multiples, works depicted in other works
\n\t•\tIncludes: Titles, artist attributions, creation dates, locations (extant or destroyed)
\n\t•\tExample works: Hagia Sophia, The Lacemaker, Great Wave off Kanagawa
\n\t•\tURI pattern: http://vocab.getty.edu/page/cona/[ID]
\n\t•\tAvailable through APIs (not yet as full LOD)
\nGetty Iconography Authority (IA)
\n\t•\tProper names for iconographical narratives, religious/fictional characters, historical events
\n\t•\tLiterary works and performing arts
\n\t•\tSpecial focus on non-Western subjects
\n\t•\tCoreferences to Iconclass for Western iconography
\n\t•\tExamples: Shiva, Avalokiteshvara, French Revolution, Xibalba
\n\t•\tAvailable through APIs (included with CONA Web Services)
\nAccess Methods:
\n\t•\tSPARQL endpoint: https://data.getty.edu/vocab/sparql
\n\t•\tSPARQL UI: https://data.getty.edu/vocab/sparql-ui
\n\t•\tActivity Stream: https://data.getty.edu/vocab/activity-stream
\n\t•\tFull downloads: N-Triples format (AAT, TGN, ULAN), refreshed monthly
\n\t•\tIndividual records: JSON, RDF/XML, N3/Turtle, N-Triples
\n\t•\tOpenRefine reconciliation service available
\n\t•\tNEW: Linked.Art semantic representation as default for JSON/JSON-LD
\nImportant Notes:
\n\t•\tLicense: Open Data Commons Attribution License (ODC-By) 1.0
\n\t•\tXML and Relational Tables formats being retired end of 2025
\n\t•\tLOD is the recommended sustainable format
\n\t•\tOver 90 sample SPARQL queries available in documentation
\n\t•\tDocumentation: https://www.getty.edu/research/tools/vocabularies/lod/
\nVIAF (Virtual International Authority File)
\nVIAF is a collaborative international authority file that virtually combines name authority files from national libraries and other institutions worldwide.
\nOverview:
\n\t•\tManaged by OCLC in cooperation with 37+ agencies from 29+ countries
\n\t•\tCombines: Library of Congress, Deutsche Nationalbibliothek, Bibliothèque nationale de France, and many others
\n\t•\t8+ million authority records for persons, corporate bodies, and works
\n\t•\tServes as an identity hub linking to multiple other authority sources
\nContent:
\n\t•\tPersonal names with variant forms across languages and scripts
\n\t•\tCorporate bodies
\n\t•\tConference names
\n\t•\tUniform titles
\n\t•\tBiographical information from contributing sources
\nURI Structure:
\n\t•\tCanonical URI: https://viaf.org/viaf/[numerical_ID]
\n\t•\tExample: https://viaf.org/viaf/15873 (Pablo Picasso)
\n\t•\tEach VIAF record asserts owl:sameAs relationships to corresponding entities in LC, Getty, Wikidata, DBpedia, etc.
\nAccess Methods:
\n\t•\tVIAF API: Search and retrieve authority records
\n\t•\thttps://www.oclc.org/developer/api/oclc-apis/viaf.en.html
\n\t•\tSupports keyword search, control number lookup
\n\t•\tReturns cluster records and source records
\n\t•\tContent negotiation: XHTML/RDFa, RDF/XML, N-Triples, JSON
\n\t•\tSRU search interface
\n\t•\tComplete data dumps: http://viaf.org/viaf/data/
\n\t•\tAvailable in RDF, MARC-21, plain text
\n\t•\tFiles last updated August 2024 (currently not being updated during infrastructure improvements)
\n\t•\tOpenRefine reconciliation endpoints available from third parties:
\n\t•\thttp://refine.codefork.com/reconcile/viaf
\n\t•\thttp://iphylo.org/~rpage/phyloinformatics/services/reconciliation_viaf.php
\nImportant Notes:
\n\t•\tLicense: Open Data Commons Attribution License (ODC-By) 1.0
\n\t•\tNo public SPARQL endpoint (though data available for local processing)
\n\t•\tHDT (Header Dictionary Triples) compressed versions available for efficient querying
\n\t•\tExperimental Linked Data Fragments servers available
\n\t•\tVIAF incorporated in ULAN and being integrated into other Getty vocabularies
\nGeoNames
\nGeoNames is a comprehensive geographical database with worldwide coverage, available as Linked Open Data.
\nOverview:
\n\t•\t11+ million geographical names
\n\t•\t9+ million unique features
\n\t•\t2.8+ million populated places
\n\t•\tMultilingual coverage
\nContent:
\n\t•\tPlace names with coordinates (WGS84)
\n\t•\tAdministrative divisions
\n\t•\tPostal codes
\n\t•\tPopulation data
\n\t•\tFeature classifications (mountains, rivers, cities, etc.)
\n\t•\tAlternate names in multiple languages
\n\t•\tHierarchical relationships between places
\nOntology:
\n\t•\tGeoNames Ontology: https://www.geonames.org/ontology/ontology_v3.3.rdf
\n\t•\tBased on W3C RDF and OWL standards
\n\t•\tCompatible with WGS84 positioning vocabulary
\nURI Structure:
\n\t•\tUses 303 redirection to distinguish concept from document
\n\t•\tConcept URI: https://sws.geonames.org/[ID]/
\n\t•\tRDF document: https://sws.geonames.org/[ID]/about.rdf
\n\t•\tExample: https://sws.geonames.org/3020251/ (Embrun, France)
\nAccess Methods:
\n\t•\tRDF/XML web service for individual features
\n\t•\tREST API for searches and queries
\n\t•\tSPARQL queries via third-party endpoints:
\n\t•\tGeoSPARQL.org: https://www.geosparql.org/
\n\t•\tFactForge: http://factforge.net/repositories/ff-news
\n\t•\tFull data dumps available for download
\n\t•\tOpenRefine reconciliation service
\nFormats:
\n\t•\tRDF/XML
\n\t•\tTurtle
\n\t•\tJSON
\n\t•\tGeoJSON for spatial queries
\nIntegration:
\n\t•\tWidely linked in LOD cloud
\n\t•\tUsed by DBpedia, Linked Geodata, and other major LOD datasets
\n\t•\tCompatible with GeoSPARQL for spatial queries
\nLibrary of Congress Linked Data Service (id.loc.gov)
\nThe Library of Congress provides comprehensive authority data and vocabularies as Linked Open Data.
\nAvailable Datasets:
\nLC Name Authority File (LCNAF)
\n\t•\t12+ million name authority records
\n\t•\tPersons, families, corporate bodies
\n\t•\tConference names
\n\t•\tURI pattern: http://id.loc.gov/authorities/names/[ID]
\nLibrary of Congress Subject Headings (LCSH)
\n\t•\tComprehensive subject authority file
\n\t•\tHierarchical relationships (broader, narrower, related terms)
\n\t•\tCross-linked with RAMEAU (French equivalent)
\n\t•\tURI pattern: http://id.loc.gov/authorities/subjects/[ID]
\nLC Classification (LCC)
\n\t•\tComplete classification scheme
\n\t•\tURI pattern: http://id.loc.gov/authorities/classification/[ID]
\nOther Vocabularies:
\n\t•\tLC Genre/Form Terms (LCGFT)
\n\t•\tLC Demographic Group Terms (LCDGT)
\n\t•\tLC Medium of Performance Thesaurus (LCMPT)
\n\t•\tThesaurus for Graphic Materials (TGM)
\n\t•\tMARC code lists and relators
\n\t•\tBIBFRAME vocabularies
\nAccess Methods:
\n\t•\tSearch interface: https://id.loc.gov/
\n\t•\tSuggest APIs (Suggest and Suggest2)
\n\t•\tSearch API with advanced query parameters:
\n\t•\tmemberOf, scheme, contentSource, rdftype filters
\n\t•\tToken search for LCCNs
\n\t•\tDate filters (cdate, mdate)
\n\t•\tContent negotiation for individual records
\n\t•\tNo SPARQL endpoint currently available
\nFormats:
\n\t•\tMADS/RDF and SKOS (where appropriate)
\n\t•\tXHTML/RDFa
\n\t•\tRDF/XML
\n\t•\tN-Triples
\n\t•\tJSON-LD
\n\t•\tBulk downloads available in all formats
\nImportant Features:
\n\t•\tLinks to external sources (Wikidata, GND, Getty, VIAF)
\n\t•\tUpdated regularly
\n\t•\tAPI documentation: https://id.loc.gov/techcenter/
\n\t•\tLicense: Public domain
\nIconclass
\nIconclass is the most widely accepted international classification system for iconographic research and subject indexing of visual arts.
\nOverview:
\n\t•\t28,000+ hierarchically ordered definitions
\n\t•\t14,000+ keywords in alphabetical index
\n\t•\tMultilingual: English, German, French, Italian, Finnish, Norwegian, with experimental Chinese and Dutch
\n\t•\tDeveloped by Henri van de Waal (1940s-1985)
\n\t•\tMaintained by Henri van de Waal Foundation and Iconclass Consortium
\nStructure:
\n\t•\t10 main divisions with alphanumeric notation codes
\n\t•\tHighly detailed hierarchies for Biblical and mythological subjects
\n\t•\tExpandable system with “keys” creating 1+ million possible notations
\n\t•\tWITH-NAMES placeholders (e.g., 11H(…) for male saints)
\n\t•\tExample notation: 71H7131 = “Bathsheba (alone) with David’s letter”
\nContent Coverage:
\n\t•\tReligious and mythological subjects
\n\t•\tHistorical events and narratives
\n\t•\tSecular subjects, objects, and concepts
\n\t•\tAbstract ideas
\n\t•\tActions and events depicted in art
\n\t•\tPre-iconographical through iconological interpretation levels
\nAccess as LOD:
\n\t•\tBase URI: http://iconclass.org/[notation]
\n\t•\tJSON format: http://iconclass.org/[notation].json
\n\t•\tRDF/SKOS format: http://iconclass.org/[notation].rdf
\n\t•\tExample: http://iconclass.org/52D1 or http://iconclass.org/52D1.rdf
\nData Dumps:
\n\t•\tComplete SKOS JSON-LD NDJSON dump: http://iconclass.org/data/iconclass_20200710_skos_jsonld.ndjson.gz
\n\t•\t~140MB compressed, 2GB+ uncompressed
\n\t•\tGitHub repository: https://github.com/iconclass/data
\n\t•\tPython library available
\nAPIs:
\n\t•\tBatch notation lookup: http://iconclass.org/json/?notation=25FF¬ation=51A
\n\t•\tNatural language search: http://iconclass.org/rkd/0/?q=lion&q_s=1&fmt=json
\n\t•\tProper URL encoding required for special characters
\nIntegration:
\n\t•\tLinks to AAT concepts for overlapping terminology
\n\t•\tIntegrated with Getty Iconography Authority
\n\t•\tUsed by major museums worldwide (Gemäldegalerie Berlin, RKD, etc.)
\n\t•\tBARTOC entry: https://bartoc.org/en/node/459
\nImportant Notes:
\n\t•\tFree access guaranteed by Iconclass Foundation
\n\t•\tConsortium membership available from July 2024
\n\t•\tExtensive bibliography (7 volumes, not yet online)
\n\t•\tBrowser interface: https://iconclass.org/
\nGND (Gemeinsame Normdatei / Integrated Authority File)
\nGND is the integrated authority file for German-speaking countries, increasingly used internationally.
\nOverview:
\n\t•\t9+ million authority records
\n\t•\tMaintained by German National Library (DNB) and GND Cooperative
\n\t•\tMerges former separate files: PND (personal names), GKD (corporate bodies), SWD (subject headings), EST (uniform titles)
\n\t•\tUsed by libraries, archives, museums, and research projects
\nEntity Types:
\n\t•\tPersons (differentiated persons)
\n\t•\tCorporate bodies and organizations
\n\t•\tConferences and events
\n\t•\tGeographic names and places
\n\t•\tSubject headings
\n\t•\tWorks (uniform titles)
\nAccess Methods:
\n\t•\tSPARQL endpoint (BETA): https://sparql.dnb.de/
\n\t•\tLobid-GND service: http://lobid.org/gnd/
\n\t•\tSearch interface
\n\t•\tJSON-LD API
\n\t•\tOpenRefine reconciliation: http://lobid.org/gnd/reconcile/
\n\t•\tDirect data access: https://data.dnb.de/opendata/
\n\t•\tOAI-PMH updates service
\nURI Structure:
\n\t•\tAuthority URI: https://d-nb.info/gnd/[GND-ID]
\n\t•\tExample: https://d-nb.info/gnd/118540238 (Johann Wolfgang von Goethe)
\nFormats Available:
\n\t•\tRDF/XML (complete downloads by entity type)
\n\t•\tMARC 21 Authority Format
\n\t•\tMARC21-XML
\n\t•\tJSON-LD
\n\t•\tTurtle
\n\t•\tEntityFacts (JSON-LD subset)
\nGND Ontology:
\n\t•\tSpecification: https://d-nb.info/standards/elementset/gnd
\n\t•\tRDF vocabulary for Semantic Web use
\n\t•\tCC0 1.0 Universal license
\n\t•\tScheduled releases: January, May, September
\n\t•\tMailing list for updates: http://lists.dnb.de/mailman/listinfo/gnd-ontology
\nData Downloads:
\n\t•\tFull dumps by category (geografikum, koerperschaft, kongress, person, sachbegriff, werk)
\n\t•\tAvailable as .rdf.gz files
\n\t•\tChange feed for incremental updates
\n\t•\tLast update tracking
\nImportant Features:
\n\t•\tLinks to VIAF, Wikidata, and other international authority files
\n\t•\tMultilingual with focus on German
\n\t•\tExpanding beyond library use to broader cultural sector
\n\t•\tPart of NFDI4Culture initiative
\n\t•\tLicense: CC0 1.0 Universal (for ontology); various for data
\nIntegration:
\n\t•\tIncorporated into VIAF
\n\t•\tCross-linked with LC authorities
\n\t•\tLinks to Getty vocabularies
\n\t•\tWikidata integration
\nAll of these vocabularies and authority files use standard Semantic Web technologies and are increasingly interconnected through owl:sameAs and other linking properties, forming a rich ecosystem of cultural heritage knowledge representation.
\n┌──────────────────────────┐
\n│ Frontend (Next.js 15) │
\n│ - Artwork/Entity pages │
\n│ - Auto-suggest fields │
\n│ - LOD enriched narrative│
\n└─────────────▲────────────┘
\n│ GraphQL/REST
\n┌─────────────┴────────────┐
\n│ API Gateway │
\n│ (.NET Aspire or Node) │
\n│ - LOD aggregation │
\n│ - Caching (Redis) │
\n│ - AI enrichment │
\n└─────────────▲────────────┘
\n│ SPARQL / APIs
\n┌─────────────┴─────────────────────┐
\n│ LOD Connectors / Microservices │
\n│ - Getty SPARQL │
\n│ - VIAF API │
\n│ - GeoNames API │
\n│ - LC suggest API │
\n│ - Iconclass API │
\n│ - LDAP / Wikidata │
\n└─────────────▲─────────────────────┘
\n│ URIs resolve
\n┌─────────────┴────────────────────┐
\n│ Triple Store (optional) │
\n│ Blazegraph / GraphDB / Jena │
\n│ - Stores enriched data │
\n│ - Fast semantic queries │
\n└─────────────▲────────────────────┘
\n│
\n┌─────────────┴────────────────────┐
\n│ AI Agents Layer │
\n│ - RAG narrative generator │
\n│ - Link discovery │
\n│ - Entity classification │
\n│ - Iconography suggestions │
\n└───────────────────────────────────┘
\n🌐 How to Use Getty, VIAF, LC, GeoNames, GND, Iconclass, Linked.Art, and AI Agents Together in a Modern Web App
\nFull technical architecture, full data flow, and implementation strategy.
\nNo tables. Fully detailed. Deep technical content.
\nA Linked Open Data web app does not merge datasets; instead it models your own domain objects (artworks, people, places, events, specimens, archives, books, etc.) and attaches URIs from established authority vocabularies.
\nEach vocabulary governs a specific knowledge domain.
\nYour local app stores your own JSON-LD records, but the “meaning” is always delegated to external URIs.
\nAn artwork references:
\n– AAT URIs for style, technique, material, object type
\n– ULAN/VIAF/LCNAF/GND for people
\n– TGN or GeoNames for places
\n– Iconclass or Getty IA for iconographic concepts
\n– CONA or other work authorities for related works
\n– LCSH or other subject vocabularies for subject descriptions
\nYour application becomes an orchestrator of distributed linked meaning.
\nThe data format that unifies everything is JSON-LD using the Linked.Art profile.
\nLinked.Art is built on CIDOC-CRM (semantic model) but expressed in a developer-friendly JSON-LD frame with stable classes like HumanMadeObject, Activity, Person, Place, Material, and Type.
\nA typical record includes URIs rather than string literals for anything with conceptual meaning.
\nThe app only stores its own URI plus URIs pointing outward.
\nEverything else—labels, descriptions, biographical data, multilingual names—is dereferenced from the authority services.
\nThe core of integrating multiple vocabularies is a URI resolver microservice within your web app architecture.
\nThis service receives any external URI and returns normalized JSON.
\nThe front-end (using React Server Components + Server Actions) fetches enriched data only when needed. You never fetch RDF directly in the browser.
\nThe flow:
\n– ULAN → person info
\n– AAT → terms (material, technique, etc.)
\n– TGN → place + coordinates
\n– Iconclass → iconography
\n– VIAF → crosslinks and variant names
\n– LC → subjects, work categories
\nThis results in:
\n– blazing fast load times
\n– SEO-compatible semantic HTML
\n– no CORS or RDF parsing in the client
\nYour back end uses the following integration strategies:
\nGetty AAT / ULAN / TGN:
\n– Query using the Getty SPARQL endpoint
\n– Content negotiation for Turtle/JSON-LD
\n– TGN geometry parsed into WGS84 coordinates
\nGND:
\n– SPARQL endpoint (sparql.dnb.de) for typed relationships
\n– GND-ontology URIs mapped to RDF types
\n– Lobid JSON-LD API for human-readable data
\nVIAF:
\n– XML or JSON cluster retrieval
\n– Matching algorithms for variant names
\n– Internal caching due to VIAF latency
\nIconclass:
\n– SKOS-based RDF through .rdf files
\n– JSON API for multi-notation lookup
\n– Use Iconclass “expanded_notation” for better faceting
\nLC Authorities:
\n– id.loc.gov Suggest API for autosuggest
\n– Content-negotiation to JSON-LD for individual entities
\n– MARC relators mapped to CRM properties
\nGeoNames:
\n– RDF endpoint for authoritative concepts
\n– REST API for population and feature code
\n– GeoJSON conversion for mapping UI
\nAll responses are normalized through internal vocabulary adapters (similar to how Wikidata’s “Frogmouth” model normalizes varied sources).
\nAI agents operate across three modes:
\nMode 1: Entity Extraction from Text
\nExtract person names, materials, styles, locations, iconography keywords.
\nMode 2: Entity Reconciliation
\nFor each extracted name or concept:
\n– Query ULAN and VIAF
\n– Score matches by lexical similarity, date overlap, role match
\n– Disambiguate “John Smith” using birth-death dates
\n– Link materials/techniques to AAT using cosine similarity on embeddings
\nMode 3: Narrative Construction
\nOnce entities are reconciled, the agent can produce:
\n– Biographical context
\n– Iconographic interpretation
\n– Material analysis
\n– Geographic mapping
\n– Historical timeline
\nThe agent uses:
\n– your triple store
\n– your resolver cache
\n– Wikidata and Getty cross-links
\n– a local vector index of enriched metadata
\n– a narrative schema for consistent output
\nThis creates dynamic interpretation layers over static LOD.
\nA triple store is not mandatory but gives you:
\n– inference of broader/narrower AAT types
\n– geographic containment (TGN/GeoNames)
\n– person roles and relationships (ULAN/GND)
\nWhen included, the triple store populates itself by:
\n– ingesting remote RDF from vocabularies
\n– ingesting your local JSON-LD
\n– running inference rules (Jena or GraphDB reasoners)
\nThis becomes the “semantic memory” for your AI agents.
\nA fully integrated LOD web app behaves like this:
\n– artist identity with cross-links
\n– biography with verified dates
\n– material and technique definitions from AAT
\n– iconography interpretation from Iconclass
\n– map visualization using GeoNames or TGN coordinates
\n– subject headings from LC
\n– hierarchical browsing (AAT broader/narrower terms)
\n– story of the work
\n– related works
\n– temporal and biographical contextualization
\n– inferred relationships not explicitly stated
\nYour website becomes a narrative knowledge graph powered by real LOD authorities.
\n– the complete code architecture
\n– the microservices
\n– the Next.js data fetching layer
\n– the .NET Aspire integration layer
\n– the resolver service
\n– the triple store ingestion scripts
\n– the AI agents for narrative enrichment
\n– or a fully deployable GitHub template
\nJust tell me:
\n“Generate the full LOD web app codebase.”
","updatedAt":"2018-10-20T01:46:40.000Z","checksum":"e0574a338aaa311a39f1f67788b99293a37781927a41c25c90b6da14c9166833","checksumPrefix":"e0574a338aaa","anchorCount":0,"lineCount":734,"rawUrl":"/api/docs/content?path=linked-art%2FVocabularies.md","htmlUrl":"/docs?doc=linked-art%2FVocabularies.md","apiUrl":"/api/docs/content?path=linked-art%2FVocabularies.md"}