From 236c531e4d06a2280190a22885f8bc306e36582d Mon Sep 17 00:00:00 2001
From: Audrey Hamelers <1749394+ahamelers@users.noreply.github.com>
Date: Sat, 6 May 2023 21:16:42 +0200
Subject: [PATCH] New rules for permissions rec version 2 (#22)
---
schematrons/1.0/permissions-errors.sch | 19 ++++++++++++++++--
schematrons/1.0/permissions-warnings.sch | 25 ++++++++++++++++++++++--
2 files changed, 40 insertions(+), 4 deletions(-)
diff --git a/schematrons/1.0/permissions-errors.sch b/schematrons/1.0/permissions-errors.sch
index ed08fdc..08970f2 100755
--- a/schematrons/1.0/permissions-errors.sch
+++ b/schematrons/1.0/permissions-errors.sch
@@ -58,11 +58,26 @@
-
+
If both @xlink:href and <ali:license_ref> are used to specify the licence
URI of an article, their contents must match exactly.
+
+ If multiple <ali:license_ref> elements are tagged they must have @start_date to indicate when each license is applicable.
+
+
+
+
+
+ @end_date must be later than @start_date on <ali:free_to_read>.
+
+
+
+
+
+ @ must contain valid dates in ISO-8601 YYYY-MM-DD format.
+
diff --git a/schematrons/1.0/permissions-warnings.sch b/schematrons/1.0/permissions-warnings.sch
index ad3502e..d7a1505 100755
--- a/schematrons/1.0/permissions-warnings.sch
+++ b/schematrons/1.0/permissions-warnings.sch
@@ -26,6 +26,15 @@
xmlns:j4r="http://jats4r.org/ns">
+
+
+
+
+
+
+
+ Creative Commons licenses should follow the recommended patterns. is not a best practices pattern for a Creative Commons URL. Check that it uses https and a trailing slash.
+
@@ -66,7 +75,19 @@
-
-
+
+
+
+ URI in license-p () does not match canonical license URI ().
+
+
+
+
+ The contents of <copyright-statement> should not conflict with <copyright-year>.
+
+
+ The contents of <copyright-statement> should not conflict with <copyright-holder>.
+
+