[
https://issues.apache.org/jira/browse/JENA-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13561754#comment-13561754
]
Sebastian Hellmann commented on JENA-386:
-----------------------------------------
Option 3:
change all URLs and update the implementation to understand both versions. Also
not ideal, as all old applications will not understand the new vocabulary.
Anybody using the new URIs would need to be aware that it is not backward
compatible.
Now that you say that thing about purl.org reminds me of the death by
meteorite, which is said to be overall more probable than an airplane crash due
to the very low % of occurance * very high number of casulties)
Are there any requests to extend/improve the assembler vocabulary? If there
aren't any plans in this direction, then I would suggest to put a note here:
http://jena.apache.org/documentation/assembler/index.html and here:
http://jena.apache.org/documentation/assembler/assembler.ttl to let people know
about the problem and just leave it be, as unpleasant as it is.
-- Sebastian
> 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
> Priority: Minor
>
> 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
