StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18147583
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-09T13:18:52.690
FavoriteCount
0
LastActivityDate
2013-08-09T13:18:52.690
LastEditDate
LastEditorUserId
0
OwnerUserId
1281433
ParentId
18145663
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Well, you can use the string based approach, though I'd strongly recommend something like: <pre class="lang-java prettyprint-override"><code>String SIOC = "http://sioc.com/ontologies/sioc#"; model.setNsPrefix("sioc",SIOC ); Property ID = model.createProperty( SIOC + "ID" ); </code></pre> to save some typing and possible typos. For many common vocabularies, Jena already has predefined vocabulary classes that define a bunch of useful constants. Most of these live in the <a href="http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/package-summary.html" rel="nofollow">com.hp.hpl.jena.vocabulary</a> package. For instance, in <a href="http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/DCTerms.html" rel="nofollow"><code>DCTerms</code></a> there are constants such as <a href="http://jena.apache.org/documentation/javadoc/jena/com/hp/hpl/jena/vocabulary/DCTerms.html#creator" rel="nofollow"><code>creator</code></a> so that you can do things like <pre class="lang-java prettyprint-override"><code>Resource r = ...; r.addProperty( DCTerms.creator, ... ); </code></pre> Of course, Jena can only predefine so many of these classes. For others, you can use Jena's <a href="http://jena.apache.org/documentation/tools/schemagen.html" rel="nofollow">schemagen</a> to generate those kinds of classes. It's a command line tool (but you can also call it programmatically, I believe), and pass it the RDF or OWL file that defines the vocabulary, and you get a <code>.java</code> file back that constants constants for all the properties, classes, and individuals in the vocabulary. You can get simple Model-based resources, or OntModel-based resources, too. It's quite configurable, and I've used in a number of projects.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWriting RDF by importing namespaces from a loaded ontologies in jena?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJoshua Taylor
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWriting RDF by importing namespaces from a loaded ontologies in jena?
 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
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.