StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16299701
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-04-30T12:16:32.217
FavoriteCount
0
LastActivityDate
2013-04-30T12:16:32.217
LastEditDate
LastEditorUserId
0
OwnerUserId
6716
ParentId
16284824
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
It depends what you mean by a bilingual ontology. If you want to have an ontology in which the concepts can be presented to both an English reader and a Romanian reader, but there's only one base set of concepts, then it's fairly easy. The identity of the concept is expressed as a URI, for example: <pre><code><http://example.com/ontology/animals/Dog> a owl:Class . </code></pre> There's only one concept denoting dogs, but you add labels and comments that will allow the class to be presented to users in either language: <pre><code><http://example.com/ontology/animals/Doc> a owl:Class ; rdfs:label "dog"@en ; rdfs:label "câine"@ro ; rdfs:comment "Denotes the class of all dogs"@en ; rdfs:comment "Denotă clasa tuturor câinilor"@ro . </code></pre> Apologies for the Romanian - it was from Google Translate. I hope it makes sense! I don't use Protege, but you should be able to add labels and comments in multiple languages - it's a basic facility in RDF. If, on the other hand, you want to have one ontology that contains concepts drawn from both languages, that can be harder. I don't know Romanian (see above!), so I don't know if this is the case or not, but some languages conceptualise the world in quite different ways, so defining a single ontology that merges concepts from both world-views can be difficult. It's also the case that, while RDF and OWL use UTF-8 as their base encoding, you may find some tools that aren't comfortable processing URI's that contain characters outside of US ASCII. That shouldn't be the case in theory, but you might want to be careful just in case.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to create bilingual ontology in Protege?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USIan Dickinson
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
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
CommentsPostId
1. COTo add a bit of Protégé specific context, this approach was discussed on the Protégé mailing list not too long ago. [The thread](http://thread.gmane.org/gmane.comp.misc.ontology.protege.owl/37684) discussed how the ordering of entities in the Ontology could be based on labels in one language or another.
 singulars
 PostPostId
 PO
 UserUserId
 USJoshua Taylor

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.