jena - How to create an ontology in Java? -

i've data triplets want write in sort of basic owl ontology. i've triplets like:

delhi part of india  

or

india asian country 

note i've relations "is-a", "part-of", or "related-to". what's simplest way build ontology? working example or reference example website great help!

there lot of different things mixed in question, suggest take bit of time (away keyboard!) think through you're trying achieve here.

firstly, geographic ontologies can quite complex, , lot of work has been done in area. obvious starting point geonames ontology, gives names geographic features, including cities dehli , countries india. @ least should re-use names places in application, maximise chances data can joined other available linked-data sources.

however, don't want whole of geonames in application (i'm guessing), need clear why need ontology @ all. way approach outside of application: rather worry kind of jena model use, start thinking through ways complete sentence "using ontology, user of application able ...". should lead on establishing competency questions (see, example, section 3 of guide) ontology. once know kinds of information want represent, , kinds of queries need apply it, technology choices clearer. realise these applications typically developed iteratively, , you'll want try code out on, still advocate getting destination more in mind before start coding journey.

you imply want use jena drive web site. there many choices here. don't mislead term semantic web - means bringing web-like qualities interlined data sets, rather putting semantics human readable web pages per se. while can so, , many people do, you'll need additional layers in architecture. typically use 1 of 2 approaches: using jena templating engine, such velocity, in servlets container, or using ruby web framework , driving jena via jruby. there many other ways solve particular problem: jena doesn't address web publishing directly, can used within java-based web framework.

finally, regarding namespaces, should re-use existing vocabularies, , hence namespaces, possible. don't make new names things have representations on web of data somewhere. use geonames, or dbpedia, or of many other published vocabularies fit. if don't fit, should create new name rather use existing name in non-compatible way. in case, should use web domain of application (e.g. company or university) basis namespace. ideally, should publish ontology @ base url of namespace, can hard arrange depending on local web policies.