Michele Pasin / Quotes

Episodes and segments

Episodes usually have a running order. In a news programmes these might be individual new stories, in a music programme the tracks played, in a football programme the matches covered. In PIPs the running order is modelled as a set of segments hanging off an episode version. Because a version can have many segments and a segment can be used in many versions, segments are joined to versions via segment events. Segment objects describe the editorial content of the segment and its duration. Segment events describe where the segment occurs in the version either by position (this is the third segment) or by the offset start time (how many seconds into the version the segment starts). This allows for segment reuse between different versions of the same episode or different versions of different episodes. So a segment of the canonical version of a Top Gear episode might be a review of a Ferrari and that same segment might be reused in the canonical version of the Top Gear Christmas special or might be reused in the canonical version of a clip...

Saved 10 October 2014 / smethur.st ↗

#episodes #program #events #duration #same-episode

Agile does plan for the long term

One of the common misunderstandings of agile is that it avoids any long-term planning in favor of only planning a few weeks out. What agile does not do is…

Gamasutra - Scrum And Long Term Project Planning For Video Games #weeks #sprint #duration #team

A program as an abstract artifact

Consider now a program, constituted by a certain code. Let us observe first that this is not a physical object, as it lacks a location in space. So, in pace…

Towards An Ontology Of Software: A Requirements Engineering Perspective #program #number #hand #types #entities #patterns

A program is constituted by code

Since code and program differ in their essential properties (programs are necessari- ly artifacts and possess essential proper functions; codes are not…

Towards An Ontology Of Software: A Requirements Engineering Perspective #entities #program #ED #relation

A program is not its code, process or algorithm

we agree with Irmak that we cannot identify a program either with a code, a process, or an algorithm. The reason is that this view conflicts with common…

Towards An Ontology Of Software: A Requirements Engineering Perspective #code #algorithm #same-algorithm #program

Code is not necessarily an artifact

In the light of these observations, a code is not necessarily an artifact. If we acci- dentally delete a line of code, the result might still be a computer…

Towards An Ontology Of Software: A Requirements Engineering Perspective #code #artifacts #computer-program #program #computer-code

Digital humanities as a gentrifying small town

To many, the dig­i­tal human­i­ties feels like a small town that has recently been rated as a great place to raise a fam­ily. It is now inun­dated by…

The Digital Humanities Situation | The Transducer #group #events #town #place #resources