Vocabularies for classicists: Difference between revisions
(Added CTS) |
(Reintroduced CTS, but with caveat) |
||
| Line 17: | Line 17: | ||
''It is helpful to understand something about the hierarchy of texts (such as the one adopted by [http://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records Functional Requirements for Bibliographic Records] [FRBR]). Vocabularies describing ancient works in the abstract (under FRBR called works) will take a different approach than ones describing manuscripts, papyri, ostraca, etc. (under FRBR called items)'' | ''It is helpful to understand something about the hierarchy of texts (such as the one adopted by [http://en.wikipedia.org/wiki/Functional_Requirements_for_Bibliographic_Records Functional Requirements for Bibliographic Records] [FRBR]). Vocabularies describing ancient works in the abstract (under FRBR called works) will take a different approach than ones describing manuscripts, papyri, ostraca, etc. (under FRBR called items)'' | ||
* [http://purl.org/spar/cito/ Citation Ontology] | * [http://purl.org/spar/cito/ Citation Ontology] | ||
* [http://datahub.io/dataset/linkedlccn Linked LCCN] | * [http://datahub.io/dataset/linkedlccn Linked LCCN] | ||
| Line 25: | Line 23: | ||
* [http://www.w3.org/TR/prov-o/# W3C Provenance Ontology] | * [http://www.w3.org/TR/prov-o/# W3C Provenance Ontology] | ||
* [http://wiki.digitalclassicist.org/Sharing_Ancient_Wisdoms_%28SAWS%29 SAWS Ontology for recording links within interrelated collections of texts] | * [http://wiki.digitalclassicist.org/Sharing_Ancient_Wisdoms_%28SAWS%29 SAWS Ontology for recording links within interrelated collections of texts] | ||
Note, that although the following are not vocabularies per se, they are important for the creation of vocabularies or RDF triples that involve ancient texts: | |||
* [http://cts3.sourceforge.net/ Canonical Text Services] (CTS) | |||
* [http://sites.tufts.edu/perseusupdates/beta-features/perseus-cts-api/ Perseus] (uses CTS) | |||
== Geography == | == Geography == | ||
Revision as of 19:51, 8 April 2013
Classicists working on digital projects that involve data are encouraged to link their data to the semantic web. If you are new to the topic, start here (Linked open data).
In thinking about new vocabularies, whether for subjects, predicates, or objects of triples, one should begin with a survey of what already exists. By using one another's vocabularies, we reinforce the interoperability, and therefore utility, of our data. And it saves the time of having to reinvent the wheel. Below are a selection of vocabularies that may be useful to classicists.
General
- RDF Vocabulary Description Language, also known as RDF Schema (RDFS)
- Web Ontology Language (OWL)
- Simple Knowledge Organization System (SKOS)
- Dublin Core
- Friend of a Friend
- Wikipedia
- DBPedia
- Cayless, ontology for Linked Open World Data (Apr. 2013: preliminary notes for material that will eventually populate LAWD.info)
See a list of others here. See here for a visual map.
Bibliography and Texts
It is helpful to understand something about the hierarchy of texts (such as the one adopted by Functional Requirements for Bibliographic Records [FRBR]). Vocabularies describing ancient works in the abstract (under FRBR called works) will take a different approach than ones describing manuscripts, papyri, ostraca, etc. (under FRBR called items)
- Citation Ontology
- Linked LCCN
- Marc Codes List
- Open Annotation
- W3C Provenance Ontology
- SAWS Ontology for recording links within interrelated collections of texts
Note, that although the following are not vocabularies per se, they are important for the creation of vocabularies or RDF triples that involve ancient texts:
- Canonical Text Services (CTS)
- Perseus (uses CTS)
Geography
- NeoGeo Spatial Ontology
- Geonames
- Linked GeoData
- Pleiades Place/Location/Name Vocabulary
- Pleiades Places
Prosopography, persons
Objects
Topics
For other examples of projects that use controlled vocabularies for linked open data, see the category listing as well as Very clean URIs.