Talk:RDF Schema

	Internet portal This article is within the scope of WikiProject Internet, a collaborative effort to improve the coverage of the Internet on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InternetWikipedia:WikiProject InternetTemplate:WikiProject InternetInternet articles
???	This article has not yet received a rating on the project's importance scale.

Computing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.

Classes and subclasses?

Would it be correct to say the following should be added to the description of classes and subclasses:

foaf:Person rdf:Class rdf:Class

? If I got it right... --Dan|^(talk) 15:23, 11 January 2010 (UTC)[reply]

This is a very old question, but just for closure, the triple that fits in this case is:

   foaf:Person rdf:type rdf:Class

However it is not necessary to add this to the description because it is entailed by

   ex:John rdf:type foaf:Person

because the rdfs:range of rdf:type is rdf:Class. — Preceding unsigned comment added by Greentaratoo (talk • contribs) 18:48, 3 March 2016 (UTC)[reply]

Mistake in rdf:XMLLiteral?

In the article, there is "rdf:XMLLiteral – the class of XML literal values. rdf:XMLLiteral is an instance of rdfs:Datatype (and thus a subclass of rdfs:Literal)." I think this should be replaced to "rdf:XMLLiteral – the class of XML literal values. rdf:XMLLiteral is an instance of rdfs:Datatype and a subclass of rdfs:Literal". Thre reason: looking at [1] rdf:XMLLiteral is an instance of rdfs:Datatype and a subclass of rdfs:Literal and according to [2] rdfs:Datatype is an instance of rdfs:Class and a subclass of rdfs:Class.

[1] http://www.w3.org/1999/02/22-rdf-syntax-ns [2] http://www.w3.org/2000/01/rdf-schema — Preceding unsigned comment added by Chrdebru (talk • contribs) 07:29, 12 January 2011 (UTC)[reply]

Error in Zoo/Cat/Animal Example

Just out of curiosity, isn't the definition of "Dog1" as a type of "Animal" incorrect? Dog1 is an example of an animal, but not a type. Art2welp (talk) 04:41, 12 February 2016 (UTC)[reply]

It's not defined as "a type of animal". The rdf:type of "Dog1" is "animal", but that's not the same thing (as you note, it just means that Dog1 is an example of an animal). On the other paw, "cat" is defined as "a type of animal" using rdfs:subClassOf. Andy Dingley (talk) 19:13, 12 February 2016 (UTC)[reply]

Yes ... and "cat1" is an rdf:type of "cat," which is a subClassOf "animal." I was really just trying to point out that rdf:type isn't very clearly defined, if that hierarchy isn't enforced. Perhaps we can add "cat1 rdf:type animal" to the example to at least illustrate that polyhierarchy. Art2welp (talk) 21:11, 17 February 2016 (UTC)[reply]

There is nothing wrong with the example and adding "cat1 rdf:type animal" would be redundant. If cat1 is an instance of (aka has the datatype) cat and cat is a subclass of animal then by definition cat1 is also an animal. This is just standard object-oriented design terminology that any technical person should be familiar with. Classes are datatypes, at least in any strongly typed OO language such as C++ or Java. I realize there are significant differences between standard object-oriented design and RDFS and OWL objects but considering classes as types and subclasses as subtypes is one thing both paradigms have in common. --MadScientistX11 (talk) 20:09, 4 September 2019 (UTC)[reply]

I think the example is misleading and poorly worded causing confusion in people not familiar with RDF in general. I have rewritten it and tried making it more intuitive. --2001:14BA:A0DD:FB00:0:0:0:1794 (talk) 09:26, 5 June 2024 (UTC)[reply]

Concept of Well-Formed Graph Comes From Where?

There is no concept of "well-formed graph" defined in either the RDF or RDFS specification. Really there is nothing "ill-formed" about the graph in the example in the RDFS entailment section. If a property has a certain range (say ex:animal) and there is a triple that uses that predicate with a certain object (say ex:cat2), then under the RDFS entailment regime, one may infer that ex:cat2 rdf:type ex:animal. No "guessing" is needed or expected - this is just what RDFS entailment means. There is nothing in the graph to indicate that ex:cat is a subclass of ex:animal. Maybe that is what intended (e.g. "cat" stands for Caterpillar tractor) - that doesn't make the graph not "well-formed", whatever that means. There is no source given for this section, so I don't know where this material, or this "well-formed" concept - came from - certainly not from the RDFS specification itself. --Greentaratoo (talk) 01:55, 3 March 2016 (UTC

Take a look at the SPARQL standards and sections on "E-entailment". I'm not even going to try explaining it at this time of night. Andy Dingley (talk) 02:52, 3 March 2016 (UTC)[reply]

You are free to explain, if you like, at whatever time is convenient for you. As to the use of "well-formed" in the SPARQL spec., that is a reference to syntactic well-formedness, not about whether the graph actually entails what the author intended. For example, RDF doesn't allow literals in the subject position, so if the result of some mapping gives something that looks like an RDF triple except it has a literal in the subject position then it is not "well-formed", which is another way of saying it is not an RDF triple. This usage is consistent with the conventional terminology of "well-formed formulas". The graph in the example is well-formed RDF. There are no additional constraints on the graph for the RDFS entailment regime, so any RDF graph is well-formed w.r.t the RDFS entailment regime. "For example, under RDFS entailment, any SPARQL query is legal, but queries that require literals as a binding for a variable in a subject position have no answer because all mappings that result in a set of RDFS entailed triples are not well-formed RDF since RDF forbids literals in the subject position." If the section is to be entitled "RDFS entailment", then it should describe RDFS entailment as defined by the RDF 1.1 specification (https://www.w3.org/TR/rdf11-mt/), not "RDFS entailment regime", which is a different thing, as defined by the SPARQL spec. Otherwise change the name of the section, cite the SPARQL spec (which is a primary source for this concept) and define that concept. But it is not correct to claim that the RDFS entailment regime imposes any kind of restriction on either RDF graphs or SPARQL queries. --Greentaratoo (talk) 03:35, 3 March 2016 (UTC)[reply]

Secondary and Tertiary Sources for RDFS

--Greentaratoo (talk) 02:06, 3 March 2016 (UTC)[reply]

I wouldn't wipe my arse on anything from W3Schools. Andy Dingley (talk) 02:53, 3 March 2016 (UTC)[reply]

Fine, what do suggest as secondary and tertiary sources - SPARQL? That's the origin of the term "RDFS entailment regime", so its a primary source.--Greentaratoo (talk) 03:08, 3 March 2016 (UTC)[reply]

There's a vast pile of RDF secondary material out there in the last decade. Try academia for one, especially Manchester Uni. There really is no shortage. Andy Dingley (talk) 03:18, 3 March 2016 (UTC)[reply]

There is a shortage of such references in this article. --Greentaratoo (talk) 03:39, 3 March 2016 (UTC)[reply]

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on RDF Schema. Please take a moment to review my edit. You may add {{cbignore}} after the link to keep me from modifying it, if I keep adding bad data, but formatting bugs should be reported instead. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether, but should be used as a last resort. I made the following changes:

Attempted to fix sourcing for http://www.dblab.ntua.gr/~bikakis/XML%20and%20Semantic%20Web%20W3C%20Standards%20Timeline-History.pdf

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 03:20, 31 March 2016 (UTC)[reply]

' within their library and "information science (LIS) community" '

It seems just a bit weird that LIS is given as the acronym, but only "information science" is within the double quotes, while 'library and' is outside of them. Toddcs (talk) 20:24, 7 October 2023 (UTC)[reply]