[
https://issues.apache.org/jira/browse/JENA-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-585:
-------------------------------
Description:
Currently, it will choose RDF/XML too readily.
The decision should be: content-type (if not text/plain), URl file extension,
RDF/XML.
The presenting problem is a file like http://host/data.ttl just dumped on a
server - it probably get served as text/plain. RDFDataMgr.read(url) will work.
This JIRA is extending that to model.read(url) where there is always a default
syntax. Normally, if the syntax is given, it is to override the implicit one
but in this case we want it to be a "soft default", only used if there is no
other sensible choice.
was:
Currently, it will choose RDF/XML too readily.
The decision should be: content-type (if not text/plain), URl file extension,
RDF/XML.
> model.read(url) to be more general in syntax choice.
> ----------------------------------------------------
>
> Key: JENA-585
> URL: https://issues.apache.org/jira/browse/JENA-585
> Project: Apache Jena
> Issue Type: Improvement
> Affects Versions: Jena 2.10.1
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
> Priority: Minor
>
> Currently, it will choose RDF/XML too readily.
> The decision should be: content-type (if not text/plain), URl file extension,
> RDF/XML.
> The presenting problem is a file like http://host/data.ttl just dumped on a
> server - it probably get served as text/plain. RDFDataMgr.read(url) will
> work. This JIRA is extending that to model.read(url) where there is always a
> default syntax. Normally, if the syntax is given, it is to override the
> implicit one but in this case we want it to be a "soft default", only used if
> there is no other sensible choice.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
