PBCore can either include or reference data from other schemas to create a better, more comprehensive data record about an asset.
For example, rights information about an asset might already or best be described within a dedicated schema like the Open Digital Rights Language (ODRL):
<?xml version="1.0" encoding="UTF-8"?> <pbcoreDescriptionDocument xmlns="http://pbcore.org/PBCore/PBCoreNamespace.html" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://pbcore.org/PBCore/PBCoreNamespace.html> <pbcoreIdentifier source="MARS">XYZ1234</pbcoreIdentifier> <pbcoreTitle>The Most Amazing Thing</pbcoreTitle> <!-- section removed for clarity --> <pbcoreExtension> <extensionEmbedded> <o-ex:rights xmlns:o-ex="http://odrl.net/1.1/ODRL-EX" xmlns:o-dd="http://odrl.net/1.1/ODRL-DD" xmlns:ds="http://www.w3.org/2000/09/xmldsig#/" > <o-ex:context> <o-dd:version>1.0</o-dd:version> </o-ex:context> <o-ex:agreement> <o-ex:asset> <o-ex:context> <o-dd:uid>cid:20030131143739-1159123348@httpwww.addresss.comdddd</o-dd:uid </o-ex:context> </o-ex:asset> <o-ex:permission> <o-dd:display> <o-ex:constraint> <o-dd:count>100</o-dd:count> <o-dd:datetime> <o-dd:start>2003-01-31T14:32:27</o-dd:start> <o-dd:end>2004-01-31T14:32:27</o-dd:end> </o-dd:datetime> </o-ex:constraint> </o-dd:display> <o-dd:print/> </o-ex:permission> </o-ex:agreement> </o-ex:rights> </extensionEmbedded> </pbcoreExtension> </pbcoreDescriptionDocument>