Hi Evgeny, thanks a lot for this example.
On Wednesday 16 May 2007 21:58:54 Evgeny Egorochkin wrote: > I will provide only one field definition featuring all aspects like > parents, localization etc. No sense to define several fileds. I agree. > First attempt: > > ===================================== > @base <http://freedesktop.org/standards/xesam#> > > Audio.Composer > a field; > of_type string; > has_parent Content.Creator; > name "Composer"@EN; > name "Композитор"@RU; > description "Audio composer". > ===================================== > > Second attempt. This is the one I'd prefer, despite first attempt looking > slighly better. Note that base url is xesam ns. Xesam: prefix actually > points to RDF ns, so that we use xesam:Property instead of rdf:property and > hide rdf traces completely :) > ===================================== > @prefix xesam: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. > @prefix : <http://www.w3.org/2000/01/rdf-schema#> > @base <http://freedesktop.org/standards/xesam#> > > Audio.Composer > a xesam:Property; > > :range string; > :subPropertyOf Content.Creator; > :label "Composer"@EN; > :label "Композитор"@RU; > :comment "Audio composer". > > ===================================== I, of course, also vote for the second version since it is clean and standard-compliant. This way our ontologies can be used and interconnected with every semantic tool and ontology. Cheers, Sebastian _______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
