Dear TopBraid Composer Users, I manage the Library of Congress's Linked Data Service, http://id.loc.gov/ . We are in the process of adding a new feature to LC's Linked Data Service designed to more easily make use of the available data by providing a simple way to import the data into OWL ontologies, especially via OWL editors such as TopBraid Composer. Although we've not published it widely yet, I thought TBC users, who could also benefit from this work, might be interested.
Quick backstory: Quite sometime ago, we published a number of vocabularies and value lists as MADS/RDF Authorities, SKOS Concepts, and RDF Resources, all as Linked Data. These include a few ISO language lists for which we are the registration and/or maintenance authority: ISO 639-1 Languages, ISO 639-2 Languages, and ISO 639-5 Languages And a few lists originally created for the MARC Bibliographic format for which we also assigned URIs: Languages, Countries, GeographicAreas, and Relators (Relators are really to be used as Object Properties) Although the data made available (URIs, labels, etc) are useable in ontologies and OWL editors such as TBC as is, our own use cases have led us to simplify the process of making use of them in ontologies and OWL editors. To this end, we've modified the output so that the data are readily understandable by an OWL editor (for example, we output rdfs:label for the label properties in addition to skos:prefLabel and madsrdf:authoritativeLabel because OWL editors appear pre-configured to understand rdfs:label and not necessarily skos:prefLabel) and we've created mini-ontologies designed for import into other ontologies. The idea is that the mini-ontology will import all that is needed to make use of the vocabularies and value lists in an user-friendly manner. For example, to make use of the ISO639-1 Languages, using TBC, one could import the following ontology: http://id.loc.gov/ontologies/iso639-1_Languages This will import all the ISO639-1 Language resources, and required data (such as labels and RDF types), and the ISO639-1 Language Class (also defined by LC). Once imported, you would then define an Object Property, the range of which is a resource that is an instance of an ISO639-1 Language (http://id.loc.gov/vocabulary/iso639-1/iso639-1_Language). The following URIs resolve to the mini-ontologies we've created: http://id.loc.gov/ontologies/iso639-1_Languages http://id.loc.gov/ontologies/iso639-2_Languages http://id.loc.gov/ontologies/iso639-5_Languages http://id.loc.gov/ontologies/MARC_Languages http://id.loc.gov/ontologies/MARC_GeographicAreas http://id.loc.gov/ontologies/MARC_Countries (The following is a list of properties) http://id.loc.gov/ontologies/Roles Please feel welcome to try these out in your own ontologies. Feedback (suggestions, quibbles, good/bad) is welcome. Cordially, Kevin -- Kevin Ford Network Development and MARC Standards Office Library of Congress Washington, DC -- You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include Enterprise Vocabulary Network (EVN), TopBraid Composer, TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/topbraid-users?hl=en
