<html xmlns="http://www.w3.org/1999/xhtml"><head></head><body><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="2" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[2]</anchor-end> <anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">IIIF</anchor> は <anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">HTML要素</anchor>の一部を <anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">XML構文</anchor>で記述する独自の<anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">マーク付け言語</anchor>を採用し、
<anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">JSON-LD</anchor> における値として使っています。</p><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="3" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[3]</anchor-end> <anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">HTML要素</anchor>を <anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">XML構文</anchor>として使うというと <anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">XHTML</anchor> を想起しますが、
<anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">XML名前空間</anchor>は使っていないようです。</p><p><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="4" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[4]</anchor-end> 通常の <anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">HTML</anchor> とは似て非なるものですから、互換性には難があります。
<anchor xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:">IIIF</anchor> 以外でこの構文を採用するべきではありません。</p><figure class="quote"><figcaption><anchor-end xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:anchor="1" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:">[1]</anchor-end> <cite xml:lang="en">Presentation API 2.1.1 — IIIF | International Image Interoperability Framework</cite>
(<time>2017-09-15 08:03:41 +09:00</time>)
<anchor-external xmlns="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resScheme="URI" xmlns:a0="urn:x-suika-fam-cx:markup:suikawiki:0:9:" a0:resParameter="http://iiif.io/api/presentation/2.1/#html-markup-in-property-values">http://iiif.io/api/presentation/2.1/#html-markup-in-property-values</anchor-external></figcaption><blockquote><p>Minimal HTML markup may be included in the description, attribution and metadata properties. It must not be used in label or other properties. This is included to allow manifest creators to add links and simple formatting instructions to blocks of text. The content must be well-formed XML and therefore must be wrapped in an element such as p or span. There must not be whitespace on either side of the HTML string, and thus the first character in the string must be a ‘&lt;’ character and the last character must be ‘&gt;’, allowing a consuming application to test whether the value is HTML or plain text using these. To avoid a non-HTML string matching this, it is recommended that an additional whitespace character be added to the end of the value.</p><p>In order to avoid HTML or script injection attacks, clients must remove:</p><p>Tags such as script, style, object, form, input and similar.</p><p>All attributes other than href on the a tag, src and alt on the img tag.</p><p>CData sections.</p><p>XML Comments.</p><p>Processing instructions.</p><p>Clients should allow only a, b, br, i, img, p, and span tags. Clients may choose to remove any and all tags, therefore it should not be assumed that the formatting will always be rendered.</p><p>{&quot;description&quot;: {&quot;@value&quot;: &quot;&lt;p&gt;Some &lt;b&gt;description&lt;/b&gt;&lt;/p&gt;&quot;, &quot;@language&quot;: &quot;en-latn&quot;}}</p></blockquote></figure></body></html>