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:

Thomas Berger <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 17 Nov 2015 18:43:29 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (69 lines)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 17.11.2015 um 15:40 schrieb Denenberg, Ray:
> Thomas - I take your point about compete vs. incomplete description
> with respect to "RDF representation", but I'm not using it in that
> context, but rather in the context of: if you dereference a web
> resource, you get a representation of that resource; there may be many
> representations, one of which may be RDF. NOT to imply that that
> representation is complete.

If I dereference <http://slideplayer.com/slide/3350892/> I get some
visual content and the description for that may or may not be somewhere
on the web.

I mean, this is how the web started: Providing means to access
resources, not their descriptions.


> 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" a
s
> 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).

/Predicates/ of RDF statements are called /properties/. They are denoted
by IRIs.

/Literals/ (only admitted in object position of statements) are always
associated with a datatype. These are denoted by IRIs and for some
more central datatypes the IRIs to use are prescribed.

According to the RDF Scheme specification Resources may be divided
into classes. If we do so, we may state that using the rdf:type
property.

By means of the rdfs vocabulary we can craft statements that the object
of a given statement is of class rdfs:Literal and of a certain
rdfs:Datatype (and has rdf:value it's value).

But this ist purely meta-meta: I can use URIs in object position
of statements and there is no guarantee that anywhere on earth
this URI is used in the subject position of statements. Of course
this is an undesirable situation, since by using it in object
position I declare that URI to represent something but apparently
I'm not going to reveal any "definition" or further identification
of that entity I have coined. But thats perfectly legal.

Of course no one can be hindered setting up a vocabulary containing
inverse properties of mine and then express the same statement
in reverse order...


viele Gruesse
Thomas Berger

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iJwEAQECAAYFAlZLZ0AACgkQYhMlmJ6W47NFJQP8CtpHLCxgBhx95S2S1J0PfOqR
jIYAS/wSfKvZOybs1n2T0iqO6kP4ceGxXZ6fwHJUZ+T39JdaCV92ArGQWTkZ/kIq
2Vf4fNJiwQvClDGf8Prye5YrBM0QijIOBqhcEP6n5nf4K0r/HUMQ1oYZeQsN7+Bk
pnCkTRCSJb81IC+zYLM=
=+uPP
-----END PGP SIGNATURE-----

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

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=ind1511&amp;L=BIBFRAME&amp;P=61287
listserv.loc.gov
crawl=CC-MAIN-2019-26
50407
application/http; msgtype=response
sha1:NLDXHDM2SDJC432MNGI45NGD2GC3UGUD
<urn:uuid:b8ba4ef4-10d6-49b2-a163-9dc62afbc4f3>
2019-06-25T04:34:29Z
140.147.55.47
text/html
sha1:O6OYFNKYSGWWJ64WM4YUAHBP6EUTBYON
<urn:uuid:3bfea61f-965d-45d4-b34a-a725040f652e>
https://listserv.loc.gov/cgi-bin/wa?A2=ind1511&amp;L=BIBFRAME&amp;P=61287
response
<urn:uuid:c0932e6e-4c82-4671-a683-73e7bd7e3b23>
isPartOf: CC-MAIN-2019-26
publisher: Common Crawl
description: Wide crawl of the web for June 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-237-29-235.ec2.internal
software: Apache Nutch 1.15 (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/