Andy Powell, profile picture
Uploaded byAndy Powell
PPT, PDF829 views

What’s in a structured value?

The document discusses representing structured values in metadata records using the Dublin Core metadata element set. It provides examples of representing creator information and subject terms as structured values using the Dublin Core terms dc:creator and dc:subject. The examples show how to assign URIs to the values, link them to related metadata descriptions, and store the metadata in separate documents rather than embedding it in each record. This allows the structured information to be centrally defined while still linking it to individual resource descriptions.

Embed presentation

Downloaded 15 times
What’s in a structured value? Andy Powell UKOLN, University of Bath
Background for some time DC has had a slightly fuzzy notion of things called ‘structured values’ DCSV recommendation, complex data-structures in RDF/XML, use of vCard, use of things like DC.Creator.Address, etc. with the exception of RDF/XML, these tend to be fairly ad hoc attempts to squeeze ‘structured’ information into DC records
Simple DC model a simple DC record is made up of one or more properties and their associated values each property is an attribute of the resource being described each property must be one of the 15 DCMES elements properties may be repeated each value is a string each string value may have an associated language (e.g. en-GB)
Qualified DC model a qualified DC record is made up of one or more properties and their associated values each property is an attribute of the resource being described each property must be either: one of the elements recommended by the DCMI (i.e. the 15 DC elements and audience), one of the DCMI element refinements
Qualified DC model (2) properties may be repeated each value is a string each value may have an associated encoding scheme each encoding scheme has a URI each string value may have an associated language (e.g. en-GB)
But… qualified DC model too simple w.r.t RDF not able to support requirements coming out of DC Agents WG sometimes the value string isn’t just a string… sometimes it is a string that contains some structure i.e. sometimes it is a ‘structured value’
Types of structured values labelled strings DCSV (DC Box, …), OpenURL, vCard unlabelled strings W3CDTF markup HTML markup (various flavours), XML-based markup (CML, MathML, …), or non-XML markup such as TeX related resource descriptions full vCard, DC.Creator.Address, RDF
Definitions a “structured value” is a string that contains machine-parsable component parts (and which has an associated “syntax encoding scheme” that indicates how the component parts are encoded within the string) a string value that includes some markup a description of a related resource
Name and identifiers as values dc:creator, dc:contributor, dc:publisher, dc:relation, dc:source name or identify a related resource identifiers typically in the form of a URI names typically in the form of person or organisation name (sometimes with the addition of extra information)
Linking/embedding requirement in the case of these 5 elements, there appears to be a requirement to form linkage between description of resource and description of one or more related resources i.e. between the resource being described and the resource that is named or identified by the element achieved by embedding or linking
Example 1 – dc:creator <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> Example RDF description using dc:creator…
Example 1 – dc:creator dc:creator Andy Powell… my:affiliation a.powell@uko… my:email … and the RDF model it represents. UKOLN, Univ… a.powell@uko… Andy Po… rdfs:label my:name <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF>
Example 1 – dc:creator dc:creator Andy Powell… my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… rdfs:label my:name But… we don’t want to embed all this information into every instance metadata record do we? relatedMetadata <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF>
Example 1 – dc:creator dc:creator Andy Powell… rdfs:label my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… my:name Need to separate part of the information out and store it in a single place – in this case in a directory service… <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <my:name> Andy Powell </my:name> <my:email> [email_address] </my:email> </rdf:Description> </rdf:RDF>
Example 1 – dc:creator valueURI dc:creator Andy Powell… rdfs:label valueURI my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… my:name To do this we need to assign a URI (the ‘valueURI’) to the anonymous ‘value’ node… <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <my:name> Andy Powell </my:name> <my:email> [email_address] </my:email> </rdf:Description> </rdf:RDF>
Example 1 – dc:creator valueURI dc:creator Andy Powell… rdfs:label valueURI my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… my:name relatedMetadataURI The document containing this information is itself an RDF resource (the ‘relatedMetadata’) and has a URI <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <my:name> Andy Powell </my:name> <my:email> [email_address] </my:email> </rdf:Description> </rdf:RDF>
Example 1 – dc:creator valueURI dc:creator Andy Powell… rdfs:label valueURI my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… my:name relatedMetadataURI rdfs:seeAlso Use rdf:seeAlso to form linkage between description and relatedMetadata… <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF>
Example 2 – dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> Example RDF description using dc:subject (taken from Qualified DC in RDF recommendation…
Example 2 – dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> dcterms:MESH dc:subject rdf:type D08.586… rdf:type rdfs:label Formated… rdfs:value … and the RDF model it represents.
Example 2 – dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> dcterms:MESH dc:subject rdf:type rdf:type But… we don’t want to embed all this information into every instance metadata record do we? relatedMetadata D08.586… rdfs:label Formated… rdfs:value
Example 2 – dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> dcterms:MESH D08.586… Formated… Need to separate part of the information out and store it in a single place – in this case with the terminology owner… rdfs:label Formated…
Example 2 – dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> valueURI dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> valueURI dcterms:MESH D08.586… Formated… To do this we need to assign a URI (the ‘valueURI’) to the anonymous ‘value’ node… rdfs:label Formated…
Example 2 – dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> valueURI dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> valueURI dcterms:MESH D08.586… Formated… relatedMetadataURI The document containing this information is itself an RDF resource (the ‘relatedMetadata’) and has a URI rdfs:label Formated…
Example 2 – dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> valueURI dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> valueURI dcterms:MESH D08.586… Formated… relatedMetadataURI rdfs:seeAlso Use rdf:seeAlso to form linkage between description and relatedMetadata… rdfs:label Formated…
Abstract DC model <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> valueURI dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> valueURI dcterms:MESH D08.586… Formated… relatedMetadataURI rdfs:seeAlso resource property valueURI valueString In terms of abstract DC model we now have: resource, property, valueURI, valueString (and valueStringLang), encodingScheme, relatedMetadata resource property valueURI relatedMetadata encodingScheme rdfs:label Formated… valueString (valueStringLang)
Need to extend abstract model each [DCMI property] ‘value’ has a ‘valueURI’ each ‘value’ has a ‘valueString’ each ‘valueString’ may have an ‘encoding scheme’ each ‘encoding scheme’ has a URI each ‘valueString’ may have a ‘language’ each ‘value’ may have a linked or embedded ‘complexValue’ (markup or related resource description)
relatedMetadata related resource description known as ‘relatedMetadata’ particular encoding syntaxes may support instantiation of relatedMetadata by embedding explicit link using ‘relatedMetadataURI’ both
Qualified DC model a qualified DC record is made up of one or more properties and their associated values each property is an attribute of the resource being described each property must be either: one of the elements recommended by the DCMI (i.e. the 15 DC elements and audience), one of the DCMI element refinements properties may be repeated
Qualified DC model (2) each value may have a valueURI each value may have a valueString each valueString may have an associated encoding scheme each encoding scheme has a URI each valueString may have an associated language (e.g. en-GB) each value may have a linked or embedded complexValue ( markup or relatedMetadata )

More Related Content

PPT
RDF and OWL
byRachel Lovinger
 
PPT
Understanding RDF: the Resource Description Framework in Context (1999)
byDan Brickley
 
PPT
Dublin Core Basic Syntax Tutorial
byEduserv Foundation
 
PPT
Everything you wanted to know about Dublin Core metadata
byEduserv Foundation
 
PDF
Rdf data-model-and-storage
by灿辉 葛
 
PDF
Efficient Query Answering against Dynamic RDF Databases
byAlexandra Roatiș
 
PPT
Data in RDF
byEmanuele Della Valle
 
PPT
Introduction To RDF and RDFS
byNilesh Wagmare
 
RDF and OWL
byRachel Lovinger
 
Understanding RDF: the Resource Description Framework in Context (1999)
byDan Brickley
 
Dublin Core Basic Syntax Tutorial
byEduserv Foundation
 
Everything you wanted to know about Dublin Core metadata
byEduserv Foundation
 
Rdf data-model-and-storage
by灿辉 葛
 
Efficient Query Answering against Dynamic RDF Databases
byAlexandra Roatiș
 
Data in RDF
byEmanuele Della Valle
 
Introduction To RDF and RDFS
byNilesh Wagmare
 

What's hot

PPT
Introduction to RDF
byNarni Rajesh
 
PPTX
469 talk
byAlisonNoel
 
PPT
Semantic web
bytariq1352
 
ODP
Dublin core Presentation
byMary Jo Chrabasz
 
PDF
Semantic Web(Web 3.0) SPARQL
byDaniel D.J. UM
 
ODP
Xml Overview
bykevinreiss
 
PPT
Rdf
byImran Babar
 
PDF
Jesús Barrasa
byConnected Data World
 
PDF
Debunking some “RDF vs. Property Graph” Alternative Facts
byNeo4j
 
PPT
Rdf Overview Presentation
byKen Varnum
 
PDF
RDF Tutorial - SPARQL 20091031
bykwangsub kim
 
PPT
Ist16-04 An introduction to RDF
byEmanuele Della Valle
 
PPT
Ontologies in RDF-S/OWL
byEmanuele Della Valle
 
PDF
Introduction to DTD
bytorp42
 
PPT
4 xml namespaces and xml schema
bygauravashq
 
PDF
Two graph data models : RDF and Property Graphs
byandyseaborne
 
PPT
2 dtd - validating xml documents
bygauravashq
 
PPT
An Introduction to the DCMI Abstract Model
byEduserv Foundation
 
PPTX
Introduction to XML
byAbhra Basak
 
PPT
RDF briefing
byFrank van Harmelen
 
Introduction to RDF
byNarni Rajesh
 
469 talk
byAlisonNoel
 
Semantic web
bytariq1352
 
Dublin core Presentation
byMary Jo Chrabasz
 
Semantic Web(Web 3.0) SPARQL
byDaniel D.J. UM
 
Xml Overview
bykevinreiss
 
Rdf
byImran Babar
 
Jesús Barrasa
byConnected Data World
 
Debunking some “RDF vs. Property Graph” Alternative Facts
byNeo4j
 
Rdf Overview Presentation
byKen Varnum
 
RDF Tutorial - SPARQL 20091031
bykwangsub kim
 
Ist16-04 An introduction to RDF
byEmanuele Della Valle
 
Ontologies in RDF-S/OWL
byEmanuele Della Valle
 
Introduction to DTD
bytorp42
 
4 xml namespaces and xml schema
bygauravashq
 
Two graph data models : RDF and Property Graphs
byandyseaborne
 
2 dtd - validating xml documents
bygauravashq
 
An Introduction to the DCMI Abstract Model
byEduserv Foundation
 
Introduction to XML
byAbhra Basak
 
RDF briefing
byFrank van Harmelen
 

Viewers also liked

PPT
Open, social and linked - what do current Web trends tell us about the future...
byAndy Powell
 
PPT
Open for Business - Open Archives, OpenURL, RSS and the Dublin Core
byAndy Powell
 
PPT
The Open Archives Initiative Protocol for Metadata Harvesting
byAndy Powell
 
PPT
The JISC Information Environment and collection description
byAndy Powell
 
PPTX
Linked Data as an enabling framework for resource discovery across libraries,...
byAndy Powell
 
PPTX
Open, social and linked - A ménage à trois of content exploitation
byAndy Powell
 
PPTX
The Google Book Settlement - and what it means for learners and researchers i...
byAndy Powell
 
PPT
Content packaging and MPEG-21 DID
byAndy Powell
 
Open, social and linked - what do current Web trends tell us about the future...
byAndy Powell
 
Open for Business - Open Archives, OpenURL, RSS and the Dublin Core
byAndy Powell
 
The Open Archives Initiative Protocol for Metadata Harvesting
byAndy Powell
 
The JISC Information Environment and collection description
byAndy Powell
 
Linked Data as an enabling framework for resource discovery across libraries,...
byAndy Powell
 
Open, social and linked - A ménage à trois of content exploitation
byAndy Powell
 
The Google Book Settlement - and what it means for learners and researchers i...
byAndy Powell
 
Content packaging and MPEG-21 DID
byAndy Powell
 

Similar to What’s in a structured value?

PDF
SPARQL and the Open Linked Data initiative
byFulvio Corno
 
PPT
A Semantic Multimedia Web (Part 2)
byRaphael Troncy
 
PPT
Publishing data on the Semantic Web
byPeter Mika
 
PDF
Introduction to RDF
byDr Sukhpal Singh Gill
 
PPTX
SWT Lecture Session 2 - RDF
byMariano Rodriguez-Muro
 
PDF
Graph databases & data integration v2
byDimitris Kontokostas
 
PPTX
Linked data and rdf
byDaniel Nüst
 
PPTX
Lecture the semantic_web_part_2
byIKS - Project
 
PDF
An introduction to Semantic Web and Linked Data
byFabien Gandon
 
KEY
RDFa Introductory Course Session 2/4 How RDFa
byPlatypus
 
KEY
How RDFa works
byJISC Netskills
 
PDF
Introduction to RDF & SPARQL
byOpen Data Support
 
PPT
Rdf And Rdf Schema For Ontology Specification
bychenjennan
 
PPTX
Sem webmaubeuge
byJose Emilio Labra Gayo
 
PDF
RDF: what and why plus a SPARQL tutorial
byJerven Bolleman
 
PPT
DC-Text: a simple text-based format for DC metadata
byEduserv Foundation
 
PPTX
Creating Linked Data 2/5 Semtech2011
byJuan Sequeda
 
PDF
2011 4IZ440 Semantic Web – RDF, SPARQL, and software APIs
byJosef Petrák
 
PDF
Using MongoDB as a high performance graph database
byChris Clarke
 
PPT
RDFa: The Semantic Web's Missing Link
byMark Birbeck
 
SPARQL and the Open Linked Data initiative
byFulvio Corno
 
A Semantic Multimedia Web (Part 2)
byRaphael Troncy
 
Publishing data on the Semantic Web
byPeter Mika
 
Introduction to RDF
byDr Sukhpal Singh Gill
 
SWT Lecture Session 2 - RDF
byMariano Rodriguez-Muro
 
Graph databases & data integration v2
byDimitris Kontokostas
 
Linked data and rdf
byDaniel Nüst
 
Lecture the semantic_web_part_2
byIKS - Project
 
An introduction to Semantic Web and Linked Data
byFabien Gandon
 
RDFa Introductory Course Session 2/4 How RDFa
byPlatypus
 
How RDFa works
byJISC Netskills
 
Introduction to RDF & SPARQL
byOpen Data Support
 
Rdf And Rdf Schema For Ontology Specification
bychenjennan
 
Sem webmaubeuge
byJose Emilio Labra Gayo
 
RDF: what and why plus a SPARQL tutorial
byJerven Bolleman
 
DC-Text: a simple text-based format for DC metadata
byEduserv Foundation
 
Creating Linked Data 2/5 Semtech2011
byJuan Sequeda
 
2011 4IZ440 Semantic Web – RDF, SPARQL, and software APIs
byJosef Petrák
 
Using MongoDB as a high performance graph database
byChris Clarke
 
RDFa: The Semantic Web's Missing Link
byMark Birbeck
 

More from Andy Powell

PDF
The OCRE Cloud Framework
byAndy Powell
 
PPTX
Shared responsibility - a model for good cloud security
byAndy Powell
 
PPTX
Building the modern institution: how Jisc can support your cloud-based digita...
byAndy Powell
 
PPTX
Developing a Cloud Based Infrastructure to Transform Working Practices and Se...
byAndy Powell
 
PPTX
Open data as an enabler of citizen engagement
byAndy Powell
 
PPTX
AWS Bath User Group - Meetup #2
byAndy Powell
 
PPTX
AWS IoT: a cloud platform for building IoT applications
byAndy Powell
 
PDF
Internet of Car Parks - a discussion about IoT
byAndy Powell
 
PPTX
Digital Marketplace/G-Cloud - the good, the bad and the ugly
byAndy Powell
 
PPTX
G cloud - what is it?
byAndy Powell
 
PPTX
IT : Strategy, management and DIY in HE - a breakout group summary
byAndy Powell
 
PPTX
Eduserv Education Cloud
byAndy Powell
 
PPTX
Eduserv Education Cloud
byAndy Powell
 
PPTX
UK university adoption of ‘shared’ cloud services
byAndy Powell
 
PPTX
UMF Cloud Pilot
byAndy Powell
 
PPTX
UMF Cloud Pilot: architecturing an IaaS offer for higher education
byAndy Powell
 
PPTX
RDTF Metadata Guidelines: an update
byAndy Powell
 
PPTX
Unified Social Sign-on
byAndy Powell
 
PPTX
What current trends tell us about the future of federated access management i...
byAndy Powell
 
PPTX
Linked data - the long and winding road
byAndy Powell
 
The OCRE Cloud Framework
byAndy Powell
 
Shared responsibility - a model for good cloud security
byAndy Powell
 
Building the modern institution: how Jisc can support your cloud-based digita...
byAndy Powell
 
Developing a Cloud Based Infrastructure to Transform Working Practices and Se...
byAndy Powell
 
Open data as an enabler of citizen engagement
byAndy Powell
 
AWS Bath User Group - Meetup #2
byAndy Powell
 
AWS IoT: a cloud platform for building IoT applications
byAndy Powell
 
Internet of Car Parks - a discussion about IoT
byAndy Powell
 
Digital Marketplace/G-Cloud - the good, the bad and the ugly
byAndy Powell
 
G cloud - what is it?
byAndy Powell
 
IT : Strategy, management and DIY in HE - a breakout group summary
byAndy Powell
 
Eduserv Education Cloud
byAndy Powell
 
Eduserv Education Cloud
byAndy Powell
 
UK university adoption of ‘shared’ cloud services
byAndy Powell
 
UMF Cloud Pilot
byAndy Powell
 
UMF Cloud Pilot: architecturing an IaaS offer for higher education
byAndy Powell
 
RDTF Metadata Guidelines: an update
byAndy Powell
 
Unified Social Sign-on
byAndy Powell
 
What current trends tell us about the future of federated access management i...
byAndy Powell
 
Linked data - the long and winding road
byAndy Powell
 

Recently uploaded

PDF
The Sheep and the Goat: Beckett’s Subversion of Divine Justice in Waiting for...
bysejadchokiya
 
PDF
Bones by Sadu Kassam (play) story ppt pdf
byRonnieMaeBorres
 
PPTX
Methods & Applications of Enzyme Immobilization Technique.pptx
byAnupkumar Sharma
 
PPTX
How to perform product search based on a custom field from the Website Shop p...
byCeline George
 
PDF
java full stack programming and interview questions
byrajuashokit
 
PPTX
Problem and Solution (PowerPoint Game Template)
byacpaulite
 
PDF
Structure-of-the-Atom PPT.pdf/CBSE CLASS 11 CHEMISTRY/ PREPARED BY K SANDEEP ...
bySandeep Swamy
 
PPTX
WEEK 2 (2).pptx TLE COOKERY 10 QUARTER 4
byResynFayeCortez2
 
PPTX
How to Add an Icon in Systray in Odoo 18
byCeline George
 
PPTX
Math 8 Quarter 4 Week 4-SECONDARY DATA.pptx
byshahanieabbat3
 
PDF
Artificial Intelligence in Research and Academic Writing, Workshop on Researc...
byProf. Vinod Kumar Kanvaria
 
PPTX
How to Manage Reservation Method in Odoo 18 Inventory
byCeline George
 
PPTX
Renal Physiology- Functional anatomy of Kidney.pptx
byDisha Soriya
 
PDF
Nursing care plan for Vomiting /B.Sc nsg
byDr. Sudhadevi Sadanandan
 
PPTX
Greengnorance Toolkit Module 5 Waste Management
byKarl Donert
 
PDF
Holm Community Heritage at St Nicholas Kirk - 2025 AGM Minutes (30.04.2025)
byAntoine Pietri
 
PDF
Chapter 05 Drugs Acting on the Central Nervous System: Anti-Depressant Drugs
bySandeshSul
 
PPTX
Fluorimetric Analysis- Theory, Instrumentation and Application
bySayali Powar
 
PPTX
How to Track & Manage My Time Section in Odoo 18 Time Off
byCeline George
 
PDF
Chapter 05 Drugs Acting on the Central Nervous System: Anticonvulsant (Antiep...
bySandeshSul
 
The Sheep and the Goat: Beckett’s Subversion of Divine Justice in Waiting for...
bysejadchokiya
 
Bones by Sadu Kassam (play) story ppt pdf
byRonnieMaeBorres
 
Methods & Applications of Enzyme Immobilization Technique.pptx
byAnupkumar Sharma
 
How to perform product search based on a custom field from the Website Shop p...
byCeline George
 
java full stack programming and interview questions
byrajuashokit
 
Problem and Solution (PowerPoint Game Template)
byacpaulite
 
Structure-of-the-Atom PPT.pdf/CBSE CLASS 11 CHEMISTRY/ PREPARED BY K SANDEEP ...
bySandeep Swamy
 
WEEK 2 (2).pptx TLE COOKERY 10 QUARTER 4
byResynFayeCortez2
 
How to Add an Icon in Systray in Odoo 18
byCeline George
 
Math 8 Quarter 4 Week 4-SECONDARY DATA.pptx
byshahanieabbat3
 
Artificial Intelligence in Research and Academic Writing, Workshop on Researc...
byProf. Vinod Kumar Kanvaria
 
How to Manage Reservation Method in Odoo 18 Inventory
byCeline George
 
Renal Physiology- Functional anatomy of Kidney.pptx
byDisha Soriya
 
Nursing care plan for Vomiting /B.Sc nsg
byDr. Sudhadevi Sadanandan
 
Greengnorance Toolkit Module 5 Waste Management
byKarl Donert
 
Holm Community Heritage at St Nicholas Kirk - 2025 AGM Minutes (30.04.2025)
byAntoine Pietri
 
Chapter 05 Drugs Acting on the Central Nervous System: Anti-Depressant Drugs
bySandeshSul
 
Fluorimetric Analysis- Theory, Instrumentation and Application
bySayali Powar
 
How to Track & Manage My Time Section in Odoo 18 Time Off
byCeline George
 
Chapter 05 Drugs Acting on the Central Nervous System: Anticonvulsant (Antiep...
bySandeshSul
 

What’s in a structured value?

  • 1.
    What’s in astructured value? Andy Powell UKOLN, University of Bath
  • 2.
    Background for sometime DC has had a slightly fuzzy notion of things called ‘structured values’ DCSV recommendation, complex data-structures in RDF/XML, use of vCard, use of things like DC.Creator.Address, etc. with the exception of RDF/XML, these tend to be fairly ad hoc attempts to squeeze ‘structured’ information into DC records
  • 3.
    Simple DC modela simple DC record is made up of one or more properties and their associated values each property is an attribute of the resource being described each property must be one of the 15 DCMES elements properties may be repeated each value is a string each string value may have an associated language (e.g. en-GB)
  • 4.
    Qualified DC modela qualified DC record is made up of one or more properties and their associated values each property is an attribute of the resource being described each property must be either: one of the elements recommended by the DCMI (i.e. the 15 DC elements and audience), one of the DCMI element refinements
  • 5.
    Qualified DC model(2) properties may be repeated each value is a string each value may have an associated encoding scheme each encoding scheme has a URI each string value may have an associated language (e.g. en-GB)
  • 6.
    But… qualified DCmodel too simple w.r.t RDF not able to support requirements coming out of DC Agents WG sometimes the value string isn’t just a string… sometimes it is a string that contains some structure i.e. sometimes it is a ‘structured value’
  • 7.
    Types of structuredvalues labelled strings DCSV (DC Box, …), OpenURL, vCard unlabelled strings W3CDTF markup HTML markup (various flavours), XML-based markup (CML, MathML, …), or non-XML markup such as TeX related resource descriptions full vCard, DC.Creator.Address, RDF
  • 8.
    Definitions a “structuredvalue” is a string that contains machine-parsable component parts (and which has an associated “syntax encoding scheme” that indicates how the component parts are encoded within the string) a string value that includes some markup a description of a related resource
  • 9.
    Name and identifiersas values dc:creator, dc:contributor, dc:publisher, dc:relation, dc:source name or identify a related resource identifiers typically in the form of a URI names typically in the form of person or organisation name (sometimes with the addition of extra information)
  • 10.
    Linking/embedding requirement inthe case of these 5 elements, there appears to be a requirement to form linkage between description of resource and description of one or more related resources i.e. between the resource being described and the resource that is named or identified by the element achieved by embedding or linking
  • 11.
    Example 1 –dc:creator <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> Example RDF description using dc:creator…
  • 12.
    Example 1 –dc:creator dc:creator Andy Powell… my:affiliation a.powell@uko… my:email … and the RDF model it represents. UKOLN, Univ… a.powell@uko… Andy Po… rdfs:label my:name <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF>
  • 13.
    Example 1 –dc:creator dc:creator Andy Powell… my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… rdfs:label my:name But… we don’t want to embed all this information into every instance metadata record do we? relatedMetadata <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF>
  • 14.
    Example 1 –dc:creator dc:creator Andy Powell… rdfs:label my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… my:name Need to separate part of the information out and store it in a single place – in this case in a directory service… <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <my:name> Andy Powell </my:name> <my:email> [email_address] </my:email> </rdf:Description> </rdf:RDF>
  • 15.
    Example 1 –dc:creator valueURI dc:creator Andy Powell… rdfs:label valueURI my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… my:name To do this we need to assign a URI (the ‘valueURI’) to the anonymous ‘value’ node… <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <my:name> Andy Powell </my:name> <my:email> [email_address] </my:email> </rdf:Description> </rdf:RDF>
  • 16.
    Example 1 –dc:creator valueURI dc:creator Andy Powell… rdfs:label valueURI my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… my:name relatedMetadataURI The document containing this information is itself an RDF resource (the ‘relatedMetadata’) and has a URI <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <my:name> Andy Powell </my:name> <my:email> [email_address] </my:email> </rdf:Description> </rdf:RDF>
  • 17.
    Example 1 –dc:creator valueURI dc:creator Andy Powell… rdfs:label valueURI my:affiliation a.powell@uko… my:email UKOLN, Univ… a.powell@uko… Andy Po… my:name relatedMetadataURI rdfs:seeAlso Use rdf:seeAlso to form linkage between description and relatedMetadata… <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF> <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:my=&quot;http://purl.org…&quot;> <rdf:Description> <dc:creator> <rdf:Description> <rdf:value> Andy Powell </rdf:value> <my:email> [email_address] </my:email> </rdf:Description> </dc:creator> </rdf:Description> </rdf:RDF>
  • 18.
    Example 2 –dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> Example RDF description using dc:subject (taken from Qualified DC in RDF recommendation…
  • 19.
    Example 2 –dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> dcterms:MESH dc:subject rdf:type D08.586… rdf:type rdfs:label Formated… rdfs:value … and the RDF model it represents.
  • 20.
    Example 2 –dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> dcterms:MESH dc:subject rdf:type rdf:type But… we don’t want to embed all this information into every instance metadata record do we? relatedMetadata D08.586… rdfs:label Formated… rdfs:value
  • 21.
    Example 2 –dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> dcterms:MESH D08.586… Formated… Need to separate part of the information out and store it in a single place – in this case with the terminology owner… rdfs:label Formated…
  • 22.
    Example 2 –dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> valueURI dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> valueURI dcterms:MESH D08.586… Formated… To do this we need to assign a URI (the ‘valueURI’) to the anonymous ‘value’ node… rdfs:label Formated…
  • 23.
    Example 2 –dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> valueURI dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> valueURI dcterms:MESH D08.586… Formated… relatedMetadataURI The document containing this information is itself an RDF resource (the ‘relatedMetadata’) and has a URI rdfs:label Formated…
  • 24.
    Example 2 –dc:subject <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> valueURI dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> valueURI dcterms:MESH D08.586… Formated… relatedMetadataURI rdfs:seeAlso Use rdf:seeAlso to form linkage between description and relatedMetadata… rdfs:label Formated…
  • 25.
    Abstract DC model<?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <rdf:Description> <dc:subject> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> </dcterms:MESH> </dc:subject> </rdf:Description> </rdf:RDF> valueURI dcterms:MESH dc:subject rdf:type rdf:type <?xml version=&quot;1.0&quot;?> <rdf:RDF xmlns:rdf=http://www…. xmlns:rdfs=http://www.w3.org/… xmlns:dc=http://purl.org/dc/… xmlns:dcterms=&quot;http://purl.org…&quot;> <dcterms:MESH> <rdf:value> D08.586.682.075.400 </rdf:value> <rdfs:label> Formate Dehydrogenase </rdfs:label> </dcterms:MESH> </rdf:RDF> valueURI dcterms:MESH D08.586… Formated… relatedMetadataURI rdfs:seeAlso resource property valueURI valueString In terms of abstract DC model we now have: resource, property, valueURI, valueString (and valueStringLang), encodingScheme, relatedMetadata resource property valueURI relatedMetadata encodingScheme rdfs:label Formated… valueString (valueStringLang)
  • 26.
    Need to extendabstract model each [DCMI property] ‘value’ has a ‘valueURI’ each ‘value’ has a ‘valueString’ each ‘valueString’ may have an ‘encoding scheme’ each ‘encoding scheme’ has a URI each ‘valueString’ may have a ‘language’ each ‘value’ may have a linked or embedded ‘complexValue’ (markup or related resource description)
  • 27.
    relatedMetadata related resourcedescription known as ‘relatedMetadata’ particular encoding syntaxes may support instantiation of relatedMetadata by embedding explicit link using ‘relatedMetadataURI’ both
  • 28.
    Qualified DC modela qualified DC record is made up of one or more properties and their associated values each property is an attribute of the resource being described each property must be either: one of the elements recommended by the DCMI (i.e. the 15 DC elements and audience), one of the DCMI element refinements properties may be repeated
  • 29.
    Qualified DC model(2) each value may have a valueURI each value may have a valueString each valueString may have an associated encoding scheme each encoding scheme has a URI each valueString may have an associated language (e.g. en-GB) each value may have a linked or embedded complexValue ( markup or relatedMetadata )