Closed giorgialodi closed 4 years ago
does this issue still persist in the new version?
Hi Eugen, I will be able to check it as soon as the OWL files are updated at the eprocurement repository, following your latest fixes :) I will ask about that in today's call. Thanks a lot for the effort!
I still see the issue.
So now I have a doubt: are we sure that the OWL files produced yesterday are using your latest fixes? @jseguraf
Hi,
As I said in the email, I used the latest version of the script. Before generating the OWL files, I did a pull from GitHub to be sure that I was using the latest version.
@jseguraf I've understood this specific issue and case (the others remain a mistery wrt the doubt mentioned above!). One is written hasAvailabilityRestriction and the other one is wrongly written hasAvaliabilityRestriction. I think the error is in the UML diagram as well. Fixing it there should be fine to really close this issue
Nicely spotted Giorgia. Thank you.
I already fixed the typo in v2.0.1. I will produced a new version of the OWL files after today's meeting.
There are two properties named "hasAvailabilityRestriction": one with domain Channel and another one with domain ContactPoint. Probably it should be one property with domain Channel or ContactPoint and range OpeningHoursSpecification