Comments (4)
SWRLRule in Manchester Syntax use ?x for variables now
from owlapi.
I think they are IRIs in the original SWRL "spec".
from owlapi.
I've added the workaround that Protege uses in the parser so that ?x is equivalent to ?urn:swrl#x.
For Protege, as far as I understand it, a rule in Manchester syntax should always have variables of the form ?foo, and in the object model they always look like urn:swrl#foo.
I've changed the manchester syntax renderer to output ?foo rather than ?<whatevernamespace#foo>, but I'm now wondering if this should always be the case or if there should be a parameter, e.g., in the format, to control this behaviour.
from owlapi.
Changed this to a more conservative approach. If there is a namespace different from urn:swrl#, use the old full IRI rendering, otherwise use the simplified form. The reverse for parsing.
This allows for simple syntax for those rules where the namespace is irrelevant, and keeps the namespace in other cases (if there is any other case, or not). Ontologies with rules roundtrip correctly with either format.
It's a pity that the SWRLVariable name implies SWRL is involved, since the interface does not have anything tying it specifically to SWRL. Might introduce a Variable interface in version 4
from owlapi.
Related Issues (20)
- EntitySearcher.getAnnotations(class) for all ontologies in import closure HOT 1
- superAnnotationProperties? HOT 2
- How to force OWL-API to use shortened IRIs in RDF/XML? HOT 1
- `uk.ac.manchester.cs.owl.owlapi.Internals` should become again interface-based like it used to be in Version 3 HOT 2
- Shared class expression in axiom with annotations causes extra triples in output HOT 1
- [question] what are possible use-cases of `ConcurrentOWLOntologyImpl` ? HOT 3
- ManchesterParser passes quotes to ShortFormProvider HOT 3
- [OBO parser] Axiom annotations using arbitrary properties are not always properly translated HOT 3
- [question] How to import SKOS Core Vocabulary without getting 429 response code HOT 3
- `OWLOntologyDocumentTarget`: documentation
- Triple parsing errors triggered by annotations on XSD datatypes HOT 2
- Vulnerabilities in Guava HOT 1
- Extending OWLOntologyLoaderListener
- Silencing import errors does not seem to work for OBO files HOT 6
- Disable resolving of imports entirely (offline mode)
- Remove org.openrdf.rio.RDFParserFactory
- Uncaught NumberFormatException when comparing (large) integers HOT 1
- "OWL 2 Web Ontology Language Data Range Extension: Linear Equations" supported? HOT 1
- Zx
- [question] Why are classes with square brackets in IRI fragments allowable in OWL/XML syntax
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from owlapi.