Next question. A festival is a subclass of event:Event, that's fine.
And I can decompose it into sub-events like individual performances.
Now what about the "containment" of a festival in a row of festivals?
We have Montreux, Salzau, Monterey, enjoy-jazz (in Mannheim/Heidelberg/
Ludwigshafen, where I like to spend most of autumn), all of them
repeat. Is there some vocabulary for "sequence of festivals with a
common name" (and sometimes common character)?
In a certain sense, "enjoy-jazz" is a class of its own, the class of
all festivals with this title/staff etc., but I'm a little bit
reluctant to spread classes all around like that. And a class
certainly has no start date, while a row of festivals has. So I'd like
to model this roughly analogous to spatial containment. But I miss the
upper category.
> Next question. A festival is a subclass of event:Event, that's fine. > And I can decompose it into sub-events like individual performances. > Now what about the "containment" of a festival in a row of festivals? > We have Montreux, Salzau, Monterey, enjoy-jazz (in Mannheim/Heidelberg/ > Ludwigshafen, where I like to spend most of autumn), all of them > repeat. Is there some vocabulary for "sequence of festivals with a > common name" (and sometimes common character)? > In a certain sense, "enjoy-jazz" is a class of its own, the class of > all festivals with this title/staff etc., but I'm a little bit > reluctant to spread classes all around like that. And a class > certainly has no start date, while a row of festivals has. So I'd like > to model this roughly analogous to spatial containment. But I miss the > upper category.
Hi Chris,
this is indeed a very good observation. As far as I know, there is currently no real property or concept to describe your concern. Hence, we probably need something: - to describe a tour/ event series of several concerts/shows -> that means for me currently, e.g. "ex:Tour a event:Event", which consists then of several sub events - to describe an annual event -> this can probably also be modelled as an event:Event, e.g. "ex:AnnualEvent", which has a specific time interval (similar as these ones of the Days of the Week Ontology) as object of its event:time property relation
> > Next question. A festival is a subclass of event:Event, that's fine.
> > And I can decompose it into sub-events like individual performances.
> > Now what about the "containment" of a festival in a row of festivals?
> > We have Montreux, Salzau, Monterey, enjoy-jazz (in Mannheim/Heidelberg/
> > Ludwigshafen, where I like to spend most of autumn), all of them
> > repeat. Is there some vocabulary for "sequence of festivals with a
> > common name" (and sometimes common character)?
> > In a certain sense, "enjoy-jazz" is a class of its own, the class of
> > all festivals with this title/staff etc., but I'm a little bit
> > reluctant to spread classes all around like that. And a class
> > certainly has no start date, while a row of festivals has. So I'd like
> > to model this roughly analogous to spatial containment. But I miss the
> > upper category.
> Hi Chris,
> this is indeed a very good observation. As far as I know, there is
> currently no real property or concept to describe your concern. Hence,
> we probably need something:
> - to describe a tour/ event series of several concerts/shows -> that
> means for me currently, e.g. "ex:Tour a event:Event", which consists
> then of several sub events
> - to describe an annual event -> this can probably also be modelled as
> an event:Event, e.g. "ex:AnnualEvent", which has a specific time
> interval (similar as these ones of the Days of the Week Ontology) as
> object of its event:time property relation
The only problem I see with this approach is that the intervals could
change. Couldn't we have an abstract class like "iterable event" (I'm
sorry, I still think in Python metaphors. ;-) Repeating events, even
composite events like a jazz festival, are something so common - art
biennales, film festivals, Bayreuth, olympic games. I can't imagine
that there's no "mixin" class like that in the world of ontologies.
> On Sep 2, 11:51 pm, Bob Ferris<z...@elbklang.net> wrote: >> Am 02.09.2010 23:36, schrieb Chris P:
>>> Next question. A festival is a subclass of event:Event, that's fine. >>> And I can decompose it into sub-events like individual performances. >>> Now what about the "containment" of a festival in a row of festivals? >>> We have Montreux, Salzau, Monterey, enjoy-jazz (in Mannheim/Heidelberg/ >>> Ludwigshafen, where I like to spend most of autumn), all of them >>> repeat. Is there some vocabulary for "sequence of festivals with a >>> common name" (and sometimes common character)? >>> In a certain sense, "enjoy-jazz" is a class of its own, the class of >>> all festivals with this title/staff etc., but I'm a little bit >>> reluctant to spread classes all around like that. And a class >>> certainly has no start date, while a row of festivals has. So I'd like >>> to model this roughly analogous to spatial containment. But I miss the >>> upper category.
>> Hi Chris,
>> this is indeed a very good observation. As far as I know, there is >> currently no real property or concept to describe your concern. Hence, >> we probably need something: >> - to describe a tour/ event series of several concerts/shows -> that >> means for me currently, e.g. "ex:Tour a event:Event", which consists >> then of several sub events >> - to describe an annual event -> this can probably also be modelled as >> an event:Event, e.g. "ex:AnnualEvent", which has a specific time >> interval (similar as these ones of the Days of the Week Ontology) as >> object of its event:time property relation
> The only problem I see with this approach is that the intervals could > change. Couldn't we have an abstract class like "iterable event" (I'm > sorry, I still think in Python metaphors. ;-) Repeating events, even > composite events like a jazz festival, are something so common - art > biennales, film festivals, Bayreuth, olympic games. I can't imagine > that there's no "mixin" class like that in the world of ontologies.
Ah sorry, maybe my description was a bit misleading. So I try to illustrate this in an example, which is quite similar to the classes from the Days of a Week Ontology[1]. We can have a annual interval or annual instant:
ex:AnnualInterval rdf:type owl:Class ; rdfs:comment "Specify a duration using tl:duration and a day or month when this annual interval begins."@en ; rdfs:label "Annual Interval"@en ; rdfs:subClassOf time:Interval ; owl:equivalentClass [ rdf:type owl:Class ; owl:intersectionOf ([ rdf:type owl:Restriction ; owl:hasValue ex:annual_timeline ; owl:onProperty tl:timeline ] time:Interval) ] .
ex:AnnualInstant rdf:type owl:Class ; rdfs:comment "Specify an approximate time instant - a day or month."@en ; rdfs:label "Annual Instant"@en ; rdfs:subClassOf time:Instant ; owl:equivalentClass [ rdf:type owl:Class ; owl:intersectionOf ([ rdf:type owl:Restriction ; owl:hasValue ex:annual_timeline ; owl:onProperty tl:timeline ] time:Instant) ] .
ex:annual_timeline rdf:type tl:TimeLine ; dc:description "Starting and ending in between an interval of a year."@en ; dc:title "Annual Timeline"@en .
# this property isn't currently a part of the Timeline Ontology tl:atMonth rdfs:label "at month"; rdfs:comment "A subproperty of :at, allowing to address a month (beginning of it for an instant, all of it for an interval)"; vs:term_status "stable"; a owl:DatatypeProperty; rdfs:subPropertyOf :at; rdfs:range xsd:gMonth .
I'm currently, unsure whether this is really the best modelling here, because the description of an annual festival has uncertain time intervals and instants. Nevertheless, I try to model an example with them ;)
ex:EnjoyJazz a ex:AnnualEvent ; event:time [ a ex:AnnualInterval ; tl:atMonth "--10"^^xsd:gMonth ; tl:duration "P2M"^^xsd:duration ] ; event:sub_event ex:EnjoyJazz2010 .
ex:EnjoyJazz2010 a mo:Festival ; event:time [ a tl:UTInterval ; tl:at "2010-10-02T18:00:00Z" ; tl:duration "P2M"^^xsd:duration ] .
> > On Sep 2, 11:51 pm, Bob Ferris<z...@elbklang.net> wrote:
> >> Am 02.09.2010 23:36, schrieb Chris P:
> >>> Next question. A festival is a subclass of event:Event, that's fine.
> >>> And I can decompose it into sub-events like individual performances.
> >>> Now what about the "containment" of a festival in a row of festivals?
> >>> We have Montreux, Salzau, Monterey, enjoy-jazz (in Mannheim/Heidelberg/
> >>> Ludwigshafen, where I like to spend most of autumn), all of them
> >>> repeat. Is there some vocabulary for "sequence of festivals with a
> >>> common name" (and sometimes common character)?
> >>> In a certain sense, "enjoy-jazz" is a class of its own, the class of
> >>> all festivals with this title/staff etc., but I'm a little bit
> >>> reluctant to spread classes all around like that. And a class
> >>> certainly has no start date, while a row of festivals has. So I'd like
> >>> to model this roughly analogous to spatial containment. But I miss the
> >>> upper category.
> >> Hi Chris,
> >> this is indeed a very good observation. As far as I know, there is
> >> currently no real property or concept to describe your concern. Hence,
> >> we probably need something:
> >> - to describe a tour/ event series of several concerts/shows -> that
> >> means for me currently, e.g. "ex:Tour a event:Event", which consists
> >> then of several sub events
> >> - to describe an annual event -> this can probably also be modelled as
> >> an event:Event, e.g. "ex:AnnualEvent", which has a specific time
> >> interval (similar as these ones of the Days of the Week Ontology) as
> >> object of its event:time property relation
> > The only problem I see with this approach is that the intervals could
> > change. Couldn't we have an abstract class like "iterable event" (I'm
> > sorry, I still think in Python metaphors. ;-) Repeating events, even
> > composite events like a jazz festival, are something so common - art
> > biennales, film festivals, Bayreuth, olympic games. I can't imagine
> > that there's no "mixin" class like that in the world of ontologies.
> Ah sorry, maybe my description was a bit misleading. So I try to
> illustrate this in an example, which is quite similar to the classes
> from the Days of a Week Ontology[1].
> We can have a annual interval or annual instant:
> ex:annual_timeline
> rdf:type tl:TimeLine ;
> dc:description "Starting and ending in between an interval of a
> year."@en ;
> dc:title "Annual Timeline"@en .
> # this property isn't currently a part of the Timeline Ontology
> tl:atMonth
> rdfs:label "at month";
> rdfs:comment "A subproperty of :at, allowing to address a month
> (beginning of it for an instant, all of it for an interval)";
> vs:term_status "stable";
> a owl:DatatypeProperty;
> rdfs:subPropertyOf :at;
> rdfs:range xsd:gMonth .
> I'm currently, unsure whether this is really the best modelling here,
> because the description of an annual festival has uncertain time
> intervals and instants. Nevertheless, I try to model an example with them ;)
> Next question. A festival is a subclass of event:Event, that's fine. > And I can decompose it into sub-events like individual performances. > Now what about the "containment" of a festival in a row of festivals? > We have Montreux, Salzau, Monterey, enjoy-jazz (in Mannheim/Heidelberg/ > Ludwigshafen, where I like to spend most of autumn), all of them > repeat. Is there some vocabulary for "sequence of festivals with a > common name" (and sometimes common character)? > In a certain sense, "enjoy-jazz" is a class of its own, the class of > all festivals with this title/staff etc., but I'm a little bit > reluctant to spread classes all around like that. And a class > certainly has no start date, while a row of festivals has. So I'd like > to model this roughly analogous to spatial containment. But I miss the > upper category.
Yes, we have a similar problem with the BBC Proms, the worldcup, the olympics etc. Right now, what we do is to have an all-encompassing event which represent the festival series. It then has sub events that represent individual occurences (proms 2009, proms 2010, etc.), and those occurences have sub events that represent individual performances. Would that work for you?
> Thanks for any input, > best regards, > Christoph
> -- > You received this message because you are subscribed to the Google Groups "Music Ontology Specification Group" group. > To post to this group, send email to music-ontology-specification-group@googlegroups.com. > To unsubscribe from this group, send email to music-ontology-specification-group+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/music-ontology-specification-group?hl=en.
> > Next question. A festival is a subclass of event:Event, that's fine.
> > And I can decompose it into sub-events like individual performances.
> > Now what about the "containment" of a festival in a row of festivals?
> > We have Montreux, Salzau, Monterey, enjoy-jazz (in Mannheim/Heidelberg/
> > Ludwigshafen, where I like to spend most of autumn), all of them
> > repeat. Is there some vocabulary for "sequence of festivals with a
> > common name" (and sometimes common character)?
> > In a certain sense, "enjoy-jazz" is a class of its own, the class of
> > all festivals with this title/staff etc., but I'm a little bit
> > reluctant to spread classes all around like that. And a class
> > certainly has no start date, while a row of festivals has. So I'd like
> > to model this roughly analogous to spatial containment. But I miss the
> > upper category.
> Yes, we have a similar problem with the BBC Proms, the worldcup, the
> olympics etc. Right now, what we do is to have an all-encompassing
> event which represent the festival series. It then has sub events that
> represent individual occurences (proms 2009, proms 2010, etc.), and
> those occurences have sub events that represent individual
> performances. Would that work for you?
