How is "English" used in catalog systems?
In a common implementation of a SQL/relational database "English" would most likely be listed in multiple tables according to its usage.
No more tables!!! One ID to rule them all
The ID becomes your URI: The "Unique Resource Identifier" for the concept of the "English Language"
But wait a minute??? I have five different Identifiers for English in my old system for English. No Worries…just add an alias (owl:sameAs tag)
<http://myNameSpace.org/english>
owl:sameAs <http://id.loc.gov/authorities/subjects/sh85043413>,
<http://id.loc.gov/vocabulary/iso639-1/en>,
<http://id.loc.gov/vocabulary/iso639-2/eng>,
<http://id.loc.gov/vocabulary/languages/eng>,
<info:lc/vocabulary/languages/eng> .
Telling the system how to use a resource can be done by adding a RDF Type tag to your resource
<http://myNameSpace.org/english>
rdf:type bf:Language,
bf:Topic,
bfe:LocSubject,
<http://id.loc.gov/vocabulary/iso639-1/iso639-1_Language>,
<http://id.loc.gov/vocabulary/iso639-2/iso639-2_Language>.
Just add another owl:sameAs tag:
<http://myNameSpace.org/english>
owl:sameAs <http://dbpedia.org/resources/English_Language> .