Fix internal links

Makefile

@@ -91,6 +91,10 @@ release/ro-crate-${TAG}.md: dependencies release/ docs/${RELEASE}/_metadata.liqu
 	   `grep ^sort: docs/${RELEASE}/*.md | sort -n -k 2 | grep -v README.md| grep -v about.md | sed s/:.*//` \
 	   docs/${RELEASE}/appendix/*.md docs/_includes/references.liquid docs/${RELEASE}/.references.md |\
 	   grep -v '{%' > release/ro-crate-${TAG}.md
+	# Fix internal links to work in single-page
+	cp release/ro-crate-${TAG}.md release/ro-crate-${TAG}.md.orig
+	sed -i -E 's,]\(([^:)]*/)*([^:)]*)\.md\),](#\2),g' release/ro-crate-${TAG}.md
+	sed -i -E 's,]\([^):]*\.md#([^)]*)\),](#\1),g' release/ro-crate-${TAG}.md
 
 release/ro-crate-${TAG}.html: dependencies release/ release/ro-crate-${TAG}.md
 	egrep -v '^{:(\.no_)?toc}' release/ro-crate-${TAG}.md | \

docs/1.1-DRAFT/appendix/jsonld.md

@@ -22,6 +22,8 @@ excerpt: |
    limitations under the License.
 -->
 
+<div id="jsonld"></div>
+
 # APPENDIX: RO-Crate JSON-LD
 
 It is not necessary to use [JSON-LD tooling] to generate or parse the _RO-Crate Metadata File_, although JSON-LD tools may make it easier to conform to this specification, e.g. handling relative URIs. It is RECOMMENDED to use JSON tooling to handle [JSON][RFC 7159] syntax and escaping rules.

docs/1.1-DRAFT/appendix/relative-uris.md

@@ -22,6 +22,8 @@ excerpt: |
    limitations under the License.
 -->
 
+<div id="relative-uris"></div>
+
 # APPENDIX: Handling relative URI references
 
 The _RO-Crate Metadata File_ use _relative URI references_ to identify files and directories

docs/1.1-DRAFT/contextual-entities.md

@@ -28,6 +28,7 @@ jekyll-mentions: false
    limitations under the License.
 -->
 
+<div id="contextual-entities"></div>
 
 # Representing Contextual Entities
 

docs/1.1-DRAFT/metadata.md

@@ -27,6 +27,8 @@ sort: 5
    limitations under the License.
 -->
 
+<div id="metadata"></div>
+
 # RO-Crate Metadata
 
 RO-Crate aims to capture and describe the [Research Object][ResearchObject] using structured _metadata_.

docs/1.1-DRAFT/provenance.md

@@ -23,6 +23,7 @@ sort: 9
    limitations under the License.
 -->
 
+<div id="provenance"></div>
 
 # Detailing provenance of entities
 

docs/1.1-DRAFT/root-data-entity.md

@@ -23,7 +23,7 @@ sort: 6
    limitations under the License.
 -->
 
-# Core Metadata for the Root Data Entity
+# Root Data Entity
 
 The **Root Data Entity** is a [Dataset] that represent the RO-Crate as a whole;
 a _Research Object_ that includes the _Data Entities_ and the related

docs/1.1-DRAFT/structure.md

@@ -23,6 +23,8 @@ sort: 4
    limitations under the License.
 -->
 
+<div id="structure"></div>
+
 # RO-Crate Structure
 
 The structure an _RO-Crate_ MUST follow is:

docs/1.1-DRAFT/workflows.md

@@ -25,6 +25,8 @@ sort: 10
    limitations under the License.
 -->
 
+<div id="workflows"></div>
+
 # Workflows and Scripts
 
 Scientific workflows and scripts that were used (or can be used) to analyze or generate files contained in an RO-Crate MAY be embedded in an RO-Crate. _Workflows_ and _scripts_ SHOULD be described using [data entities](data-entities.md) of type [SoftwareSourceCode].