WebProtege seems to parse some turtle files as OBO files

[matthewhorridge]

The ontology below gets parsed as an OBO file when it's clearly a turtle file.

# baseURI: http://www.modelservers.org/public/ontologies/typical.ttl
# imports: http://www.modelservers.org/public/ontologies/cmo.ttl

@prefix :        <http://www.modelservers.org/public/ontologies/typical.ttl#> .
@prefix cmo:     <http://www.modelservers.org/public/ontologies/cmo.ttl#> .
@prefix dcterms:  <http://purl.org/dc/terms#> .
@prefix owl:     <http://www.w3.org/2002/07/owl#> .
@prefix qudt-quantity:  <http://qudt.org/vocab/quantity#> .
@prefix rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix rdfs:    <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xml:     <http://www.w3.org/XML/1998/namespace> .
@prefix xsd:     <http://www.w3.org/2001/XMLSchema#> .

<http://www.modelservers.org/public/ontologies/typical.ttl>
      rdf:type owl:Ontology ;
      owl:imports <http://www.modelservers.org/public/ontologies/cmo.ttl> .

:Car  rdf:type owl:Class .

:NAVSIS123
      rdf:type :NavigationSystem .

:NavigationSystem
      rdf:type rdfs:Class ;
      rdfs:subClassOf owl:Thing .

:TypicalProperty_1
      rdf:type cmo:TypicalProperty ;
      cmo:forClass :Car ;
      cmo:typicalProperty :amountOfDoors .

:TypicalProperty_2
      rdf:type cmo:TypicalProperty ;
      cmo:forClass :Car ;
      cmo:typicalProperty :hasNavigationSystem .

:TypicalValue_1
      rdf:type cmo:TypicalValue ;
      cmo:forClass :Car ;
      cmo:forProperty :width ;
      cmo:typicalValue "1.84"^^xsd:float .

:TypicalValue_2
      rdf:type cmo:TypicalValue ;
      cmo:forClass :Car ;
      cmo:forProperty :hasNavigationSystem ;
      cmo:typicalValue :NAVSIS123 .

:amountOfDoors
      rdf:type owl:DatatypeProperty ;
      rdfs:range xsd:integer .

:hasNavigationSystem
      rdf:type owl:ObjectProperty ;
      rdfs:range :NavigationSystem ;
      rdfs:subPropertyOf dcterms:hasPart .

:width
      rdf:type owl:DatatypeProperty ;
      rdfs:range xsd:float .

[matthewhorridge]

Verified that this is indeed the problem. The OBO parser doesn't throw any exceptions when parsing this document.