[ 
https://issues.apache.org/jira/browse/TAVERNA-1037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stian Soiland-Reyes updated TAVERNA-1037:
-----------------------------------------
    Labels: RFC gsoc2018 java uri  (was: )

> GSOC: Use arcp:// URIs in RO Bundle
> -----------------------------------
>
>                 Key: TAVERNA-1037
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-1037
>             Project: Apache Taverna
>          Issue Type: New Feature
>          Components: Taverna Language
>         Environment: Java, HTTP
>            Reporter: Stian Soiland-Reyes
>            Priority: Major
>              Labels: RFC, gsoc2018, java, uri
>
> This is a proposed GSOC project.
> The 
> [ro-bundle|https://github.com/apache/incubator-taverna-language/tree/master/taverna-robundle]
>  module of Taverna Language currently uses app:// URIs in its Java 
> [FileSystem|https://docs.oracle.com/javase/8/docs/api/java/nio/file/FileSystem.html]
>  URIs and thus also in its RDF loading.
> This was in accordance with [RO bundle 
> spec|https://researchobject.github.io/specifications/bundle/#absolute-uris] 
> -- however the app:// URI scheme has been since abandoned.
> The arcp URI scheme has been proposed as an alternative: 
> https://tools.ietf.org/id/draft-soilandreyes-arcp-03.html
> This proposal suggests to modify RO Bundle to use arcp:// URIs -- but not 
> just modify app://bf5a0cab-86d7-40da-b588-1ce4953ae13d/ to 
> arcp://uuid,bf5a0cab-86d7-40da-b588-1ce4953ae13d/  - but to support the other 
> mechanisms suggested by arcp in 
> https://tools.ietf.org/id/draft-soilandreyes-arcp-03.html#rfc.section.4.1
> That is, it should be possible to open an RO Bundle from a fixed URL as 
> identifier, or using its sha256 checksum in readonly mode. 
> It should also be possible to lookup an RO Bundle URI from a .well-known 
> endpoint as defined in 
> https://tools.ietf.org/id/draft-soilandreyes-arcp-03.html#rfc.section.4.4



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to