New pitfall suggestion

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

Have you already thought about the title of your pitfall? How it is called?

Example: Cycles in a hierarchy

How would you describe the pitfall? *

You can either provide a natural language description, an RDF example, an SPARQL query that would detect it or send us a graphic describing it to oops@delicias.dia.fi.upm.es

How would you solve the pitfall in case you find it? Could be there more than more one solution?

Again you can explain it in natural language, an RDF piece of code, send a diagram, etc.

Any clue about how to detect the pitfall automatically?

Again you can explain it in natural language, an SPARQL query, a sequence diagram, etc.

To what extent is it importat to correct such a pitfall?

You can select two options if you are not sure.

Very important, it is crucial for ontology consistency, reasoning, applicability, etc.

It is not vital, you could do with it but it will be much better if you correct it.

It is not really important, but it will make the ontology nicer.

Anything else to declare?

For example, whether you mind to be contacted in case we need further details (in this case you should provide at least an email address), when and how did you find the pitfall, why do you care about it, etc.

Submit

Clear form

Never submit passwords through Google Forms.

Forms

This content is neither created nor endorsed by Google.