• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Work with all your cloud files (Drive, Dropbox, and Slack and Gmail attachments) and documents (Google Docs, Sheets, and Notion) in one place. Try Dokkio (from the makers of PBworks) for free. Now available on the web, Mac, Windows, and as a Chrome extension!


RDF Definition - Person

Page history last edited by Antony Briggs 5 years ago


@prefix rdf:  <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix dct:  <http://purl.org/dc/terms/>
@prefix foaf: <http://xmlns.com/foaf/0.1/>
@prefix void: <http://rdfs.org/ns/void#>
@prefix bl: <http://http://www.bl.uk/ns#>
@prefix owl: <http://www.w3.org/2002/07/owl#>
@prefix bio: <http://purl.org/vocab/bio/0.1/>
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>


Base URI

Example URL: http://www.bl.uk/people/samuel-taylor-coleridge

Item source

/sitecore/content/Home/People BL_Global_Page_Person, BL_Global_Page_Person_NonDisplayable


Example URL: http://www.bl.uk/people/samuel-taylor-coleridge#person

Items in /sitecore/content/Home/People can be of template BL_Global_Page_Person_NonDisplayable or BL_Global_Page_Person_NonDisplayable

Item definition

PropertyValue SourceSample ValueNotes
rdf:type Fixed

foaf:Agent, foaf:Person, dc:Agent

same as BNB
foaf:name BL_Global_Page_Person_NonDisplayable:FirstName +
BL_Global_Page_Person_NonDisplayable:MiddleName +
"Samuel Taylor Coleridge"  
foaf:familyName BL_Global_Page_Person_NonDisplayable:LastName "Coleridge"  
foaf:givenName BL_Global_Page_Person_NonDisplayable:FirstName +
"Samuel Taylor"  
owl:sameAs BL_Global_Inherited_LibraryOfCongress:LCUri http://id.loc.gov/authorities/names/n81004092 if populated
owl:sameAs ? http://bnb.data.bl.uk/doc/person/ColeridgeSamuelTaylor1772-1834 V2: Link to the BNB resources for people, if appropriate
bl:occupation BL_Global_Page_Person_NonDisplayable:Occupation "Poet" String Literal from CMS
base URI + #birth
bio:birth is more specific but have used with bio:event to match BNB
base URI + #death
bl:genre BL_Global_Inherited_Genre:Genre "Romantic Literature" String Literal from CMS
bl:literaryPeriod BL_Global_Inherited_LiteraryPeriod:LiteraryPeriod "Romantic" String Literal from CMS
wdrs:describedBy base URI Example URL: http://www.bl.uk/people/samuel-taylor-coleridge
Resource which describes the person



Example URL: http://www.bl.uk/people/samuel-taylor-coleridge#birth

 Item definition

PropertyValue SourceSample ValueNotes
rdf:type Fixed bio:Birth  
  • BirthDateFrom
  • BirthDateDisplay 




if XXXDateFrom is populated, the and xsd:date is generated

If not, then XXXDateDisplay is examined for a 4 digit number and if found a xsd:gYear is generated. This is the same logic as the website.

? (see above)
"Mary, Devon, England"

V2: The BNB has URIs for places in the form:

&lt;http://bnb.data.bl.uk/id/place/ChapelHill&gt; a geo:SpatialThing, dc:Location; rdfs:label "Chapel Hill".



Example URL: http://www.bl.uk/people/samuel-taylor-coleridge#death

Item definition

PropertyValue SourceSample ValueNotes
rdf:type Fixed bio:Birth  
bio:date ? (see #birth above)




See above
? (see #birth above)
"Highgate, London, England"



See also: Common Definitions

Comments (3)

corine deliot said

at 12:05 pm on Sep 29, 2016


Re: use of owl:sameAs. The relationship between the Person modelled as a foaf:Person and the entity defined at id.loc.gov is not owl:sameAs because the latter has been modelled as a skos:Concept. In the Linked Open BNB, we use madsrdf:isIdentifiedByAuthority. See http://www.loc.gov/standards/mads/rdf/#t32

Thanks, Corine

Elliot Smith said

at 9:45 am on Oct 7, 2016

Another option would be to create an owl:sameAs to the person Samuel Taylor Coleridge on the id.co.gov site - http://id.loc.gov/rwo/agents/n81004092 - which is a foaf:Person.

Other comments:

1. In RES, we index resources with the rdf:type <http://purl.org/NET/c4dm/event.owl#Event>. If the birth/death dates also had this type, you could associate them with geo:SpatialThing triples, which would enable more accurate location finding.
2. The bio:place is a string literal; it would be better if this were a a dbpedia resource, as this would enable apps using geographic data to find this event (e.g. imagine an app which shows birthplaces of famous people around the UK). (The semantics of the bio schema allow this.)
3. I'm not sure about genre and literary period as properties of people. It would make more sense to me if these were removed. The genre/literary period could be inferred via the relationships between a person and their works/articles/items.
4. void:dataset should probably be void:inDataset.

Richard Light said

at 12:24 pm on Oct 7, 2016

In general I would avoid using owl:sameAs completely. There is (for example) skos:exactMatch and skos:closeMatch, which don't have the apocalyptic consequences of owl:sameAs.

Re birth dates, my guess is that 'from' and 'to' are to capture uncertainty about the date, rather than duration of the event, i.e. they should be 'earliest' and 'latest'.

It looks as though place URLs e.g. http://bnb.data.bl.uk/id/place/ChapelHill do resolve to something, but don't return any useful information about the place. I agree that dbpedia (or Geonames) would be better.

You don't have permission to comment on this page.