[
https://issues.apache.org/jira/browse/JENA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561573#comment-13561573
]
Andy Seaborne commented on JENA-386:
------------------------------------
Sorry - this can't be fixed. The project no longer has access to
jena.hpl.hp.com.
Our choices are
leave as-is: not deferencable but existing assembler files work
change the URI and break all uses of the assembler vocabulary.
Neither is ideal.
Even PURL services only reduce the problem, not fix it. If the PURL service is
lost, you loose a lot of URIs.
> Jena Assembler Vocab not reachable via http
> --------------------------------------------
>
> Key: JENA-386
> URL: https://issues.apache.org/jira/browse/JENA-386
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Sebastian Hellmann
>
> Documentation (http://jena.apache.org/documentation/assembler/index.html)
> links to http://jena.apache.org/documentation/assembler/assembler.ttl
> In the header of this file it says:
> @prefix ja: <http://jena.hpl.hp.com/2005/11/Assembler#> .
> @prefix lm: <http://jena.hpl.hp.com/2004/08/location-mapping#> .
> I am getting:
> curl -I http://jena.hpl.hp.com/2005/11/Assembler
> curl: (7) couldn't connect to host
> Will these be available again in the future or do we just have to live with
> it, that the schema namespace did not survive the move to apache?
> Sorry, if this is a know issue, I tried to search for it in Jira, but
> couldn't find it.
> Thanks,
> Sebastian
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
