All questions and comments about or in any way related to OTTR (http://ottr.xyz) are welcome here!
The 1st OTTR user forum will take place virtually on 2021-01-28 Thu
12:00--14:00 CET. The purpose of the event is to let users of the OTTR
framework share experiences and to meet the developers behind OTTR to
discuss future directions. The event should also be of interest to
those that are curious to see practical uses of the OTTR framework.
We also welcome input and presentations of tools and technologies that
are related to OTTR.
Preliminary agenda:
- OTTR team: current status and future plans
- Q&A
- Invited talk: Johan W. Klüwer
- Shorter talks
- Discussion
Register here: https://ottr.xyz/event/2021-01-28-user-forum/
Hi! I have created OTTR templates for every constraint in the SHACL Core vocabulary, but I wonder if it is possible to nest templates in the instance declaration? So I do not have to repeat myself by passing ShapeURI and pathURI for every instance declaration of any constraint.
Example of wanted instance declaration:
o-sh:PropertyShape(ex:ShapeURI, ex:pathURI,
( o-sh:MinCount(1),
o-sh:MaxCount(1),
o-sh:Pattern("^[a-zA-Z]+$")
)
)With expected result:
ex:ShapeURI a sh:PropertyShape ;
sh:path ex:pathURI ;
sh:minCount 1 ;
sh:maxCount 1 ;
sh:pattern "^[a-zA-Z]+$" .Hi @veleda. No, this is not supported. This would require an instance to return a value and behave like a function. Instances are more like predicates (in the logical sense) and represent a statement (possibly complex statement of several triples).
A possibility is to create a template that contains all or a selection of the predicates that are relevant for sh:PropertyShape, possibly using optional parameters to allow for more variations of input:
o-sh:PropertyShape[ ?shape, ?path, ??min, ??max, ??pattern ]Perhaps a good starting point could be the diagram found here: https://www.w3.org/TR/shacl/#constraints-section ? However, it seems it is not complete as for instance sh:pattern is missing. How far from complete is this diagram?
A problem is of course that a template with too many parameters can be hard to use, and its instances hard to understand. Named parameters, which is a future feature, would be helpful here.
Thank you for the reply, @m.g.skjaeveland_gitlab! I understand. It's not a big problem, instancing templates would require some kind of repeating pattern then. Too long template signatures will, as you say, be hard to use.
The diagram you refer to is an illustration of the key classes of SHACL (PropertyShape and NodeShape, and their superclass). It is not displaying the complete SHACL vocabulary, but a subset of constraints for the sake of example. The definitions of the SHACL Core Constraint components can be found under this section https://www.w3.org/TR/shacl/#core-components . As I mentioned, I've completed OTTR templates (in the syntax of stOTTR) for all constraints described in SHACL Core. Once I've added non-validating features in SHACL and SHACL SPARQL, I'll upload my collection of templates. :)
org.apache.poi.ss.formula.FormulaParseException: Parse error near char 31 '[' in specified formula 'IF(ISNA(VLOOKUP(F15,[1]!Tabell2[#All],2,FALSE))=TRUE, "Feil", VLOOKUP(F15,[1]!Tabell2[#All],2,FALSE))'. Expected ',' or ')'which indicates that there is a problem with a formula in the spreadsheet. It could be a problem with the formula it self (e.g., syntax error), or it could be a problems with how apache poi handles the formula, for instance not all functions are supported, but that is not what is reported here. If it is a problem with poi, you could try to copy the computed value of the formula so that poi does not have to evaluate the formula to get the value.
4 replies
3 replies
I have a question that I've come across when using OTTR. I am wondering if it is possible to have an object property and give it "object property characteristics" in OTTR (for example, to make an object property functional or transitive). I have had a look through the documentation and cannot find reference to property characteristics. If this is possible, could someone please point me to the correct place to see how to do this?
Thanks so much for your help.
Hi @Caitlin2694 , I would state this by using the Type template (http://tpl.ottr.xyz/rdf/0.1/Type), e.g.,
o-rdf:Type(?ob, owl:FunctionalProperty)If you need multiple characteristics for the same property, you will need to make many instances of the Type template.
One could argue that we should have dedicated templates for this, e.g., something like:
o-owl-ax:FunctionalProperty[?ob] :: { o-rdf:Type(?ob, owl:FunctionalProperty) } .as this would give us fuller coverage of the OWL spec (https://www.w3.org/TR/owl2-mapping-to-rdf) -- which is a good argument, I think. We should aim for complete coverage of this OWL spec.
Hi all,
here are the latest news and updates from the OTTR project.
** As of yesterday, new releases of Lutra will be issued bi-monthly.
The release will be followed by an announcement email like this that
will include the latest news.
** Lutra 0.6.14 was released yesterday. The release is found on
GitLab, the jar artefacts are released on Maven central, and the
(incomplete) javadocs are available through javadoc.io. The Lutra CLI
executable is also available directly from
http://ottr.xyz/downloads/lutra/. This information is found on the
GitLab README file:
https://gitlab.com/ottr/lutra/lutra#downloads
Changelog:
https://gitlab.com/ottr/lutra/lutra/-/blob/develop/CHANGELOG.md
** We have labelled issues where where we in particular think your
help is needed and possible:
https://gitlab.com/groups/ottr/-/issues/?label_name%5B%5D=wanted%3A%20help
Please have a look and help us out.
** Our GitLab project on http://gitlab.com/ottr was recently accepted
for GitLab's open source programme:
https://about.gitlab.com/solutions/open-source/ This means we can
continue to use most of GitLab's services for free.
** Conferences and Workshops. We will, or have been, present at the
following conferences and workshops to present our work:
"A Survey of Syntactic Modelling Structures in Biomedical
Ontologies", research paper accepted for ISWC 2022 by Christian
Kindermann and Martin G. Skjæveland. https://iswc2022.semanticweb.org/"Concrete Names for Complex Expressions in Ontologies: A case study
on SNOMED CT", by Christian Kindermann and Martin G. Skjæveland, full
paper accepted for International Workshop on Knowledge Graph
Summarization, https://kgsum.github.io/"Reusable Ontology Modelling Patterns for Biodiversity Data with
Reasonable Ontology Templates (OTTR)" by Laura Ann Slaughter, Leif
Harald Karlsen, Eveliina Päivikki Kallioniemi, Martin Georg Skjæveland,
https://biss.pensoft.net/article/93939/ will be presented at TDWG 2022:
https://www.tdwg.org/conferences/2022/We presented OTTR at OntoCommons' Workshop on Ontology Engineering
and Knowledge Graphs tool ecosystem.
https://ontocommons.eu/news-events/events/workshop-ontology-engineering-and-knowledge-graphs-tool-ecosystem
Martin