<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Music Ontology revision 1.10: introduction of musical performances as events in time</title>
	<atom:link href="http://fgiasson.com/blog/index.php/2007/02/26/music_ontology_revision_1_10_introductio/feed/" rel="self" type="application/rss+xml" />
	<link>http://fgiasson.com/blog/index.php/2007/02/26/music_ontology_revision_1_10_introductio/</link>
	<description></description>
	<lastBuildDate>Tue, 15 May 2012 14:41:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Fred</title>
		<link>http://fgiasson.com/blog/index.php/2007/02/26/music_ontology_revision_1_10_introductio/comment-page-1/#comment-667</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Fri, 02 Mar 2007 00:30:38 +0000</pubDate>
		<guid isPermaLink="false">#comment-667</guid>
		<description>Hi Everybody,&lt;br /&gt;
&lt;br /&gt;
Chris: I think that both Yves and Samer answered to all your questions. However, I played a log with the ontology today to map musicbrainz with it. I also discussed a lot with Yves about many things and some issue has been discovered (small ones) and we discussed a lot about how to make the ontology clearer and simpler to understand.&lt;br /&gt;
&lt;br /&gt;
We developed a couple of workflow, we will have to rework some definitions, re-introduce some basic properties to explicits relations. With a data dump of musicbrainz using MO and a document explaining the mapping, I think (and hope) and the revision 1.10 of the ontology will be much more easy to understand.&lt;br /&gt;
&lt;br /&gt;
Take care,&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Fred</description>
		<content:encoded><![CDATA[<p>Hi Everybody,</p>
<p>Chris: I think that both Yves and Samer answered to all your questions. However, I played a log with the ontology today to map musicbrainz with it. I also discussed a lot with Yves about many things and some issue has been discovered (small ones) and we discussed a lot about how to make the ontology clearer and simpler to understand.</p>
<p>We developed a couple of workflow, we will have to rework some definitions, re-introduce some basic properties to explicits relations. With a data dump of musicbrainz using MO and a document explaining the mapping, I think (and hope) and the revision 1.10 of the ontology will be much more easy to understand.</p>
<p>Take care,</p>
<p>
Fred</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Samer Abdallah</title>
		<link>http://fgiasson.com/blog/index.php/2007/02/26/music_ontology_revision_1_10_introductio/comment-page-1/#comment-666</link>
		<dc:creator>Samer Abdallah</dc:creator>
		<pubDate>Wed, 28 Feb 2007 16:46:36 +0000</pubDate>
		<guid isPermaLink="false">#comment-666</guid>
		<description>A couple of points:&lt;br /&gt;
&lt;br /&gt;
Firstly, about the time varying properties like band membership etc. This is issue was forseen and&lt;br /&gt;
is part of the reason why we adopted an event based knowledge representation so deeply into the&lt;br /&gt;
system. In this case, one would declare a &#039;Membership event&#039; which covers the time interval for which&lt;br /&gt;
the membership holds. A query such as memberOf(&#039;BritneySpears&#039;,X) would then only have meaning&lt;br /&gt;
relative to a current time (ie it would be a modal  query). The Event ontology is indeed an expression&lt;br /&gt;
of the perdurantist view - the least offensive definition for an event we have found is &#039;an event is a &lt;br /&gt;
classification of a region of space-time (or just time if space is irrelevant).&lt;br /&gt;
&lt;br /&gt;
From this point of view, a Sound (event) is the classification of some region of space-time as containing&lt;br /&gt;
or supporting an acoustic field - ie a *physical* thing. If the sound is recorded as it happens, there is&lt;br /&gt;
another event which characterises the transduction of the acoustic field into a signal. At this point, we&lt;br /&gt;
consider the signal to be an informational/mathematical objects and we no-longer need events to&lt;br /&gt;
describe it. &lt;br /&gt;
&lt;br /&gt;
In the case of electronic music produced directly a digital signal, there is no recording and no sound&lt;br /&gt;
until the signal played through a speaker. This is also described using two events - the resulting sound,&lt;br /&gt;
and a &#039;Playback&#039; event which mirrors a recording, and represents the realisation of an informational object (the signal) as a physical process (the sound).&lt;br /&gt;
&lt;br /&gt;
There is no obstacle to representing such things in the ontology. It just means that if you ask for recording events, or objects resulting from recording events, you won&#039;t get this electronic music. &lt;br /&gt;
You woudl have to ask for, say, signals which are ultimately derived from this or that Work - there&lt;br /&gt;
would have to a property relating a Work (conceptual) or a score (informational) directly to the resulting&lt;br /&gt;
signal. For example, if I use timidity to synthesise a midi sequence using certain parameters, there is&lt;br /&gt;
a functional relation tying the midi score to the resulting signal. &lt;br /&gt;
&lt;br /&gt;
If the situation is more complicated, with say, a live laptop performance, with a human controlling the&lt;br /&gt;
synthesis in unpredictable ways while it is going on, and signal going directly to a file, then there is a&lt;br /&gt;
(physical) Performance event, but the product is not a Sound, but a Signal.&lt;br /&gt;
&lt;br /&gt;
And yes, Sound should not be a subclass of MusicalExpression.&lt;br /&gt;
&lt;br /&gt;
Cheers,&lt;br /&gt;
</description>
		<content:encoded><![CDATA[<p>A couple of points:</p>
<p>Firstly, about the time varying properties like band membership etc. This is issue was forseen and<br />
is part of the reason why we adopted an event based knowledge representation so deeply into the<br />
system. In this case, one would declare a &#8216;Membership event&#8217; which covers the time interval for which<br />
the membership holds. A query such as memberOf(&#8216;BritneySpears&#8217;,X) would then only have meaning<br />
relative to a current time (ie it would be a modal  query). The Event ontology is indeed an expression<br />
of the perdurantist view &#8211; the least offensive definition for an event we have found is &#8216;an event is a <br />
classification of a region of space-time (or just time if space is irrelevant).</p>
<p>From this point of view, a Sound (event) is the classification of some region of space-time as containing<br />
or supporting an acoustic field &#8211; ie a *physical* thing. If the sound is recorded as it happens, there is<br />
another event which characterises the transduction of the acoustic field into a signal. At this point, we<br />
consider the signal to be an informational/mathematical objects and we no-longer need events to<br />
describe it. </p>
<p>In the case of electronic music produced directly a digital signal, there is no recording and no sound<br />
until the signal played through a speaker. This is also described using two events &#8211; the resulting sound,<br />
and a &#8216;Playback&#8217; event which mirrors a recording, and represents the realisation of an informational object (the signal) as a physical process (the sound).</p>
<p>There is no obstacle to representing such things in the ontology. It just means that if you ask for recording events, or objects resulting from recording events, you won&#8217;t get this electronic music. <br />
You woudl have to ask for, say, signals which are ultimately derived from this or that Work &#8211; there<br />
would have to a property relating a Work (conceptual) or a score (informational) directly to the resulting<br />
signal. For example, if I use timidity to synthesise a midi sequence using certain parameters, there is<br />
a functional relation tying the midi score to the resulting signal. </p>
<p>If the situation is more complicated, with say, a live laptop performance, with a human controlling the<br />
synthesis in unpredictable ways while it is going on, and signal going directly to a file, then there is a<br />
(physical) Performance event, but the product is not a Sound, but a Signal.</p>
<p>And yes, Sound should not be a subclass of MusicalExpression.</p>
<p>Cheers,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yves Raimond</title>
		<link>http://fgiasson.com/blog/index.php/2007/02/26/music_ontology_revision_1_10_introductio/comment-page-1/#comment-664</link>
		<dc:creator>Yves Raimond</dc:creator>
		<pubDate>Wed, 28 Feb 2007 15:56:13 +0000</pubDate>
		<guid isPermaLink="false">#comment-664</guid>
		<description>Hi Chris!&lt;br /&gt;
&lt;br /&gt;
Yes - you are totally right, we consider the sound as being the &quot;physical sound&quot; itself.  I think the cognition of the sound is thus not expressed here, but this could surely be an extension of the ontology! That&#039;s one of the main point now: the ontology provides &quot;anchor points&quot;, so we can act as a backbone ontology for other stuff: automatic feature extraction (often linked to the concept of Event), cognition (linked to this Sound concept), recording stuff (microphones, DAC, linked to Recording)... &lt;br /&gt;
&lt;br /&gt;
In the case of electronic music, that is an issue. We could maybe consider the sound as an informational object there? To be discussed...&lt;br /&gt;
&lt;br /&gt;
Btw, are you a member of the mailing list? Its archives are here:&lt;br /&gt;
http://groups.google.com/group/music-ontology-specification-group&lt;br /&gt;
&lt;br /&gt;
It could be great to chat a bit more about all these points on this list! Could you send your comments there?&lt;br /&gt;
&lt;br /&gt;
Thanks,&lt;br /&gt;
y&lt;br /&gt;
&lt;br /&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Chris!</p>
<p>Yes &#8211; you are totally right, we consider the sound as being the &#8220;physical sound&#8221; itself.  I think the cognition of the sound is thus not expressed here, but this could surely be an extension of the ontology! That&#8217;s one of the main point now: the ontology provides &#8220;anchor points&#8221;, so we can act as a backbone ontology for other stuff: automatic feature extraction (often linked to the concept of Event), cognition (linked to this Sound concept), recording stuff (microphones, DAC, linked to Recording)&#8230; </p>
<p>In the case of electronic music, that is an issue. We could maybe consider the sound as an informational object there? To be discussed&#8230;</p>
<p>Btw, are you a member of the mailing list? Its archives are here:<br />
<a href="http://groups.google.com/group/music-ontology-specification-group" rel="nofollow">http://groups.google.com/group/music-ontology-specification-group</a></p>
<p>It could be great to chat a bit more about all these points on this list! Could you send your comments there?</p>
<p>Thanks,<br />
y</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Mungall</title>
		<link>http://fgiasson.com/blog/index.php/2007/02/26/music_ontology_revision_1_10_introductio/comment-page-1/#comment-665</link>
		<dc:creator>Chris Mungall</dc:creator>
		<pubDate>Wed, 28 Feb 2007 06:06:37 +0000</pubDate>
		<guid isPermaLink="false">#comment-665</guid>
		<description>Sound is both an Event and a MusicalExpression. Surely there are sounds that are not musical expressions?&lt;br /&gt;
&lt;br /&gt;
The comment for sound is:&lt;br /&gt;
&lt;br /&gt;
A subclass of MusicalExpression, representing a sound.&lt;br /&gt;
&lt;br /&gt;
I&#039;m not sure if this is intended to be a text definition. If so, it commits the use/mention mistake. May I suggest the wording of the definition denotes the instances the class represents. Instead of &quot;A subclass of MusicalExpression&quot;, which not say &quot;A MusicalExpression&quot; (assuming this definition is correct)?&lt;br /&gt;
&lt;br /&gt;
According to this comment, A sound represents a sound. This is circular.&lt;br /&gt;
&lt;br /&gt;
I think you want to mention the phsyics of sounds (and possibly their perception as well - you should take a position on the hoary old philosophical chestnut about sounds in a forest devoid of listeners).&lt;br /&gt;
&lt;br /&gt;
Meriam Webster has:&lt;br /&gt;
&lt;br /&gt;
mechanical radiant energy that is transmitted by longitudinal pressure waves in air or other material medium and is the objective cause of the sensation of hearing&lt;br /&gt;
&lt;br /&gt;
Which seems reasonable.&lt;br /&gt;
&lt;br /&gt;
However, this would cause problems for electronic music in which the &quot;recording&quot; is made from entirely synthesised sounds&lt;br /&gt;
Can I use the MO to express statements like:&lt;br /&gt;
&lt;br /&gt;
Theremins sound spooky to me&lt;br /&gt;
&lt;br /&gt;
Black metal sounds like cats being strangled&lt;br /&gt;
&lt;br /&gt;
What about found sounds? And this:&lt;br /&gt;
http://www.amazon.com/Stockhausen-Helikopter-Streichquartett-Helicopter-Quartet/dp/B00004NJJX&lt;br /&gt;
</description>
		<content:encoded><![CDATA[<p>Sound is both an Event and a MusicalExpression. Surely there are sounds that are not musical expressions?</p>
<p>The comment for sound is:</p>
<p>A subclass of MusicalExpression, representing a sound.</p>
<p>I&#8217;m not sure if this is intended to be a text definition. If so, it commits the use/mention mistake. May I suggest the wording of the definition denotes the instances the class represents. Instead of &#8220;A subclass of MusicalExpression&#8221;, which not say &#8220;A MusicalExpression&#8221; (assuming this definition is correct)?</p>
<p>According to this comment, A sound represents a sound. This is circular.</p>
<p>I think you want to mention the phsyics of sounds (and possibly their perception as well &#8211; you should take a position on the hoary old philosophical chestnut about sounds in a forest devoid of listeners).</p>
<p>Meriam Webster has:</p>
<p>mechanical radiant energy that is transmitted by longitudinal pressure waves in air or other material medium and is the objective cause of the sensation of hearing</p>
<p>Which seems reasonable.</p>
<p>However, this would cause problems for electronic music in which the &#8220;recording&#8221; is made from entirely synthesised sounds<br />
Can I use the MO to express statements like:</p>
<p>Theremins sound spooky to me</p>
<p>Black metal sounds like cats being strangled</p>
<p>What about found sounds? And this:<br />
<a href="http://www.amazon.com/Stockhausen-Helikopter-Streichquartett-Helicopter-Quartet/dp/B00004NJJX" rel="nofollow">http://www.amazon.com/Stockhausen-Helikopter-Streichquartett-Helicopter-Quartet/dp/B00004NJJX</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Mungall</title>
		<link>http://fgiasson.com/blog/index.php/2007/02/26/music_ontology_revision_1_10_introductio/comment-page-1/#comment-663</link>
		<dc:creator>Chris Mungall</dc:creator>
		<pubDate>Wed, 28 Feb 2007 05:37:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-663</guid>
		<description>hmm, cutting and pasting RDF/XML doesn&#039;t appear to work here. The example was the 4th one here:&lt;br /&gt;
http://pingthesemanticweb.com/ontology/mo/#sec-example-level1</description>
		<content:encoded><![CDATA[<p>hmm, cutting and pasting RDF/XML doesn&#8217;t appear to work here. The example was the 4th one here:<br />
<a href="http://pingthesemanticweb.com/ontology/mo/#sec-example-level1" rel="nofollow">http://pingthesemanticweb.com/ontology/mo/#sec-example-level1</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Mungall</title>
		<link>http://fgiasson.com/blog/index.php/2007/02/26/music_ontology_revision_1_10_introductio/comment-page-1/#comment-662</link>
		<dc:creator>Chris Mungall</dc:creator>
		<pubDate>Wed, 28 Feb 2007 05:33:59 +0000</pubDate>
		<guid isPermaLink="false">#comment-662</guid>
		<description>The MO has advanced a lot since its first inception.&lt;br /&gt;
&lt;br /&gt;
It is interesting to see the MO address issues of time. It&#039;s widely known that OWL has problems with time (which the OWL time ontology do not solve). To illustrate, let me take one example from the MO documentation:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 2         Britney Spears&lt;br /&gt;
 3         &lt;br /&gt;
 4         ...&lt;br /&gt;
 5     &lt;br /&gt;
&lt;br /&gt;
 6     &lt;br /&gt;
 7         Kevin Federline&lt;br /&gt;
 8         ...&lt;br /&gt;
 9      &lt;br /&gt;
&lt;br /&gt;
OWL assumes a static world in which BritneySpears married_to KevinFederline holds eternally. This is not an accurate representation of reality. relations between continuants (3-Dimensional entities such as Britney Spears or Britney Spears&#039; hair) hold for temporal durations.&lt;br /&gt;
&lt;br /&gt;
BritneySpears stands in a married_to Jason Allen Alexander on 1/3/05, and in a married_to relation to Kevin Federline on 2/27/07. An OWL reasoner would conclude that Britney Spears is polyandrous.&lt;br /&gt;
&lt;br /&gt;
The solution in this case is to explicitly represent dependent continuants such as Marriages. The two different marriage instances that Britney Spears participates_in could be time-indexed. A similar solution could be applied to other relationships such as being in a band together. This would involve some changes to the MO.&lt;br /&gt;
&lt;br /&gt;
This solution is unsatisfactory for certain kinds of relations. For example, Britney Spears Hair was part_of Britney Spears on 1/3/05, but that same aggregate of hairs is not part_of Britney Spears on 2/27/07. Here, representing what are clearly relations as instances of relationship classes is unsatifactory, as are other solutions such as turning Britney Spears into a time-worm (the so-called perdurantist ontological position, in which there are no continuants such as Britney Spears, only processes, such as the process of Britney Spears life and parts of Britney Spears life).&lt;br /&gt;
&lt;br /&gt;
This may not be such a problem for the MO, which does not in general deal with changing anatomical features of artists; the primary entities in MO are processes such as performances  where this problem does not arise. </description>
		<content:encoded><![CDATA[<p>The MO has advanced a lot since its first inception.</p>
<p>It is interesting to see the MO address issues of time. It&#8217;s widely known that OWL has problems with time (which the OWL time ontology do not solve). To illustrate, let me take one example from the MO documentation:</p>
<p>
 2         Britney Spears<br />
 3         <br />
 4         &#8230;<br />
 5     </p>
<p> 6     <br />
 7         Kevin Federline<br />
 8         &#8230;<br />
 9      </p>
<p>OWL assumes a static world in which BritneySpears married_to KevinFederline holds eternally. This is not an accurate representation of reality. relations between continuants (3-Dimensional entities such as Britney Spears or Britney Spears&#8217; hair) hold for temporal durations.</p>
<p>BritneySpears stands in a married_to Jason Allen Alexander on 1/3/05, and in a married_to relation to Kevin Federline on 2/27/07. An OWL reasoner would conclude that Britney Spears is polyandrous.</p>
<p>The solution in this case is to explicitly represent dependent continuants such as Marriages. The two different marriage instances that Britney Spears participates_in could be time-indexed. A similar solution could be applied to other relationships such as being in a band together. This would involve some changes to the MO.</p>
<p>This solution is unsatisfactory for certain kinds of relations. For example, Britney Spears Hair was part_of Britney Spears on 1/3/05, but that same aggregate of hairs is not part_of Britney Spears on 2/27/07. Here, representing what are clearly relations as instances of relationship classes is unsatifactory, as are other solutions such as turning Britney Spears into a time-worm (the so-called perdurantist ontological position, in which there are no continuants such as Britney Spears, only processes, such as the process of Britney Spears life and parts of Britney Spears life).</p>
<p>This may not be such a problem for the MO, which does not in general deal with changing anatomical features of artists; the primary entities in MO are processes such as performances  where this problem does not arise.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (Requested URI is rejected)
Database Caching using disk: basic

Served from: fgiasson.com @ 2012-05-23 05:27:05 -->
