This document outlines the conventions used in mapping EML XML into JSON-LD.
<url>http://example.com/1</url> <url>http://example.com/2</url> <url>http://example.com/3</url>
becomes:
"url": ["http://example.com/1", "http://example.com/2", "http://example.com/3"]
#
, unless the attribute name is id
, in which case it uses the special JSON-LD prefix, @
. For instance: <dataset id="abc123", system="knb"><title>The Title<title></dataset>
becomes
"dataset": { "@id": "abc123", "#system": "knb", "title": "The Title" }
<url function="download">http://example.com</url>
becomes:
"url": { "#function"="download" "url": "http://example.com" }
Contents of para
and section
(the two choices for components of any TextType
content) are encoded as literal character strings and not parsed.
references are expanded:
Semantic annotations (EML 2.2) are expanded into native JSON-LD
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.