LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  November 2015

BIBFRAME November 2015

Subject:

Re: Properties of Item proposal

From:

Karen Coyle <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Thu, 19 Nov 2015 07:18:02 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (69 lines)

Ray, we had a lively back-and-forth conversation going on that has 
suddenly stopped, and I'm wondering what your thinking is at this point. 
I'm sure that Tom didn't intend to shut the conversation down, and much 
of what he says echoes what we were discussing prior to his reply.

Where do we go from here? Is there a resolution? Agreement? Further 
discussion?

Thanks,
kc

On 11/17/15 12:17 PM, Tom Johnson wrote:
> On Tue, 17 Nov 2015 09:40:38 -0500, Denenberg, Ray <[log in to unmask]> wrote:
>
>> Clearly there is confusion over "resource" - web resource, information
> resource, RDF resource. I'm not sure it's useful to sort through it all, as
> some of these definition have historical significance only.  So let's try to
> break this down without talking about resources.
>
>> An RDF property may be a datatype property or an object property. A
> datatype property takes a literal for its object (Quotes).  An object
> property takes an "individual" for its object (braces).   "Individual" as
> in, a member of an RDF class.  An individual always has an RDF description
> (or in your terminology, you can always make an RDF statement about it).
>
> It's unclear to me where any of this comes from. It isn't an accurate
> description of RDF or RDFS, which have only one type of property
> (rdf:Property). OWL does have DatatypeProperty and ObjectProperty classes,
> but they are subclasses of rdf:Property; other types of properties are
> allowed.
>
> Additionally, it is allowed, desirable, and common to link to resources on
> the web in Linked Data, even when they do not have RDF representations.
> Every item in DPLA, for instance has triples of the form:
>
>    :aggregation a ore:Aggregation ;
>       edm:isShownAt <http://example.com/some/item/page.html> .
>
>    <http://example.com/some/item/page.html> a edm:WebResource .
>
> Using a literal in place of that resource would be obfuscating and would
> prevent us and others from making additional assertions about it. Web pages,
> jpegs, ebooks, etc... *are* (or at least, can be) OWL individuals.
>
> What you refer to as an "RDF resource" is only one of the kinds of things we
> want to talk about, and while it's good practice to have RDF descriptions,
> there are cases where this isn't feasible or necessary (e.g. because someone
> else controls the server that hosts the web page you want to describe).
>
> I would also suggest using different terminology; as Karen has pointed out,
> "RDF resource" has a formal meaning within the specifications. A related
> concept that may interest you is "RDF source"[0], loosely: resources that
> provide an RDF Graph. This concept is used heavily in the recent Linked Data
> Platform spec[1].
>
> [0] http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-source
> [1] http://www.w3.org/TR/ldp/#dfn-linked-data-platform-rdf-source
>
>
> Tom Johnson
> Metadata & Platform Architect
> Digital Public Library of America

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager
https://listserv.loc.gov/cgi-bin/wa?A2=BIBFRAME;f256206e.1511
listserv.loc.gov
crawl=CC-MAIN-2019-51
51859
application/http; msgtype=response
sha1:OLR354QAFYXZ62273JQHTC7DQJYVGV6W
<urn:uuid:da5f18a3-4721-4974-bc5f-6eece50d0bfd>
2019-12-16T00:41:27Z
140.147.55.47
text/html
sha1:UC46RMQEFA6QDZXU4VQWDCI5FC6GNEQX
<urn:uuid:99b98a28-4ad5-44df-81d0-48bf19c7d315>
https://listserv.loc.gov/cgi-bin/wa?A2=BIBFRAME;f256206e.1511
response
<urn:uuid:37157674-c5eb-4463-8a5f-67b083b0deff>
isPartOf: CC-MAIN-2019-51
publisher: Common Crawl
description: Wide crawl of the web for December 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-157.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/