Comments (8)
The problem is with http://www.ontologyrepository.com/CommonCoreOntologies/Mid/ExtendedRelationOntology
The version in the repo is OK
However, when the URL is fetched over the web it is returned as an HTML document:
<html><div class="container"><pre><meta http-equiv="content-type" content="text/html; charset=UTF-8">@prefix : <http://www.ontologyrepository.com/CommonCoreOntologies/Mid/ExtendedRelationOntology/> .
@prefix cco: <http://www.ontologyrepository.com/CommonCoreOntologies/> .
@prefix obo: <http://purl.obolibrary.org/obo/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix xml: <http://www.w3.org/XML/1998/namespace> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@base <http://www.ontologyrepository.com/CommonCoreOntologies/Mid/ExtendedRelationOntology> .
...
from commoncoreontologies.
The URL does not content negotiate for either Turtle or RDF/XML
bash-3.2$ curl -s -H "Accept: text/turtle" -L http://www.ontologyrepository.com/CommonCoreOntologies/Mid/ExtendedRelationOntology | head -1
<html><div class="container"><pre><meta http-equiv="content-type" content="text/html; charset=UTF-8">@prefix : <http://www.ontologyrepository.com/CommonCoreOntologies/Mid/ExtendedRelationOntology/> .
bash-3.2$ curl -s -H "Accept: application/rdf+xml" -L http://www.ontologyrepository.com/CommonCoreOntologies/Mid/ExtendedRelationOntology | head -1
<html><div class="container"><pre><meta http-equiv="content-type" content="text/html; charset=UTF-8">@prefix : <http://www.ontologyrepository.com/CommonCoreOntologies/Mid/ExtendedRelationOntology/> .
from commoncoreontologies.
Thanks for pointing this out! We just set up our servers to resolve IRIs and still need to work out the formatting for ontologies vs individual terms.
from commoncoreontologies.
@cmungall @timrdf What is the standard return that a tool like Robot or Protege needs to consume an ontology file? Do they always specify a format in an Accept header? The OBO principle states:
However, the official owl PURL for the ontology must resolve to a syntactically valid OWL file in an RDF in RDF-XML syntax.
Does that mean for integration with OBO ontologies and their dev pipelines, our URLs should return RDF/XML as a defualt?
from commoncoreontologies.
from commoncoreontologies.
If a client makes a request with a reasonable Accept header, then it's proper to oblige. If an Accept header is not provided by a naive client, the server can choose to default to the oldest legacy serialization (application/rdf+xml) to maximize compatibility.
This distinction is more important when requests of the resource are made by either humans (text/html) or machines (text/turtle).
from commoncoreontologies.
from commoncoreontologies.
Both full ontology and individual term IRIs are returning requests. They can be loaded via IRI into tools like Protege or Robot.
from commoncoreontologies.
Related Issues (20)
- Add Hunting, Fishing, Trapping
- Always include a BFO import HOT 1
- Data sets, Data collections, Data aggregates - what is the proper BFO branch? HOT 1
- Capacity and Payload Capacity be made Qualities, not Functions. HOT 40
- Clarification re: Optical Lens HOT 20
- Delete suggestion that describes is functional
- Example of implied polyhierarchy not captured
- Definition of "government organization" too restrictive HOT 8
- Problems with definition of "educational organization" HOT 7
- Problems with the definition of "disability" HOT 8
- Plugs, sockets, connectors and compatibility HOT 1
- Definition of and comments for 'is a measurement of HOT 14
- Force Generating Function HOT 2
- Telescope and Microscope subclass of Camera? HOT 7
- OWL file for Modal Relation Ontology HOT 5
- Add 'inhibits' and 'is inhibited by' (from Cyber Ontology)
- Define payload in terms of role and other payload issues HOT 5
- Definitions of Communication Reception Artifact Function's subclasses are too broad HOT 2
- Subclass relation between Poison Artifact Function and Damaging Artifact Function might be mistaken HOT 3
- Definitions of Signal Detection Artifact Function and Signal Processing Artifact Function too broad HOT 6
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 commoncoreontologies.