From d18e021f79d4accb8e7da1c960bfd690af27bd60 Mon Sep 17 00:00:00 2001 From: csnyulas Date: Tue, 10 Sep 2024 10:19:49 +0300 Subject: [PATCH] Made a few corrections in the README.md regarding Known issues --- README.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index dea2afec..f9e90263 100644 --- a/README.md +++ b/README.md @@ -89,7 +89,7 @@ locations in the source XML. `epo:AgentInRole`'s "contact point in role" due to technical difficulty -- `Expected epo:hasTimePeriod --> [1..*] at-voc:timeperiod , but found 0 instances` predicate is an alternative and should not be mandatory +- `Expected epo:hasTimePeriod --> [1..*] at-voc:timeperiod , but found 0 instances` predicate is an alternative and should not be mandatory - `model declares a xsd:dateTime` data type misalignment between eForms and ePO @@ -97,15 +97,13 @@ locations in the source XML. - External resources such as a referenced notices will raise violations if tested standalone (as they will only contain information in the current notice's scope) -- `cpov:ContactPoint adms:identifier / skos:notation ?value` ePO 4.0.0 does not foresee an Identifier for ContactPoint (OPT-201-Organization-TouchPoint) - - all `epo-not:CompetitionNotice` and associations of it will not exist for `epo:ResultNotice` - all alternative values will not exist for all notices (e.g. `used` vs. `n-used`) -- `epo hasAwardDecisionDate` data type misalignment between eForms and ePO +- `epo:hasAwardDecisionDate` data type misalignment between eForms and ePO -- `epo hasOJSIssueNumber` data type misalignment between eForms and ePO +- `epo:hasOJSIssueNumber` data type misalignment between eForms and ePO - `Expected epo:hasAwardCriteriaStatedInProcurementDocuments`