[XESAM] RDF vs .Desktop
Evgeny Egorochkin
phreedom.stdin at gmail.com
Wed May 16 14:02:19 PDT 2007
On Wednesday 16 May 2007 23:35:07 jamie wrote:
> On Wed, 2007-05-16 at 22:58 +0300, Evgeny Egorochkin wrote:
> > It's quite hard to figure out how to best write this to suit the people
> > who like to KISS everything, but I'll try :)
> >
> > Note:
> >
> > I'm using syntax named Turtle(the most used N3 derivative). This is an
> > alternative serialization to RDF+XML and is a well-accepted standard.
> >
> > I will provide only one field definition featuring all aspects like
> > parents, localization etc. No sense to define several fileds.
> > If some feature is not needed, the corresponding line is omitted.
> > @base and @prefix headers are the same for all files.
> > A file can contain as many definitions as you want.
> >
> > 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".
> >
> > =====================================
>
> shouldn;t :subPropertyOf Content.Creator;
> be
>
> Parent DC.Creator
It was an example. It wasn't supposed to be a field definition form any
particular ontology.
> (me thought subPropertyOf is part of the rdfs vocab?)
:subPropertyOf is indeed rdfs:subPropertyOf (take a look at the header). As
you asked, I obscured RDF(s) references as much as possible, and minimized
format overhead by stripping prefixes etc.
The reason I'm for the second example is that some external tools will be able
to extract more semantics from this definition as compared to the first one.
Nevertheless the first one is a valid RDF.
--Evgeny
More information about the xdg
mailing list