-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Concerning the statistics 6.6.2.6 #121
Comments
The intent of 6.6.2.6 is to capture the total number of triples between subjects and objects of a specified type e.g. 100 distinct subjects may be connected to 10 distinct objects via 100 triples. |
I cannot fully understand what the meaning of to declare a property partition on "rdfs:property".
|
6.6.2.6 does just this, does it not? |
I don't think so. count(distinct ?s) = 100, count(distinct ?o) = 1, count(?p) = 100
count(distinct ?s) = 10, count(distinct ?o) = 10, count(?p) = 100
|
so 6.6.2.2 talks about properties and number of triples. This query is not, however, limited to the subject and object being of some arbitrary type - we imagine that this is necessarily true. SELECT ?p (COUNT(?p) AS ?triples) |
That is to say, would 6.6.2.6 be as follows?
|
yes that's right |
Hi,
The spec of 6.6.2.6 defines the unique numbers of subjects and objects w.r.t a predicate.
This shows one aspect of the triples connecting two classes, but another cannot be obtained.
It is the unique number of triples connecting the two classes.
More properly, it specifies the number of unique triples that connects typed subjects and objects, which belong to certain classes, respectively.
One extreme example is that 100 different subjects have an identical property.
The former says that 100 distinctSubjects and 1 distinctObject(s) while the latter says 100 triples.
Another example is that each of 10 different subjects has an identical set of 10 properties.
The former says that 10 distinctSubjects and 10 distinctObjects while the latter says 100 triples.
I think the latter statistics is also useful to know the characteristics of the target dataset, and I feel this was on the document before, wasn't it?
The text was updated successfully, but these errors were encountered: