 |
 |
<[log in to unmask]> <[log in to unmask]> In-Reply-To: <[log in to unmask]> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [132.174.124.35] x-microsoft-antispam: BCL:0;PCL:0;RULEID: x-forefront-prvs: 0268246AE7 x-forefront-antispam-report: SFV:NSPM;SFS:(6009001)(24454002)(51704005)(13464003)(377454003)(199002)(189002)(479174003)(80022001)(4396001)(86362001)(81542001)(76176999)(46102001)(87936001)(54356999)(20776003)(66066001)(85852003)(105586002)(31966008)(81342001)(76576001)(95666004)(101416001)(83072002)(21056001)(107886001)(19580395003)(74316001)(76482001)(99286002)(50986999)(85306003)(106356001)(92566001)(74662001)(15395725005)(15975445006)(2656002)(64706001)(77096002)(79102001)(99396002)(19580405001)(74502001)(77982001)(83322001)(33646001)(15202345003)(107046002)(108616002)(24736002);DIR:OUT;SFP:;SCL:1;SRVR:BY2PR06MB201;H:BY2PR06MB204.namprd06.prod.outlook.com;FPR:;MLV:sfv;PTR:InfoNoRecords;MX:1;LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: oclc.org X-Proofpoint-Virus-Version: vendor=nai engine=5600 definitions=7495 signatures=670478 X-Proofpoint-Spam-Reason: safe Presumably, Kevin can publish this exact statement on the Web in his own do= main. The URI where he does so can, if necessary, be used to indicate where= the statement was obtained. If the statement is embedded as RDFa in the UI= , humans and machines can both win. As Simeon suggests, some of these use cases don't need heavyweight provenan= ce solutions. Jeff > -----Original Message----- > From: Bibliographic Framework Transition Initiative Forum > [mailto:[log in to unmask]] On Behalf Of Simeon Warner > Sent: Thursday, July 10, 2014 3:33 PM > To: [log in to unmask] > Subject: Re: [BIBFRAME] Bibframe and Linked Data (Authorities) >=20 > IMO, the statement: >=20 > http://viaf.org/viaf/64055977/ skos:note "He smelled very bad" >=20 > contains no provenance information about the _statement_. It is > dangerous to infer any from the subject URI (although one might infer > something about the provenance of the subject URI itself). If people > interpret that wrongly as Kevin mentions, that seems like an education > issue. >=20 > Now, perhaps if I downloaded that statement as LOD from > http://viaf.org/viaf/64055977/ then I might reasonably infer something > about provenance (perhaps that OCLC asserted, approved or collected the > statement; to be specific one would need out-of-band knowledge of OCLC > and that dataset). >=20 > If one really cares about the expressing the provenance then it should > be made explicit and systems will need to keep track of it. This could > involve recording where things came from in "identified datasets" as > Jeff Young suggests (separate branch of the thread) or more heavyweight > methods such as named graphs, nquads etc... >=20 > Being able to served LOD from a subject URI does seem like a valid > motivation to mint new URIs that are owl:sameAs existing ones. However, > I don't think that should be conflated with provenance interpretation. >=20 > Cheers, > Simeon >=20 > On 7/10/14 2:30 PM, Ford, Kevin wrote: > > Dear Karen, > > > > The complexity arises if someone other than OCLC (?) asserts > something > > about a VIAF URI. > > > > So, for example (and, please note, I've used a different URI, > because, > > well, the one your provided is problematic for my purpose here), what > > if /I/ asserted: > > > > http://viaf.org/viaf/64055977/ skos:note "He smelled very badly, all > > the time." > > > > On the surface it looks like VIAF/OCLC said Raphael smelled badly, > all > > the time because, provenance-wise, the domain tracks back to OCLC. > In > > reality, I said it, but you cannot tell. > > > > If we use global URIs, and additional statements are made against > > those, then something like this could happen. > > > > Yours, > > > > Kevin > > > > *From:*Bibliographic Framework Transition Initiative Forum > > [mailto:[log in to unmask]] *On Behalf Of > > *Smith-Yoshimura,Karen > > *Sent:* Thursday, July 10, 2014 1:40 PM > > *To:* [log in to unmask] > > *Subject:* Re: [BIBFRAME] Bibframe and Linked Data (Authorities) > > > > Kevin - > > > > Re: > > > > >There's been lots of talk about provenance and the like in a global > > graph of data, but I feel most of those discussions rely on fairly > > technical mechanisms, the complexity of >which outweigh the > simplicity > > of minting one's own URI. (Also, the provenance statements will need > > their own URIs!) > > > > Doesn't http://viaf.org/viaf/54202464 show the provenance is VIAF? > > What's complex about this? > > > > Karen S-Y > >