Re: HTTPS for RDF URIs?

uhm, I have a question about the scheme differences.
This could be used maybe to expose the "same" resource projecting only
public values (http) and value accessible to specific user on secure
connection? (https)
I mean: apart from the fact that we could have different formats, do you
think that a use case would actually be in exposing also data with limited
public access?

Alfredo


2014-01-30 Kingsley Idehen <kidehen@openlinksw.com>:

>  On 1/30/14 1:09 PM, Melvin Carvalho wrote:
>
>
>> If not bad, is there any provision for allowing that an HTTPS URI that
>> only differs in the scheme part from HTTPS URI be identified as the same
>> resource?
>>
>
>  http and https are fundamentally different resources, but you can link
> them together with owl : sameAs, I think ...
>
>
> Yes.
>
> You simply use an <http://www.w3.org/2002/07/owl#sameAs><http://www.w3.org/2002/07/owl#sameAs>relation to indicate that a common entity is denoted [1] by the http: and
> https: scheme URIs in question.
>
> [1] http://bit.ly/1fqJ5yv -- Denotes Relation
> [2] http://bit.ly/Lf4TSg -- Referent
> [3] http://bit.ly/1bD2eZs -- Identifier.
>
> --
>
> Regards,
>
> Kingsley Idehen 
> Founder & CEO
> OpenLink Software
> Company Web: http://www.openlinksw.com
> Personal Weblog: http://www.openlinksw.com/blog/~kidehen
> Twitter Profile: https://twitter.com/kidehen
> Google+ Profile: https://plus.google.com/+KingsleyIdehen/about
> LinkedIn Profile: http://www.linkedin.com/in/kidehen
>
>
>
>