StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7323558
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2011-09-06T17:08:24.250
FavoriteCount
0
LastActivityDate
2011-09-07T07:32:11.033
LastEditDate
2011-09-07T07:32:11.033
LastEditorUserId
112091
OwnerUserId
112091
ParentId
7312848
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I believe there is some misunderstanding here concerning RDF and XML. RDF is a bunch of triples that can be expressed both in XML and in other serialization formats. Unlike XML, RDF is not hierarchical, therefore there is no such a thing as "subelement" in RDF. The fact that Mr. Guid is just is under Mr Node_1 is an illusion "suggested" by the misleading XML node hierarchy. To demonstrate that, I list the triples of your examples (please, mind that the order of triples in RDF is irrelevant!): "Node 1" typeOf Person "Node 1" depiction "Default.png" "Node 1" description "Description" "Node 1" knows "Mr. Guid" "Mr. Guid" typeOf Person "Node 2" typeOf Person "Node 2" depiction "Default.png" "Node 2" description "Description" Try the following: Add one more triple: "Mr. Guid" knows "Node 1" with the following code: <pre><code>Person mrGuid = _rdfDocument.GetIndividual("6779ac10-210b-40d2-8111-711db6988bb9") as Person; Person mrNode1 = _rdfDocument.GetIndividual("Node 1") as Person; mrGuid.knows = mrNode1; Console.WriteLine(_rdfDocument.ToRdfXml()); </code></pre> Now, both Node 1 knows Mr Guid and Mr Guid knows Node 1, and this is a perfectly legal scenario. Who would be the root and who would be the subelement? The XML serializer will probably pick the first one in row to be the "root" and the other as the "subelement", but it is arbitrary. The nesting is just an illusion created by the XML serialization. Do not fall for that. The query you fire with the <code>rdfDocument.GetIndividuals(Person.Uri, true);</code> statement simply filters out all individuals that is of type <code>Person</code>, and hence it returns correctly all the three guys.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PORowlex - Getting only "root" individuals of a document
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USROWLEX Admin
UserOwnerUserId
1. USROWLEX Admin
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PORowlex - Getting only "root" individuals of a document
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. CO"there is no such thing as "subelement" in RDF" that was in fact my error, I was too focused on the xml! we resolved the problem by changing a little bit the ontologie.
 singulars
 PostPostId
 PO
 UserUserId
 USyazer

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.