[XESAM] RDF vs .Desktop

[Evgeny Egorochkin]

Just realized that I KISSed examples too much and didn't notice a mistake.  
Need to sleep more :( and stop talking to myself...

Anyway, resource has to have a prefix: or has to be included in <> brackets.

Also, I changed field naming to xesam:Audio.composer. This seems to be better 
due to Jamie's wish to explicitly link DC and other external ontologies. I 
don't object this either.

These two examples now look like this:

=========    #1      ======================
=====================================
@prefix DC:	 	<http://freedesktop.org/standards/DC#>
@prefix xesam: 	<http://freedesktop.org/standards/xesam#>
@prefix : 			<http://freedesktop.org/standards/xesam_base#>

xesam:Audio.Composer
	a			:field;
	:of_type		:string;
	:has_parent	DC:Creator;
	:name		"Composer"@EN;
	:name		"Композитор"@RU;
	:description	"Audio composer".
=====================================

=========     #2    =======================
You can map rdf:Property to something other like file:Property
not sure which is better. Any ideas for the prefix since xesam: is now used?
I still strongly advise to use #2 an not #1.
=====================================
@prefix rdf:		<http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix DC:	 	<http://freedesktop.org/standards/DC#>
@prefix type: 		<http://freedesktop.org/standards/xesam_base#>
@prefix xesam: 	<http://freedesktop.org/standards/xesam#>
@prefix : 			<http://www.w3.org/2000/01/rdf-schema#>

xesam:Audio.Composer
	a				rdf:Property;
	:range			type:string;
	:subPropertyOf		DC:Creator;
	:label			"Composer"@EN;
	:label			"Композитор"@RU;
	:comment		"Audio composer".
=====================================

Will re-check this when I wake up once more :)

Sorry for confusion.

--Evgeny

On Wednesday 16 May 2007 22:58:54 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".
>
> =====================================
>
> --Evgeny