please build

Author: Rob Sanderson

source/_includes/links.md

@@ -189,7 +189,7 @@
 [org-open-annotation-multi]: http://www.openannotation.org/spec/core/multiplicity.html#Choice "Open Annotation: Multiplicity"
 [org-open-annotation-types]: http://www.openannotation.org/spec/core/core.html#BodyTargetType "Open Annotation: Body Target"
 [org-open-annotation]: http://www.openannotation.org/spec/core/ "Open Annotation"
-[org-openarchives-rsync]: http://openarchives.org/rs/toc
+[org-openarchives-rsync]: https://openarchives.org/rs/toc
 [org-rfc-2119]: https://tools.ietf.org/html/rfc2119 "RFC Keywords"
 [org-rfc-2617]: https://tools.ietf.org/html/rfc2617 "HTTP Authentication: Basic and Digest Access Authentication"
 [org-rfc-2818]: https://tools.ietf.org/html/rfc2818 "HTTP Over TLS"

source/image/1.1/index.html

@@ -944,7 +944,7 @@ <h2>
     This API does not specify whether the image server will support authentication or what mechanism it might use. In the
     case of  "401 Unauthorized" HTTP error response, the content of the WWW-Authenticate header will depend on the
     authentication mechanism supported by the server. If the server supports HTTP Basic or Digest authentication then the
-    header should follow <a href="http://www.ietf.org/rfc/rfc2617" target="_blank">RFC2617</a>, for example:
+    header should follow <a href="https://www.ietf.org/rfc/rfc2617" target="_blank">RFC2617</a>, for example:
   </p>
   <p class="code-block">
     WWW-Authenticate: Basic realm="Images"
@@ -1002,7 +1002,7 @@ <h2>
   <p>
     The URL syntax of this API relies upon slash (/) separators which MUST NOT be encoded. Clients MUST percent-encode
     special characters (the to-encode set below: percent and gen-delims of
-    <a href="http://www.ietf.org/rfc/rfc3986" target="_blank">RFC3986</a> except the colon) within the components
+    <a href="https://www.ietf.org/rfc/rfc3986" target="_blank">RFC3986</a> except the colon) within the components
     of requests. For example, any slashes within the identifier part of the URL MUST be percent-encoded. Encoding is
     necessary only for the identifier because other components will not include special characters.
   </p>

source/model/shared-canvas/1.0/index.html

@@ -58,7 +58,7 @@ <h2><a id="abstract"></a>Abstract</h2>
 parts thereof,
 via <a href="http://www.w3.org/community/openannotation/">Open
 Annotations</a> and the Annotations are grouped and ordered
-in <a href="http://www.openarchives.org/ore/">OAI-ORE
+in <a href="https://www.openarchives.org/ore/">OAI-ORE
 Aggregations</a>.
 </p>
 </div>

source/presentation/4.0/index.md

@@ -76,21 +76,20 @@ Mention cookbook
 
 ## Foundations
 
-Simple model diagram
-
-Manifests and Containers briefly
-
+<p style="float: right">
+  <img src="{{ site.api_url | absolute_url }}/assets/images/data-model.png" alt="Data Model" width="400"><br/>
+</p>
 
 
 ### Manifests
 
-A Manifest is the primary unit of distribution of IIIF. It is a JSON document that provides a description of the structure and properties of a single item to be presented to the user, such as a title and other descriptive and linking information about the object and/or the intellectual work that it conveys. The scope of what constitutes an item, and thus its Manifest, is up to the publisher of that Manifest. The Manifest contains sufficient information for the client to initialize itself and begin to display something quickly to the user.
+A Manifest is the primary unit of distribution of IIIF. Each Manifest usually describes how to present an object, such as a book, statue, music album or 3 dimensional scene. It is a JSON document that carries information needed for the client to present content to the user, such as a title and other descriptive information. The scope of what constitutes an object, and thus its Manifest, is up to the publisher of that Manifest. The Manifest contains sufficient information for the client to initialize itself and begin to display something quickly to the user.
 
-The Manifest's `items` property is a list of _Containers_ of _Content Resources_ (images, 3D models, audio, etc). Client software loads the Manifest and presents the Content Resources to the user. The `items` property provides an order to the content.
+The Manifest's `items` property is an ordered list of _Containers_ of _Content Resources_ (images, 3D models, audio, etc). Client software loads the Manifest and presents the Content Resources to the user in that order.
 
 Manifests have descriptive, technical and linking properties. The required properties of Manifests are `id`, `type`, `items` and `label`. Additional descriptive properties include `summary`, `metadata`, `rights`, `thumbnail`, `homepage` and `provider`. 
 
-[See Model Docs](manifest)
+See the [Model Documentation](model/#manifest) for more information.
 
 ```
 Manifest JSON

source/registry/profiles/index.md

@@ -68,7 +68,7 @@ This table summarizes the known profiles available, for use with the [Presentati
 | http://www.loc.gov/standards/alto  | The URI for identifying [ALTO](https://www.loc.gov/standards/alto/) which is used for encoding OCR text. |
 | http://www.loc.gov/standards/marcxml  | The URI for identifying [MarcXML](https://www.loc.gov/standards/marcxml/) metadata records.  |
 | http://purl.org/dc/terms/ | The URI for identifying records that follow the [Dublin Core Metadata Initiative Metadata Terms](https://www.dublincore.org/specifications/dublin-core/dcmi-terms/) (NB: these are different from the legacy Dublin Core Metadata Element Set, Version 1.1, refered to as http://purl.org/dc/elements/1.1/). |
-| http://www.europeana.eu/schemas/edm/  | The URI for identifying [EDM (Europeana Data Model)](https://pro.europeana.eu/page/edm-documentation) metadata records.  |
+| https://www.europeana.eu/schemas/edm/  | The URI for identifying [EDM (Europeana Data Model)](https://pro.europeana.eu/page/edm-documentation) metadata records.  |
 {: .api-table}