 |
 |
"HTTP URIs, and only HTTP URIs, are used to identify resources that are subjects or objects of RDF statements." So if a publisher uses an HTTPS-only website, we can't talk about their books? If we want longevity in our standard, we should rely on RDF to define (and as necessary redefine) the lower levels of the technology stack. cheers stuart -- I have a new phone number: 04 463 5692 https://www.facebook.com/VUWLibrary / https://www.facebook.com/TKMPC ________________________________________ From: Bibliographic Framework Transition Initiative Forum <[log in to unmask]> on behalf of Simon Spero <[log in to unmask]> Sent: Friday, 10 June 2016 11:33:45 a.m. To: [log in to unmask] Subject: Re: [BIBFRAME] bf:Urn Ah. Maybe this should be added to the document describing bibframe RDF conventions ( http://www.loc.gov/bibframe/docs/bibframe2-rdf-conventions.html )? Simon On Jun 9, 2016 7:24 PM, "Ray Denenberg" <[log in to unmask]<mailto:[log in to unmask]>> wrote: > > I meant “...in BIBFRAME only http URIs ….” > >> On Jun 9, 2016, at 7:16 PM, Simon Spero <[log in to unmask]<mailto:[log in to unmask]>> wrote: >> >> On Jun 9, 2016 6:43 PM, "Ray Denenberg" <[log in to unmask]<mailto:[log in to unmask]>> wrote: >> > A Urn is in fact a URI, but that’s irrelevant. It is not an HTTP URI. HTTP URIs, and only HTTP URIs, are used to identify resources that are subjects or objects of RDF statements. >> >> That's not strictly correct. >> Resource names in subjects or objects can be any absolute IRI. See §3.2 of the RDF concepts and Abstract Syntax recommendation for details. >> >> The IRI <ftp://chickens.org/🐤> is perfectly valid in subject, predicate, or object positions. >> >> Simon > >