[Metadata] Metadata group meeting

classic Classic list List threaded Threaded
6 messages Options
Schulte  Olaf A. Schulte Olaf A.
Reply | Threaded
Open this post in threaded view
|

[Metadata] Metadata group meeting

Dear All

There has been little response from the Metadata group with respect to Bjoern's case around Matterhorn RSS/Atom syndication feeds or the series metadata now proposed for Matterhorn (s. below for details), so my assumption is that you prefer meetings over list discussions. Would you therefore please indicate your availability at

http://doodle.ethz.ch/hzv485yq2rbme5mb

(early morning for US, late afternoon for Europe) for the next meeting?

With respect to the agenda, I see two and a half items:

First, a discussion of the series metadata in general; they are available at

http://opencast.jira.com/wiki/x/IQDf

with points for discussion marked red; feel free to add. In particular (half an item), we are concerned about a set of subtypes we would like to introduce for dcterms:type (item) to describe the various resources DCMI describes as "MovingImage". We would like to get feedback whether that set (Animation, Biography, Discussion, Documentation, Farewell Lecture, Film, Inaugural Lecture, Interview, Lecture Recording, Magazine, Music, News, Speech, Sports, Talk) makes sense to you.

The second item is mapping the metadata to RSS/Atom-like distribution channels. For this, I would hope for someone to help us with a real use case, for the group to discuss whether the existing metadata scheme is adequate to this end. Brandon, we never finished the discussion about the issues you raised (cf. attachments), maybe continuing along those lines would help? Or would Bjoern like to make his case?

Regards

Olaf A.


-----Ursprüngliche Nachricht-----
Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Bjoern Hassler
Gesendet: Dienstag, 16. März 2010 23:39
An: Opencast Matterhorn
Betreff: Re: [Opencast Matterhorn] Matterhorn rss/atom syndication feeds

Hi Adam,

We keep calling it the "Steeple specification", but really it's an
"agreement to use rss/atom/yahoo media in a common way, with minimal
extensions". I guess the "Steeple spec" is:

1. Use atom/rss to bundle feeds together (relying on <atom:link rel="subfeed">)
2. Within feeds, use yahoo media (e.g. <media:content>)
3. Include certain information through use of <media:credit> and
<atom:category> (where Steeple has defined some schemes)
4. Add a minimal number of attributes and elements through Steeple namespace.

Regarding (3), we're including e.g. name of institution/department,
and name of speaker, and recommend <atom:category> for subject
classification.

Regarding (4), the additional attributes I am planning to put forward
for inclusion for the yahoo media standard. There are only two
additional elements (one concerning ids, and one for duration), that
we would also put forward for inclusion for the yahoo media standard.

More info here:
http://www.steeple.org.uk/wiki/Syndication
http://purl.org/steeple

But more than happy to answer by email as well!
Bjoern


On Tue, Mar 16, 2010 at 10:29 PM, Adam Hochman <[hidden email]> wrote:

> Hi Bjoern,
> does steeple have its own unique namespace and schema or are you using a
> "standard" like media rss?
>
> ~Adam
>
> On 3/16/10 1:23 PM, Bjoern Hassler wrote:
>>
>> Hi Josh, hi all,
>>
>> I just wanted to revisit the feeds conversation.
>>
>> I'll be able to supply "patches" to the xml, if that's useful. I won't
>> really be able to look into patching the code itself though :-)
>>
>> How can we take this forward? (Incidentally, who's working on iTunesU
>> integration?)
>>
>> Best,
>> Bjoern
>>
>>
>> On Thu, Feb 11, 2010 at 5:26 PM, Josh Holtzman<[hidden email]>
>>  wrote:
>>
>>>
>>> Thanks Bjoern.  The current RSS and atom feeds looks like the xml below.
>>>  If
>>> you'd like to work on patches to make these more "portal friendly", I'd
>>> be
>>> happy to help.
>>>
>>> Josh
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>>
>>> <rss xmlns:content="http://purl.org/rss/1.0/modules/content/"
>>> xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
>>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
>>>
>>>   <channel>
>>>     <title>Latest episodes</title>
>>>     <link>http://localhost:8080/engage/ui</link>
>>>     <description>Latest episodes on site</description>
>>>
>>>     <item>
>>>       <title>Land and Vegetation: Key players on the Climate
>>> Scene</title>
>>>
>>>
>>> <link>http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-404b-b1fa-3a54b73a4cbc</link>
>>>
>>>       <content:encoded>&lt;div
>>> xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;img
>>>
>>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-3a54b73a4cbc/attachments/attachment-1.jpg"
>>> /&gt;&lt;/div&gt;</content:encoded>
>>>
>>>       <guid
>>> isPermaLink="false">49c1ab86-088a-404b-b1fa-3a54b73a4cbc</guid>
>>>       <itunes:duration>00:00:00</itunes:duration>
>>>       <itunes:author>test</itunes:author>
>>>
>>>       <itunes:explicit>no</itunes:explicit>
>>>       <itunes:keywords />
>>>       <dc:title>Land and Vegetation: Key players on the Climate
>>> Scene</dc:title>
>>>       <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
>>>
>>>       <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
>>>     </item>
>>>   </channel>
>>>
>>> </rss>
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>>
>>> <feed xmlns="http://purl.org/atom/ns#"
>>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="0.3">
>>>
>>>   <title mode="escaped">Latest episodes</title>
>>>   <link rel="alternate" href="http://localhost:8080/engage/ui" />
>>>   <tagline>Latest episodes on site</tagline>
>>>
>>>   <id>latest</id>
>>>   <entry>
>>>     <title mode="escaped">Land and Vegetation: Key players on the Climate
>>> Scene</title>
>>>     <link
>>>
>>> href="http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-404b-b1fa-3a54b73a4cbc"
>>> />
>>>
>>>     <author>
>>>       <name />
>>>     </author>
>>>     <id>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</id>
>>>     <content type="application/xhtml+xml" mode="xml">
>>>       <div xmlns="http://www.w3.org/1999/xhtml">
>>>
>>>         <img
>>>
>>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-3a54b73a4cbc/attachments/attachment-1.jpg"
>>> />
>>>
>>>       </div>
>>>     </content>
>>>     <dc:title>Land and Vegetation: Key players on the Climate
>>> Scene</dc:title>
>>>     <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
>>>     <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
>>>
>>>   </entry>
>>>
>>> </feed>
>>>
>>>
>>>
>>> On Thu, Feb 11, 2010 at 7:07 AM, Bjoern Hassler<[hidden email]>
>>> wrote:
>>>
>>>>
>>>> Hi all,
>>>>
>>>> well done on Matterhorn 0.5!
>>>>
>>>> Would it be worth looking at the rss feeds generated by Matterhorn, to
>>>> see
>>>> whether there's scope for making these compliant with the Steeple
>>>> rss/atom
>>>> recommendations?
>>>>
>>>> I should think that the PCF's Miro Communities and the Spanish REDIRIS
>>>> Arca project would be interested in talking about the feeds too, to see
>>>> how
>>>> they could be used in their projects. Tweaking the feeds could be quite
>>>> useful in a number of ways, for instance Matterhorn would then work
>>>> nicely
>>>> with the various portal softwares around (including the Steeple portal).
>>>>
>>>> How should we take this forward?
>>>>
>>>> Cheers,
>>>> Bjoern
>>>> _______________________________________________
>>>> Matterhorn mailing list
>>>> [hidden email]
>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>
>>>>
>>>> To unsubscribe please email
>>>> [hidden email]
>>>> _______________________________________________
>>>>
>>>
>>> _______________________________________________
>>> Matterhorn mailing list
>>> [hidden email]
>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>
>>>
>>> To unsubscribe please email
>>> [hidden email]
>>> _______________________________________________
>>>
>>>
>>
>> _______________________________________________
>> Matterhorn mailing list
>> [hidden email]
>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>
>>
>> To unsubscribe please email
>> [hidden email]
>> _______________________________________________
>>
>>
>
> _______________________________________________
> Matterhorn mailing list
> [hidden email]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>
>
> To unsubscribe please email
> [hidden email]
> _______________________________________________
>
_______________________________________________
Matterhorn mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[hidden email]
_______________________________________________

Dear Brandon



I think some of your questions touch on the issues we currently deal with and will be discussed in the meeting today, but let me comment upon some of the points you make.



Matterhorn 0.5 – Matterhorn 1.0

The metadata scheme at



http://opencast.jira.com/wiki/display/MH/Matterhorn+metadata+scheme



originates from ETH Zurich’s REPLAY scheme and is supposed to become the Opencast Matterhorn metadata scheme for Matterhorn 1.0; as an alpha release, 0.5 only features very rudimental implementations of the metadata scheme, especially with respect to the UI design.

As other institutions have different needs compared to ETH, the metadata scheme is subject to ongoing discussions (cf. http://opencast.jira.com/browse/MH-1279 and my recent e-mail to this list) to satisfy the requirements from various institutions; so please consider it under review for now.



Abstract, keywords

More to your point: dcterms:abstract was used in the REPLAY scheme, but – subject to the discussion we are having on my recent e-mail – will not feature in the Opencast scheme; instead, we will use dcterms:description for both item and series. As for “keywords” (tags?) I would like to see some discussion around this as I could imagine this to be mapped to either dcterms:description (item?) or dcterms:subject (item?). Is there such a thing as dcterms:keywords?



Technical metadata

Finally, this scheme is being completed by a set of more technical metadata which Matterhorn can – in most cases – automatically extract from the tracks, such as duration, resolution, frame rate, ratio etc. Would these be the ones you expect?



See you later



Olaf A.







Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Brandon Muramatsu
Gesendet: Dienstag, 2. März 2010 13:28
An: [hidden email]
Betreff: [Metadata] Questions regarding Matterhorn Metadata



Hi all,

A colleague and I are planning on participating in the metadata meeting in a few hours. I followed a bit of the discussions last spring and summer but was unfortunately not able to engage to any significant extent. Now, my project is grappling with the need to define the metadata we collect, and define how we expose that metadata to a couple services we are developing, and then express that metadata externally for a number of uses.

I have no desire to create yet another spec. (Though if you're interested the last metadata spec I wrote for implementing in a system is available online [1].)

I should mention I haven't had time to play directly with v0.5, but am working under the assumption that I should be able to determine what's going on by looking in the documentation on the wiki and Jira [1].

However, I can't figure out what Matterhorn is doing with metadata from the public Matterhorn documents in Jira and the wiki. I did not go digging through the service definitions.

Specific Questions:

- Is the specification expressed at [2], the one implemented in v0.5?

- If [2] is implemented, how is the metadata mapped to an RSS feed?
---  A quick look at [3] shows that there's a mismatch in labels for fields. For example, if abstract is different than description in [3], then what is the best practice for feed.description?
--- The metadata schema does not appear to allow for tags--they could be encoded in dc.subject, but there does not appear provision for dc.keywords (which is where I would put them) and hence how does one populate feed.rsstags?

- The metadata schema does not appear to include any of what might be described as the technical metadata of the resource, such as the video dimensions, duration, codec, etc. Is this part of the schema? Is this decision documented somewhere that I didn't locate? Or are users expected to extract that themselves from directly from the media (for example, are the Matterhorn services extracting this from the media if they need it, I think the basic example is duration for use in say in captioning)?

- What are Matterhorn's plans for exposing or exchanging metadata outside the system? Only through RSS? Or for example, is there an XML specification for encoding Matterhorn metadata? (If there is I would have thought my searches for metadata would have found it.) Or was this out of scope for the work so far?

- What metadata is being encoded in the video files themselves? For example, are title and creators encoded with the video file?


Thanks.

Brandon Muramatsu
MIT

[1] http://educommons.com/documentation/manual/metadata-and-import-export/metadata-specifications-for-ocw-repositories
[2] http://opencast.jira.com/secure/StudioSearch.jspa?suggest-tracking=search&quickSearch=true&query=metadata
[3] http://opencast.jira.com/wiki/display/MH/Matterhorn+metadata+scheme
[4] http://opencast.jira.com/wiki/display/MH/Atom+and+RSS+Feeds


Dear All



Let me chime in late here by trying to comment upon the various issues I see; let me know if I miss a point or several points.



1. Lacking metadata fields, e.g. lecture series number or local ID

The reason a reference to the lecture (series) number cannot be found explicitly in the metadata scheme is the fact that these references are of local importance mainly. This is not to disregard this use, but the scheme was envisioned to cater for an inter-institutional exchange, where local information wouldn't be of primary importance. However, dcterms:description is certainly not the place for this (s. below); dcterms:identifier could be ("An unambiguous reference to the resource within a given context") - s. below for customized metadata.



2. Lacking metadata fields for specific distribution purposes (iTunes)

Unfortunately, I'm not familiar with the specific needs of iTunes or iTunes U and I would like to point to the efforts Bjoern is undertaking to feed distribution channels from the Opencast Core metadata scheme. I would make this the next agenda item for the metadata group, if someone (Brandon? Andy?) could specify what information was needed. We could then map this to the information contained in the metadata scheme; if there is no equivalent, we would either have to enhance the Opencast Core scheme (if this information can be expressed using a Dublin Core elements, cf. http://dublincore.org/documents/dces/ and http://dublincore.org/documents/usageguide/qualifiers.shtml) or add customized metadata fields for distribution purposes. Remember, the Opencast Core scheme is not the only metadata we can convey (there are the technical metadata for one), but we cannot carry everything with this scheme. If iTunes is asking for TV-like metadata, I'm not sure we can bend the scheme for this, but, in Brandon's case "Show" could be dcterms:title (series), Episode ID could be dcterms:identifier (item), Season could be dcterms:created (series), Episode could be dcterms:title (item), and TV Network could be dcterms:publisher (series).



3. Vocabulary / recommended use

Please don't consider the metadata elements arbitrary with respect to the information they contain and the way this information is entered. If we say dcterms:created was to meet "W3C-DTF profile of ISO 8601" or dcterms:extent should describe the size or duration of the resource according to ISO8601, then you shouldn't enter a date in a different format or a size in whatever form you think is adequate. Likewise, dcterms:description cannot be used to convey a lecture (series) number if a description of the resource is expected.



4. Time and place

dcterms:created (item) describes the point in time of a resource being created, dcterms:created (series) can describe a point in time or a period of time (duration of a conference, semester etc.).

dcterms:spatial describes the place/location; we can discuss whether item and series metadata allow for different vocabulary (GeoNames, city, country, room etc.).



5. Sorting

This is indeed a problem we still have, especially in the context of what Brandon describes: If you want to break the given (chronological) order we have as a consequence of dcterms:created, there is no metadata element to guide this new order. Our library colleague tells us that this sorting is "arbitrary" and should therefore not be featured in the metadata but in the distributive end. Is this an option in the context of your scenario, Brandon?



Regards



Olaf A.



Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Judy Stern
Gesendet: Donnerstag, 25. März 2010 01:04
An: Opencast Matterhorn
Cc: [hidden email]
Betreff: Re: [Opencast Matterhorn] continuation of "metadata in UIs" conversation started at PO meeting today



On Mar 24, 2010, at 4:27 PM, Brandon Muramatsu wrote:

Matterhorn is missing metadata elements, probably a lot of them if you want to express most of the Matterhorn metadata in xml or the like, and you're missing a clear mapping from elements within Matterhorn interfaces/database/whatever to an external representation.



Okay (and I'm saying this to all, not just Brandon): so we need to get clear on what it is that we're missing! From what Brandon is saying, we may not be safe even if  we incorporated many more DC-mapped fields (e.g. I'm thinking about all the Replay provides access to). Other opinions? (Input from the metadata group would be great here, though I understand if you're waiting for Olaf to return.)



One more wiki page that is relevant to this discussion: http://opencast.jira.com/wiki/display/MH/Metadata+mapping+in+the+UIs



Judy







On Mar 24, 2010, at 4:27 PM, Brandon Muramatsu wrote:

Replies inline below.

On Wed, Mar 24, 2010 at 6:59 PM, Judy Stern <[hidden email]<mailto:[hidden email]>> wrote:

Good question, Brandon!

Hopefully others will respond, too, but here's my take:

At first glance it does seem like we're missing a "lecture number" (or equivalent for non-academic term) field, but given that we're only working with the concept of individual lectures at the moment, I could say "we'll get to that when we firm up our concept of 'series'". When we do get to series, I wonder if the system can have an underlying notion of lecture number (calculated logically according to creation date, e.g.) that's not exposed to the Matterhorn admin user but is passed to any distribution channels that need it. Or perhaps we just need to add that as an explicit field (but then I worry about the UI necessary to re-order....not impossible but probably not going to be done for 1.0).


FWIW, I'd say you could autopopulate initial values based on creation date, but that you'd probably want the flexibility of setting the order independently of creation date. Think a TV show that produces shows in an order A, B, C but airs them in the order A, C, B. In some cases, the "official" ordering is A, C, B.


btw, when you say "Track", I'm interpreting it as "Track #", as seen in iTunes. (In terms of the QT architecture, Apple uses the term "Track" to refer to the different elements that compose a movie, e.g. "sound track", "video track", "text track", "chapter track" and lots more that most people don't know about :-)  Interestingly, I can't find "Track #" metadata inside files downloaded from iTunes U (that clearly have track #'s in iTunes), at least not looking at the file's metadata ("annotations") via QT Player. Are you sure that this particular piece of metadata is embedded in the file?



Well, it's possible I'm track is just a CD (maybe? redbook or the like) metadata/descriptor element, and that is not how QuickTime is reading in that information. Aka the data is stored one way and has a human label, and an internal label.

The relevant video/tv show info would be Show, Episode ID, Season, Episode, and TV Network. Which iTunes reads in and uses (I'm pretty sure based on trial and error) for display. If you have a TV show purchased/downloaded through iTunes the data's in there, though I can't find a way of exposing this metadata in either iTunes or QuickTime. I've been using a program MetaX (http://www.kerstetter.net/index.php/projects/software/metax) to view and set the metadata. I mucked around with these fields to figure out what I'd need to do to get things ordered properly in iTunes.


I doubt that we want to use dcterms: description to store this metadata, but would defer to the metadata group on this one. Is there any other reasonable dublin core choice for this?


No, there is not really a Dublin Core element for this -- my example was a roundabout way of saying, Matterhorn is missing metadata elements, probably a lot of them if you want to express most of the Matterhorn metadata in xml or the like, and you're missing a clear mapping from elements within Matterhorn interfaces/database/whatever to an external representation.

Brandon




On Mar 24, 2010, at 1:57 PM, Brandon Muramatsu wrote:





Judy, quick reply...

What I can't figure out from this list, for example, is how do I view or express in the UI or export as metadata the label corresponding to the iTunes/QuickTime notion of Track? Or perhaps put in a different set of terminology, but referring to the same concept, how do I express the lecture number in a group of lectures?

This is metadata that can be embedded in a QuickTime file, for example. And is metadata that I know Matterhorn is interested in.

But I don't see a way of expressing it in metadata, and certainly not a way that's unique.

I could for example use a dcterms:description field for the value of the lecture number. It's not completely unreasonable to express the information this way. But as displayed on the wiki page, how is that dcterms:description, say different from the dcterms:description that contains the text summary of the contents of the video as a whole?

Also I think there's an underlying problem with the definition of metadata elements stored inside the "system", how that metadata is expressed in UIs, and how that metadata is expressed to the world at large.

(I think my example, to be fair I haven't fully thought through all the implications, exposes issues with the last two issues I identify above.)


Brandon

On Wed, Mar 24, 2010 at 3:53 PM, Judy Stern <[hidden email]<mailto:[hidden email]>> wrote:

At the Product Owner meeting this morning, there was concern expressed that the current UIs don't expose the agreed upon set of metadata.



In the UI's we currently have the full set of "exposed" metadata listed at: http://opencast.jira.com/wiki/display/MH/Matterhorn+metadata+scheme+%28work+in+progress%29 (please note that in the UI's some of this metadata needs to be "disclosed", due to form length considerations, but we still consider it "exposed"). This page is labeled a "work in progress" but I am quite sure it is the closest thing we have to "agree upon".



In addition, it is planned that configurers will be able to make changes to the default UI's as follows:

*       MH-1250 As a configurer, I need to specify which metadata should be exposed to the administrator.
*       MH-1251 As a configurer, I need to specify which metadata is required for the administrator to enter.
*       MH-1252 As a configurer, I need to specify which exposed metadata has secondary importance, so the the admin is not inundated with lower priority fields.
*       MH-2645 As a configurer I need to specify labels for metadata fields that administrators at my institution will understand



If anybody feels that their metadata needs will not be met, considering the above, please respond to this thread. I am not a metadata expert, nor have we done the user research/business analysis I would have like to better understand requirements around this, so I will be grateful for any input. (Let's assume, for the moment, that series metadata is another topic. This was not discussed in Zurich nor has it been documented, as were the items on the wiki page referenced above but Olaf has contributed a great deal to the conversation in <http://opencast.jira.com/browse/MH-1279>.)



A question has recently arisen as to whether we should also expose, in the default upload UI, "Location" and "Creation date" (my guess is that these map to dcterms:created and dcterms:spatial, though I'm less sure about the latter); they are not in the current "exposed" list.  Creation date and location are gathered during scheduling, btw, though not as metadata, afaik. Any opinions about whether location and creation date are important metadata fields?



thanks in advance for your input,

Judy



Judy Stern

Educational Technology Services, UC Berkeley

[hidden email]<mailto:[hidden email]>

_______________________________________________
Matterhorn mailing list
[hidden email]<mailto:[hidden email]>
http://lists.opencastproject.org/mailman/listinfo/matterhorn


To unsubscribe please email
[hidden email]
_______________________________________________



Judy Stern

Educational Technology Services, UC Berkeley

[hidden email]<mailto:[hidden email]>








_______________________________________________
Metadata mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/metadata

ATT00001..txt (222 bytes) Download Attachment
Schulte  Olaf A. Schulte Olaf A.
Reply | Threaded
Open this post in threaded view
|

Re: [Metadata] Metadata group meeting

Hello

No (!) response with respect to the date for the next meeting nor to the issues at hand. Please consider this a friendly reminder that your input is very welcome.

Regards

Olaf A.

> -----Ursprüngliche Nachricht-----
> Von: Schulte Olaf A.
> Gesendet: Dienstag, 13. April 2010 23:51
> An: [hidden email]
> Cc: [hidden email]
> Betreff: Metadata group meeting
>
> Dear All
>
> There has been little response from the Metadata group with respect to Bjoern's
> case around Matterhorn RSS/Atom syndication feeds or the series metadata now
> proposed for Matterhorn (s. below for details), so my assumption is that you
> prefer meetings over list discussions. Would you therefore please indicate your
> availability at
>
> http://doodle.ethz.ch/hzv485yq2rbme5mb
>
> (early morning for US, late afternoon for Europe) for the next meeting?
>
> With respect to the agenda, I see two and a half items:
>
> First, a discussion of the series metadata in general; they are available at
>
> http://opencast.jira.com/wiki/x/IQDf
>
> with points for discussion marked red; feel free to add. In particular (half an item),
> we are concerned about a set of subtypes we would like to introduce for
> dcterms:type (item) to describe the various resources DCMI describes as
> "MovingImage". We would like to get feedback whether that set (Animation,
> Biography, Discussion, Documentation, Farewell Lecture, Film, Inaugural Lecture,
> Interview, Lecture Recording, Magazine, Music, News, Speech, Sports, Talk) makes
> sense to you.
>
> The second item is mapping the metadata to RSS/Atom-like distribution channels.
> For this, I would hope for someone to help us with a real use case, for the group
> to discuss whether the existing metadata scheme is adequate to this end.
> Brandon, we never finished the discussion about the issues you raised (cf.
> attachments), maybe continuing along those lines would help? Or would Bjoern like
> to make his case?
>
> Regards
>
> Olaf A.
>
>
> -----Ursprüngliche Nachricht-----
> Von: [hidden email] [mailto:matterhorn-
> [hidden email]] Im Auftrag von Bjoern Hassler
> Gesendet: Dienstag, 16. März 2010 23:39
> An: Opencast Matterhorn
> Betreff: Re: [Opencast Matterhorn] Matterhorn rss/atom syndication feeds
>
> Hi Adam,
>
> We keep calling it the "Steeple specification", but really it's an "agreement to use
> rss/atom/yahoo media in a common way, with minimal extensions". I guess the
> "Steeple spec" is:
>
> 1. Use atom/rss to bundle feeds together (relying on <atom:link rel="subfeed">) 2.
> Within feeds, use yahoo media (e.g. <media:content>) 3. Include certain
> information through use of <media:credit> and <atom:category> (where Steeple
> has defined some schemes) 4. Add a minimal number of attributes and elements
> through Steeple namespace.
>
> Regarding (3), we're including e.g. name of institution/department, and name of
> speaker, and recommend <atom:category> for subject classification.
>
> Regarding (4), the additional attributes I am planning to put forward for inclusion
> for the yahoo media standard. There are only two additional elements (one
> concerning ids, and one for duration), that we would also put forward for inclusion
> for the yahoo media standard.
>
> More info here:
> http://www.steeple.org.uk/wiki/Syndication
> http://purl.org/steeple
>
> But more than happy to answer by email as well!
> Bjoern
>
>
> On Tue, Mar 16, 2010 at 10:29 PM, Adam Hochman <[hidden email]>
> wrote:
> > Hi Bjoern,
> > does steeple have its own unique namespace and schema or are you using
> > a "standard" like media rss?
> >
> > ~Adam
> >
> > On 3/16/10 1:23 PM, Bjoern Hassler wrote:
> >>
> >> Hi Josh, hi all,
> >>
> >> I just wanted to revisit the feeds conversation.
> >>
> >> I'll be able to supply "patches" to the xml, if that's useful. I
> >> won't really be able to look into patching the code itself though :-)
> >>
> >> How can we take this forward? (Incidentally, who's working on iTunesU
> >> integration?)
> >>
> >> Best,
> >> Bjoern
> >>
> >>
> >> On Thu, Feb 11, 2010 at 5:26 PM, Josh
> >> Holtzman<[hidden email]>
> >>  wrote:
> >>
> >>>
> >>> Thanks Bjoern.  The current RSS and atom feeds looks like the xml below.
> >>>  If
> >>> you'd like to work on patches to make these more "portal friendly",
> >>> I'd be happy to help.
> >>>
> >>> Josh
> >>>
> >>> <?xml version="1.0" encoding="UTF-8"?>
> >>>
> >>> <rss xmlns:content="http://purl.org/rss/1.0/modules/content/"
> >>> xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
> >>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
> >>>
> >>>   <channel>
> >>>     <title>Latest episodes</title>
> >>>     <link>http://localhost:8080/engage/ui</link>
> >>>     <description>Latest episodes on site</description>
> >>>
> >>>     <item>
> >>>       <title>Land and Vegetation: Key players on the Climate
> >>> Scene</title>
> >>>
> >>>
> >>> <link>http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-40
> >>> 4b-b1fa-3a54b73a4cbc</link>
> >>>
> >>>       <content:encoded>&lt;div
> >>> xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;img
> >>>
> >>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-
> 3a54b73a4cbc/attachments/attachment-1.jpg"
> >>> /&gt;&lt;/div&gt;</content:encoded>
> >>>
> >>>       <guid
> >>> isPermaLink="false">49c1ab86-088a-404b-b1fa-3a54b73a4cbc</guid>
> >>>       <itunes:duration>00:00:00</itunes:duration>
> >>>       <itunes:author>test</itunes:author>
> >>>
> >>>       <itunes:explicit>no</itunes:explicit>
> >>>       <itunes:keywords />
> >>>       <dc:title>Land and Vegetation: Key players on the Climate
> >>> Scene</dc:title>
> >>>       <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
> >>>
> >>>
> >>> <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
> >>>     </item>
> >>>   </channel>
> >>>
> >>> </rss>
> >>>
> >>> <?xml version="1.0" encoding="UTF-8"?>
> >>>
> >>> <feed xmlns="http://purl.org/atom/ns#"
> >>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="0.3">
> >>>
> >>>   <title mode="escaped">Latest episodes</title>
> >>>   <link rel="alternate" href="http://localhost:8080/engage/ui" />
> >>>   <tagline>Latest episodes on site</tagline>
> >>>
> >>>   <id>latest</id>
> >>>   <entry>
> >>>     <title mode="escaped">Land and Vegetation: Key players on the
> >>> Climate Scene</title>
> >>>     <link
> >>>
> >>> href="http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-404b-
> b1fa-3a54b73a4cbc"
> >>> />
> >>>
> >>>     <author>
> >>>       <name />
> >>>     </author>
> >>>     <id>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</id>
> >>>     <content type="application/xhtml+xml" mode="xml">
> >>>       <div xmlns="http://www.w3.org/1999/xhtml">
> >>>
> >>>         <img
> >>>
> >>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-
> 3a54b73a4cbc/attachments/attachment-1.jpg"
> >>> />
> >>>
> >>>       </div>
> >>>     </content>
> >>>     <dc:title>Land and Vegetation: Key players on the Climate
> >>> Scene</dc:title>
> >>>     <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
> >>>
> >>> <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
> >>>
> >>>   </entry>
> >>>
> >>> </feed>
> >>>
> >>>
> >>>
> >>> On Thu, Feb 11, 2010 at 7:07 AM, Bjoern
> >>> Hassler<[hidden email]>
> >>> wrote:
> >>>
> >>>>
> >>>> Hi all,
> >>>>
> >>>> well done on Matterhorn 0.5!
> >>>>
> >>>> Would it be worth looking at the rss feeds generated by Matterhorn,
> >>>> to see whether there's scope for making these compliant with the
> >>>> Steeple rss/atom recommendations?
> >>>>
> >>>> I should think that the PCF's Miro Communities and the Spanish
> >>>> REDIRIS Arca project would be interested in talking about the feeds
> >>>> too, to see how they could be used in their projects. Tweaking the
> >>>> feeds could be quite useful in a number of ways, for instance
> >>>> Matterhorn would then work nicely with the various portal softwares
> >>>> around (including the Steeple portal).
> >>>>
> >>>> How should we take this forward?
> >>>>
> >>>> Cheers,
> >>>> Bjoern
> >>>> _______________________________________________
> >>>> Matterhorn mailing list
> >>>> [hidden email]
> >>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >>>>
> >>>>
> >>>> To unsubscribe please email
> >>>> [hidden email]
> >>>> _______________________________________________
> >>>>
> >>>
> >>> _______________________________________________
> >>> Matterhorn mailing list
> >>> [hidden email]
> >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >>>
> >>>
> >>> To unsubscribe please email
> >>> [hidden email]
> >>> _______________________________________________
> >>>
> >>>
> >>
> >> _______________________________________________
> >> Matterhorn mailing list
> >> [hidden email]
> >> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >>
> >>
> >> To unsubscribe please email
> >> [hidden email]
> >> _______________________________________________
> >>
> >>
> >
> > _______________________________________________
> > Matterhorn mailing list
> > [hidden email]
> > http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >
> >
> > To unsubscribe please email
> > [hidden email]
> > _______________________________________________
> >
> _______________________________________________
> Matterhorn mailing list
> [hidden email]
> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>
>
> To unsubscribe please email
> [hidden email]
> _______________________________________________
_______________________________________________
Metadata mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/metadata
Bjoern Hassler-3 Bjoern Hassler-3
Reply | Threaded
Open this post in threaded view
|

Re: [Metadata] Metadata group meeting

Hi all,

we should take this forward. I've jsut entered times on the doodle.

Generally mornings are ok for me. Unfortunately I can't do afternoons for the time being, due to other work commitments.

(I'm in Zambia.)

Bjoern

On 20 Apr 2010, at 17:12, Schulte Olaf A. wrote:

> Hello
>
> No (!) response with respect to the date for the next meeting nor to the issues at hand. Please consider this a friendly reminder that your input is very welcome.
>
> Regards
>
> Olaf A.
>
>> -----Ursprüngliche Nachricht-----
>> Von: Schulte Olaf A.
>> Gesendet: Dienstag, 13. April 2010 23:51
>> An: [hidden email]
>> Cc: [hidden email]
>> Betreff: Metadata group meeting
>>
>> Dear All
>>
>> There has been little response from the Metadata group with respect to Bjoern's
>> case around Matterhorn RSS/Atom syndication feeds or the series metadata now
>> proposed for Matterhorn (s. below for details), so my assumption is that you
>> prefer meetings over list discussions. Would you therefore please indicate your
>> availability at
>>
>> http://doodle.ethz.ch/hzv485yq2rbme5mb
>>
>> (early morning for US, late afternoon for Europe) for the next meeting?
>>
>> With respect to the agenda, I see two and a half items:
>>
>> First, a discussion of the series metadata in general; they are available at
>>
>> http://opencast.jira.com/wiki/x/IQDf
>>
>> with points for discussion marked red; feel free to add. In particular (half an item),
>> we are concerned about a set of subtypes we would like to introduce for
>> dcterms:type (item) to describe the various resources DCMI describes as
>> "MovingImage". We would like to get feedback whether that set (Animation,
>> Biography, Discussion, Documentation, Farewell Lecture, Film, Inaugural Lecture,
>> Interview, Lecture Recording, Magazine, Music, News, Speech, Sports, Talk) makes
>> sense to you.
>>
>> The second item is mapping the metadata to RSS/Atom-like distribution channels.
>> For this, I would hope for someone to help us with a real use case, for the group
>> to discuss whether the existing metadata scheme is adequate to this end.
>> Brandon, we never finished the discussion about the issues you raised (cf.
>> attachments), maybe continuing along those lines would help? Or would Bjoern like
>> to make his case?
>>
>> Regards
>>
>> Olaf A.
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: [hidden email] [mailto:matterhorn-
>> [hidden email]] Im Auftrag von Bjoern Hassler
>> Gesendet: Dienstag, 16. März 2010 23:39
>> An: Opencast Matterhorn
>> Betreff: Re: [Opencast Matterhorn] Matterhorn rss/atom syndication feeds
>>
>> Hi Adam,
>>
>> We keep calling it the "Steeple specification", but really it's an "agreement to use
>> rss/atom/yahoo media in a common way, with minimal extensions". I guess the
>> "Steeple spec" is:
>>
>> 1. Use atom/rss to bundle feeds together (relying on <atom:link rel="subfeed">) 2.
>> Within feeds, use yahoo media (e.g. <media:content>) 3. Include certain
>> information through use of <media:credit> and <atom:category> (where Steeple
>> has defined some schemes) 4. Add a minimal number of attributes and elements
>> through Steeple namespace.
>>
>> Regarding (3), we're including e.g. name of institution/department, and name of
>> speaker, and recommend <atom:category> for subject classification.
>>
>> Regarding (4), the additional attributes I am planning to put forward for inclusion
>> for the yahoo media standard. There are only two additional elements (one
>> concerning ids, and one for duration), that we would also put forward for inclusion
>> for the yahoo media standard.
>>
>> More info here:
>> http://www.steeple.org.uk/wiki/Syndication
>> http://purl.org/steeple
>>
>> But more than happy to answer by email as well!
>> Bjoern
>>
>>
>> On Tue, Mar 16, 2010 at 10:29 PM, Adam Hochman <[hidden email]>
>> wrote:
>>> Hi Bjoern,
>>> does steeple have its own unique namespace and schema or are you using
>>> a "standard" like media rss?
>>>
>>> ~Adam
>>>
>>> On 3/16/10 1:23 PM, Bjoern Hassler wrote:
>>>>
>>>> Hi Josh, hi all,
>>>>
>>>> I just wanted to revisit the feeds conversation.
>>>>
>>>> I'll be able to supply "patches" to the xml, if that's useful. I
>>>> won't really be able to look into patching the code itself though :-)
>>>>
>>>> How can we take this forward? (Incidentally, who's working on iTunesU
>>>> integration?)
>>>>
>>>> Best,
>>>> Bjoern
>>>>
>>>>
>>>> On Thu, Feb 11, 2010 at 5:26 PM, Josh
>>>> Holtzman<[hidden email]>
>>>>  wrote:
>>>>
>>>>>
>>>>> Thanks Bjoern.  The current RSS and atom feeds looks like the xml below.
>>>>>  If
>>>>> you'd like to work on patches to make these more "portal friendly",
>>>>> I'd be happy to help.
>>>>>
>>>>> Josh
>>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>
>>>>> <rss xmlns:content="http://purl.org/rss/1.0/modules/content/"
>>>>> xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
>>>>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
>>>>>
>>>>>   <channel>
>>>>>     <title>Latest episodes</title>
>>>>>     <link>http://localhost:8080/engage/ui</link>
>>>>>     <description>Latest episodes on site</description>
>>>>>
>>>>>     <item>
>>>>>       <title>Land and Vegetation: Key players on the Climate
>>>>> Scene</title>
>>>>>
>>>>>
>>>>> <link>http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-40
>>>>> 4b-b1fa-3a54b73a4cbc</link>
>>>>>
>>>>>       <content:encoded>&lt;div
>>>>> xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;img
>>>>>
>>>>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-
>> 3a54b73a4cbc/attachments/attachment-1.jpg"
>>>>> /&gt;&lt;/div&gt;</content:encoded>
>>>>>
>>>>>       <guid
>>>>> isPermaLink="false">49c1ab86-088a-404b-b1fa-3a54b73a4cbc</guid>
>>>>>       <itunes:duration>00:00:00</itunes:duration>
>>>>>       <itunes:author>test</itunes:author>
>>>>>
>>>>>       <itunes:explicit>no</itunes:explicit>
>>>>>       <itunes:keywords />
>>>>>       <dc:title>Land and Vegetation: Key players on the Climate
>>>>> Scene</dc:title>
>>>>>       <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
>>>>>
>>>>>
>>>>> <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
>>>>>     </item>
>>>>>   </channel>
>>>>>
>>>>> </rss>
>>>>>
>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>
>>>>> <feed xmlns="http://purl.org/atom/ns#"
>>>>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="0.3">
>>>>>
>>>>>   <title mode="escaped">Latest episodes</title>
>>>>>   <link rel="alternate" href="http://localhost:8080/engage/ui" />
>>>>>   <tagline>Latest episodes on site</tagline>
>>>>>
>>>>>   <id>latest</id>
>>>>>   <entry>
>>>>>     <title mode="escaped">Land and Vegetation: Key players on the
>>>>> Climate Scene</title>
>>>>>     <link
>>>>>
>>>>> href="http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-404b-
>> b1fa-3a54b73a4cbc"
>>>>> />
>>>>>
>>>>>     <author>
>>>>>       <name />
>>>>>     </author>
>>>>>     <id>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</id>
>>>>>     <content type="application/xhtml+xml" mode="xml">
>>>>>       <div xmlns="http://www.w3.org/1999/xhtml">
>>>>>
>>>>>         <img
>>>>>
>>>>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-
>> 3a54b73a4cbc/attachments/attachment-1.jpg"
>>>>> />
>>>>>
>>>>>       </div>
>>>>>     </content>
>>>>>     <dc:title>Land and Vegetation: Key players on the Climate
>>>>> Scene</dc:title>
>>>>>     <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
>>>>>
>>>>> <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
>>>>>
>>>>>   </entry>
>>>>>
>>>>> </feed>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 11, 2010 at 7:07 AM, Bjoern
>>>>> Hassler<[hidden email]>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> well done on Matterhorn 0.5!
>>>>>>
>>>>>> Would it be worth looking at the rss feeds generated by Matterhorn,
>>>>>> to see whether there's scope for making these compliant with the
>>>>>> Steeple rss/atom recommendations?
>>>>>>
>>>>>> I should think that the PCF's Miro Communities and the Spanish
>>>>>> REDIRIS Arca project would be interested in talking about the feeds
>>>>>> too, to see how they could be used in their projects. Tweaking the
>>>>>> feeds could be quite useful in a number of ways, for instance
>>>>>> Matterhorn would then work nicely with the various portal softwares
>>>>>> around (including the Steeple portal).
>>>>>>
>>>>>> How should we take this forward?
>>>>>>
>>>>>> Cheers,
>>>>>> Bjoern
>>>>>> _______________________________________________
>>>>>> Matterhorn mailing list
>>>>>> [hidden email]
>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>>>
>>>>>>
>>>>>> To unsubscribe please email
>>>>>> [hidden email]
>>>>>> _______________________________________________
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Matterhorn mailing list
>>>>> [hidden email]
>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>>
>>>>>
>>>>> To unsubscribe please email
>>>>> [hidden email]
>>>>> _______________________________________________
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Matterhorn mailing list
>>>> [hidden email]
>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>
>>>>
>>>> To unsubscribe please email
>>>> [hidden email]
>>>> _______________________________________________
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Matterhorn mailing list
>>> [hidden email]
>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>
>>>
>>> To unsubscribe please email
>>> [hidden email]
>>> _______________________________________________
>>>
>> _______________________________________________
>> Matterhorn mailing list
>> [hidden email]
>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>
>>
>> To unsubscribe please email
>> [hidden email]
>> _______________________________________________
> _______________________________________________
> Metadata mailing list
> [hidden email]
> http://lists.opencastproject.org/mailman/listinfo/metadata

--
Dr Bjoern Hassler
Centre for Applied Research in Educational Technologies &
Centre for Commonwealth Education,
University of Cambridge, UK
Email: [hidden email]

Aptivate | (http://www.aptivate.org)
The Humanitarian Centre, Fenner's, Gresham Road, Cambridge CB1 2ES
Email: [hidden email]

Mobile (UK): +44-7952-888939
Mobile (Zambia): +26-0978-717308
Web: http://www.sciencemedianetwork.org



_______________________________________________
Metadata mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/metadata
Schulte  Olaf A. Schulte Olaf A.
Reply | Threaded
Open this post in threaded view
|

Re: [Metadata] Metadata group meeting

Hello Bjoern

Your morning makes this pretty difficult for North America...

Regards

Olaf A.

> -----Ursprüngliche Nachricht-----
> Von: Bjoern Hassler [mailto:[hidden email]]
> Gesendet: Dienstag, 20. April 2010 17:28
> An: Schulte Olaf A.
> Cc: '[hidden email]'
> Betreff: Re: [Metadata] Metadata group meeting
>
> Hi all,
>
> we should take this forward. I've jsut entered times on the doodle.
>
> Generally mornings are ok for me. Unfortunately I can't do afternoons for the time
> being, due to other work commitments.
>
> (I'm in Zambia.)
>
> Bjoern
>
> On 20 Apr 2010, at 17:12, Schulte Olaf A. wrote:
>
> > Hello
> >
> > No (!) response with respect to the date for the next meeting nor to the issues at
> hand. Please consider this a friendly reminder that your input is very welcome.
> >
> > Regards
> >
> > Olaf A.
> >
> >> -----Ursprüngliche Nachricht-----
> >> Von: Schulte Olaf A.
> >> Gesendet: Dienstag, 13. April 2010 23:51
> >> An: [hidden email]
> >> Cc: [hidden email]
> >> Betreff: Metadata group meeting
> >>
> >> Dear All
> >>
> >> There has been little response from the Metadata group with respect to Bjoern's
> >> case around Matterhorn RSS/Atom syndication feeds or the series metadata
> now
> >> proposed for Matterhorn (s. below for details), so my assumption is that you
> >> prefer meetings over list discussions. Would you therefore please indicate your
> >> availability at
> >>
> >> http://doodle.ethz.ch/hzv485yq2rbme5mb
> >>
> >> (early morning for US, late afternoon for Europe) for the next meeting?
> >>
> >> With respect to the agenda, I see two and a half items:
> >>
> >> First, a discussion of the series metadata in general; they are available at
> >>
> >> http://opencast.jira.com/wiki/x/IQDf
> >>
> >> with points for discussion marked red; feel free to add. In particular (half an
> item),
> >> we are concerned about a set of subtypes we would like to introduce for
> >> dcterms:type (item) to describe the various resources DCMI describes as
> >> "MovingImage". We would like to get feedback whether that set (Animation,
> >> Biography, Discussion, Documentation, Farewell Lecture, Film, Inaugural
> Lecture,
> >> Interview, Lecture Recording, Magazine, Music, News, Speech, Sports, Talk)
> makes
> >> sense to you.
> >>
> >> The second item is mapping the metadata to RSS/Atom-like distribution
> channels.
> >> For this, I would hope for someone to help us with a real use case, for the
> group
> >> to discuss whether the existing metadata scheme is adequate to this end.
> >> Brandon, we never finished the discussion about the issues you raised (cf.
> >> attachments), maybe continuing along those lines would help? Or would Bjoern
> like
> >> to make his case?
> >>
> >> Regards
> >>
> >> Olaf A.
> >>
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: [hidden email] [mailto:matterhorn-
> >> [hidden email]] Im Auftrag von Bjoern Hassler
> >> Gesendet: Dienstag, 16. März 2010 23:39
> >> An: Opencast Matterhorn
> >> Betreff: Re: [Opencast Matterhorn] Matterhorn rss/atom syndication feeds
> >>
> >> Hi Adam,
> >>
> >> We keep calling it the "Steeple specification", but really it's an "agreement to
> use
> >> rss/atom/yahoo media in a common way, with minimal extensions". I guess the
> >> "Steeple spec" is:
> >>
> >> 1. Use atom/rss to bundle feeds together (relying on <atom:link rel="subfeed">)
> 2.
> >> Within feeds, use yahoo media (e.g. <media:content>) 3. Include certain
> >> information through use of <media:credit> and <atom:category> (where
> Steeple
> >> has defined some schemes) 4. Add a minimal number of attributes and
> elements
> >> through Steeple namespace.
> >>
> >> Regarding (3), we're including e.g. name of institution/department, and name of
> >> speaker, and recommend <atom:category> for subject classification.
> >>
> >> Regarding (4), the additional attributes I am planning to put forward for
> inclusion
> >> for the yahoo media standard. There are only two additional elements (one
> >> concerning ids, and one for duration), that we would also put forward for
> inclusion
> >> for the yahoo media standard.
> >>
> >> More info here:
> >> http://www.steeple.org.uk/wiki/Syndication
> >> http://purl.org/steeple
> >>
> >> But more than happy to answer by email as well!
> >> Bjoern
> >>
> >>
> >> On Tue, Mar 16, 2010 at 10:29 PM, Adam Hochman
> <[hidden email]>
> >> wrote:
> >>> Hi Bjoern,
> >>> does steeple have its own unique namespace and schema or are you using
> >>> a "standard" like media rss?
> >>>
> >>> ~Adam
> >>>
> >>> On 3/16/10 1:23 PM, Bjoern Hassler wrote:
> >>>>
> >>>> Hi Josh, hi all,
> >>>>
> >>>> I just wanted to revisit the feeds conversation.
> >>>>
> >>>> I'll be able to supply "patches" to the xml, if that's useful. I
> >>>> won't really be able to look into patching the code itself though :-)
> >>>>
> >>>> How can we take this forward? (Incidentally, who's working on iTunesU
> >>>> integration?)
> >>>>
> >>>> Best,
> >>>> Bjoern
> >>>>
> >>>>
> >>>> On Thu, Feb 11, 2010 at 5:26 PM, Josh
> >>>> Holtzman<[hidden email]>
> >>>>  wrote:
> >>>>
> >>>>>
> >>>>> Thanks Bjoern.  The current RSS and atom feeds looks like the xml below.
> >>>>>  If
> >>>>> you'd like to work on patches to make these more "portal friendly",
> >>>>> I'd be happy to help.
> >>>>>
> >>>>> Josh
> >>>>>
> >>>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>>>
> >>>>> <rss xmlns:content="http://purl.org/rss/1.0/modules/content/"
> >>>>> xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
> >>>>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
> >>>>>
> >>>>>   <channel>
> >>>>>     <title>Latest episodes</title>
> >>>>>     <link>http://localhost:8080/engage/ui</link>
> >>>>>     <description>Latest episodes on site</description>
> >>>>>
> >>>>>     <item>
> >>>>>       <title>Land and Vegetation: Key players on the Climate
> >>>>> Scene</title>
> >>>>>
> >>>>>
> >>>>> <link>http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-40
> >>>>> 4b-b1fa-3a54b73a4cbc</link>
> >>>>>
> >>>>>       <content:encoded>&lt;div
> >>>>> xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;img
> >>>>>
> >>>>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-
> >> 3a54b73a4cbc/attachments/attachment-1.jpg"
> >>>>> /&gt;&lt;/div&gt;</content:encoded>
> >>>>>
> >>>>>       <guid
> >>>>> isPermaLink="false">49c1ab86-088a-404b-b1fa-3a54b73a4cbc</guid>
> >>>>>       <itunes:duration>00:00:00</itunes:duration>
> >>>>>       <itunes:author>test</itunes:author>
> >>>>>
> >>>>>       <itunes:explicit>no</itunes:explicit>
> >>>>>       <itunes:keywords />
> >>>>>       <dc:title>Land and Vegetation: Key players on the Climate
> >>>>> Scene</dc:title>
> >>>>>       <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
> >>>>>
> >>>>>
> >>>>> <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
> >>>>>     </item>
> >>>>>   </channel>
> >>>>>
> >>>>> </rss>
> >>>>>
> >>>>> <?xml version="1.0" encoding="UTF-8"?>
> >>>>>
> >>>>> <feed xmlns="http://purl.org/atom/ns#"
> >>>>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="0.3">
> >>>>>
> >>>>>   <title mode="escaped">Latest episodes</title>
> >>>>>   <link rel="alternate" href="http://localhost:8080/engage/ui" />
> >>>>>   <tagline>Latest episodes on site</tagline>
> >>>>>
> >>>>>   <id>latest</id>
> >>>>>   <entry>
> >>>>>     <title mode="escaped">Land and Vegetation: Key players on the
> >>>>> Climate Scene</title>
> >>>>>     <link
> >>>>>
> >>>>> href="http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-404b-
> >> b1fa-3a54b73a4cbc"
> >>>>> />
> >>>>>
> >>>>>     <author>
> >>>>>       <name />
> >>>>>     </author>
> >>>>>     <id>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</id>
> >>>>>     <content type="application/xhtml+xml" mode="xml">
> >>>>>       <div xmlns="http://www.w3.org/1999/xhtml">
> >>>>>
> >>>>>         <img
> >>>>>
> >>>>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-
> >> 3a54b73a4cbc/attachments/attachment-1.jpg"
> >>>>> />
> >>>>>
> >>>>>       </div>
> >>>>>     </content>
> >>>>>     <dc:title>Land and Vegetation: Key players on the Climate
> >>>>> Scene</dc:title>
> >>>>>     <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
> >>>>>
> >>>>> <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
> >>>>>
> >>>>>   </entry>
> >>>>>
> >>>>> </feed>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Thu, Feb 11, 2010 at 7:07 AM, Bjoern
> >>>>> Hassler<[hidden email]>
> >>>>> wrote:
> >>>>>
> >>>>>>
> >>>>>> Hi all,
> >>>>>>
> >>>>>> well done on Matterhorn 0.5!
> >>>>>>
> >>>>>> Would it be worth looking at the rss feeds generated by Matterhorn,
> >>>>>> to see whether there's scope for making these compliant with the
> >>>>>> Steeple rss/atom recommendations?
> >>>>>>
> >>>>>> I should think that the PCF's Miro Communities and the Spanish
> >>>>>> REDIRIS Arca project would be interested in talking about the feeds
> >>>>>> too, to see how they could be used in their projects. Tweaking the
> >>>>>> feeds could be quite useful in a number of ways, for instance
> >>>>>> Matterhorn would then work nicely with the various portal softwares
> >>>>>> around (including the Steeple portal).
> >>>>>>
> >>>>>> How should we take this forward?
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Bjoern
> >>>>>> _______________________________________________
> >>>>>> Matterhorn mailing list
> >>>>>> [hidden email]
> >>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >>>>>>
> >>>>>>
> >>>>>> To unsubscribe please email
> >>>>>> [hidden email]
> >>>>>> _______________________________________________
> >>>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> Matterhorn mailing list
> >>>>> [hidden email]
> >>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >>>>>
> >>>>>
> >>>>> To unsubscribe please email
> >>>>> [hidden email]
> >>>>> _______________________________________________
> >>>>>
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> Matterhorn mailing list
> >>>> [hidden email]
> >>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >>>>
> >>>>
> >>>> To unsubscribe please email
> >>>> [hidden email]
> >>>> _______________________________________________
> >>>>
> >>>>
> >>>
> >>> _______________________________________________
> >>> Matterhorn mailing list
> >>> [hidden email]
> >>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >>>
> >>>
> >>> To unsubscribe please email
> >>> [hidden email]
> >>> _______________________________________________
> >>>
> >> _______________________________________________
> >> Matterhorn mailing list
> >> [hidden email]
> >> http://lists.opencastproject.org/mailman/listinfo/matterhorn
> >>
> >>
> >> To unsubscribe please email
> >> [hidden email]
> >> _______________________________________________
> > _______________________________________________
> > Metadata mailing list
> > [hidden email]
> > http://lists.opencastproject.org/mailman/listinfo/metadata
>
> --
> Dr Bjoern Hassler
> Centre for Applied Research in Educational Technologies &
> Centre for Commonwealth Education,
> University of Cambridge, UK
> Email: [hidden email]
>
> Aptivate | (http://www.aptivate.org)
> The Humanitarian Centre, Fenner's, Gresham Road, Cambridge CB1 2ES
> Email: [hidden email]
>
> Mobile (UK): +44-7952-888939
> Mobile (Zambia): +26-0978-717308
> Web: http://www.sciencemedianetwork.org
>
>

_______________________________________________
Metadata mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/metadata
Brian O'Hagan Brian O'Hagan
Reply | Threaded
Open this post in threaded view
|

Re: [Metadata] Metadata group meeting

Hi all.  

I've updated the Doodle with my availability next week.  Apologies for the delay.  I do look forward to collaborating on moving this conversation forward, thus I'll do my best to coordinate once we have a meeting time! (ps. I'm in New York EST)

/Brian

On Apr 20, 2010, at 11:48 AM, Schulte Olaf A. wrote:

> Hello Bjoern
>
> Your morning makes this pretty difficult for North America...
>
> Regards
>
> Olaf A.
>
>> -----Ursprüngliche Nachricht-----
>> Von: Bjoern Hassler [mailto:[hidden email]]
>> Gesendet: Dienstag, 20. April 2010 17:28
>> An: Schulte Olaf A.
>> Cc: '[hidden email]'
>> Betreff: Re: [Metadata] Metadata group meeting
>>
>> Hi all,
>>
>> we should take this forward. I've jsut entered times on the doodle.
>>
>> Generally mornings are ok for me. Unfortunately I can't do afternoons for the time
>> being, due to other work commitments.
>>
>> (I'm in Zambia.)
>>
>> Bjoern
>>
>> On 20 Apr 2010, at 17:12, Schulte Olaf A. wrote:
>>
>>> Hello
>>>
>>> No (!) response with respect to the date for the next meeting nor to the issues at
>> hand. Please consider this a friendly reminder that your input is very welcome.
>>>
>>> Regards
>>>
>>> Olaf A.
>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Schulte Olaf A.
>>>> Gesendet: Dienstag, 13. April 2010 23:51
>>>> An: [hidden email]
>>>> Cc: [hidden email]
>>>> Betreff: Metadata group meeting
>>>>
>>>> Dear All
>>>>
>>>> There has been little response from the Metadata group with respect to Bjoern's
>>>> case around Matterhorn RSS/Atom syndication feeds or the series metadata
>> now
>>>> proposed for Matterhorn (s. below for details), so my assumption is that you
>>>> prefer meetings over list discussions. Would you therefore please indicate your
>>>> availability at
>>>>
>>>> http://doodle.ethz.ch/hzv485yq2rbme5mb
>>>>
>>>> (early morning for US, late afternoon for Europe) for the next meeting?
>>>>
>>>> With respect to the agenda, I see two and a half items:
>>>>
>>>> First, a discussion of the series metadata in general; they are available at
>>>>
>>>> http://opencast.jira.com/wiki/x/IQDf
>>>>
>>>> with points for discussion marked red; feel free to add. In particular (half an
>> item),
>>>> we are concerned about a set of subtypes we would like to introduce for
>>>> dcterms:type (item) to describe the various resources DCMI describes as
>>>> "MovingImage". We would like to get feedback whether that set (Animation,
>>>> Biography, Discussion, Documentation, Farewell Lecture, Film, Inaugural
>> Lecture,
>>>> Interview, Lecture Recording, Magazine, Music, News, Speech, Sports, Talk)
>> makes
>>>> sense to you.
>>>>
>>>> The second item is mapping the metadata to RSS/Atom-like distribution
>> channels.
>>>> For this, I would hope for someone to help us with a real use case, for the
>> group
>>>> to discuss whether the existing metadata scheme is adequate to this end.
>>>> Brandon, we never finished the discussion about the issues you raised (cf.
>>>> attachments), maybe continuing along those lines would help? Or would Bjoern
>> like
>>>> to make his case?
>>>>
>>>> Regards
>>>>
>>>> Olaf A.
>>>>
>>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: [hidden email] [mailto:matterhorn-
>>>> [hidden email]] Im Auftrag von Bjoern Hassler
>>>> Gesendet: Dienstag, 16. März 2010 23:39
>>>> An: Opencast Matterhorn
>>>> Betreff: Re: [Opencast Matterhorn] Matterhorn rss/atom syndication feeds
>>>>
>>>> Hi Adam,
>>>>
>>>> We keep calling it the "Steeple specification", but really it's an "agreement to
>> use
>>>> rss/atom/yahoo media in a common way, with minimal extensions". I guess the
>>>> "Steeple spec" is:
>>>>
>>>> 1. Use atom/rss to bundle feeds together (relying on <atom:link rel="subfeed">)
>> 2.
>>>> Within feeds, use yahoo media (e.g. <media:content>) 3. Include certain
>>>> information through use of <media:credit> and <atom:category> (where
>> Steeple
>>>> has defined some schemes) 4. Add a minimal number of attributes and
>> elements
>>>> through Steeple namespace.
>>>>
>>>> Regarding (3), we're including e.g. name of institution/department, and name of
>>>> speaker, and recommend <atom:category> for subject classification.
>>>>
>>>> Regarding (4), the additional attributes I am planning to put forward for
>> inclusion
>>>> for the yahoo media standard. There are only two additional elements (one
>>>> concerning ids, and one for duration), that we would also put forward for
>> inclusion
>>>> for the yahoo media standard.
>>>>
>>>> More info here:
>>>> http://www.steeple.org.uk/wiki/Syndication
>>>> http://purl.org/steeple
>>>>
>>>> But more than happy to answer by email as well!
>>>> Bjoern
>>>>
>>>>
>>>> On Tue, Mar 16, 2010 at 10:29 PM, Adam Hochman
>> <[hidden email]>
>>>> wrote:
>>>>> Hi Bjoern,
>>>>> does steeple have its own unique namespace and schema or are you using
>>>>> a "standard" like media rss?
>>>>>
>>>>> ~Adam
>>>>>
>>>>> On 3/16/10 1:23 PM, Bjoern Hassler wrote:
>>>>>>
>>>>>> Hi Josh, hi all,
>>>>>>
>>>>>> I just wanted to revisit the feeds conversation.
>>>>>>
>>>>>> I'll be able to supply "patches" to the xml, if that's useful. I
>>>>>> won't really be able to look into patching the code itself though :-)
>>>>>>
>>>>>> How can we take this forward? (Incidentally, who's working on iTunesU
>>>>>> integration?)
>>>>>>
>>>>>> Best,
>>>>>> Bjoern
>>>>>>
>>>>>>
>>>>>> On Thu, Feb 11, 2010 at 5:26 PM, Josh
>>>>>> Holtzman<[hidden email]>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> Thanks Bjoern.  The current RSS and atom feeds looks like the xml below.
>>>>>>> If
>>>>>>> you'd like to work on patches to make these more "portal friendly",
>>>>>>> I'd be happy to help.
>>>>>>>
>>>>>>> Josh
>>>>>>>
>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>
>>>>>>> <rss xmlns:content="http://purl.org/rss/1.0/modules/content/"
>>>>>>> xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
>>>>>>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
>>>>>>>
>>>>>>>  <channel>
>>>>>>>    <title>Latest episodes</title>
>>>>>>>    <link>http://localhost:8080/engage/ui</link>
>>>>>>>    <description>Latest episodes on site</description>
>>>>>>>
>>>>>>>    <item>
>>>>>>>      <title>Land and Vegetation: Key players on the Climate
>>>>>>> Scene</title>
>>>>>>>
>>>>>>>
>>>>>>> <link>http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-40
>>>>>>> 4b-b1fa-3a54b73a4cbc</link>
>>>>>>>
>>>>>>>      <content:encoded>&lt;div
>>>>>>> xmlns="http://www.w3.org/1999/xhtml"&gt;&lt;img
>>>>>>>
>>>>>>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-
>>>> 3a54b73a4cbc/attachments/attachment-1.jpg"
>>>>>>> /&gt;&lt;/div&gt;</content:encoded>
>>>>>>>
>>>>>>>      <guid
>>>>>>> isPermaLink="false">49c1ab86-088a-404b-b1fa-3a54b73a4cbc</guid>
>>>>>>>      <itunes:duration>00:00:00</itunes:duration>
>>>>>>>      <itunes:author>test</itunes:author>
>>>>>>>
>>>>>>>      <itunes:explicit>no</itunes:explicit>
>>>>>>>      <itunes:keywords />
>>>>>>>      <dc:title>Land and Vegetation: Key players on the Climate
>>>>>>> Scene</dc:title>
>>>>>>>      <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
>>>>>>>
>>>>>>>
>>>>>>> <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
>>>>>>>    </item>
>>>>>>>  </channel>
>>>>>>>
>>>>>>> </rss>
>>>>>>>
>>>>>>> <?xml version="1.0" encoding="UTF-8"?>
>>>>>>>
>>>>>>> <feed xmlns="http://purl.org/atom/ns#"
>>>>>>> xmlns:dc="http://purl.org/dc/elements/1.1/" version="0.3">
>>>>>>>
>>>>>>>  <title mode="escaped">Latest episodes</title>
>>>>>>>  <link rel="alternate" href="http://localhost:8080/engage/ui" />
>>>>>>>  <tagline>Latest episodes on site</tagline>
>>>>>>>
>>>>>>>  <id>latest</id>
>>>>>>>  <entry>
>>>>>>>    <title mode="escaped">Land and Vegetation: Key players on the
>>>>>>> Climate Scene</title>
>>>>>>>    <link
>>>>>>>
>>>>>>> href="http://localhost:8080/engage/ui/watch.html?id=49c1ab86-088a-404b-
>>>> b1fa-3a54b73a4cbc"
>>>>>>> />
>>>>>>>
>>>>>>>    <author>
>>>>>>>      <name />
>>>>>>>    </author>
>>>>>>>    <id>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</id>
>>>>>>>    <content type="application/xhtml+xml" mode="xml">
>>>>>>>      <div xmlns="http://www.w3.org/1999/xhtml">
>>>>>>>
>>>>>>>        <img
>>>>>>>
>>>>>>> src="http://localhost:8080/static/49c1ab86-088a-404b-b1fa-
>>>> 3a54b73a4cbc/attachments/attachment-1.jpg"
>>>>>>> />
>>>>>>>
>>>>>>>      </div>
>>>>>>>    </content>
>>>>>>>    <dc:title>Land and Vegetation: Key players on the Climate
>>>>>>> Scene</dc:title>
>>>>>>>    <dc:publisher>ETH Zurich, Switzerland</dc:publisher>
>>>>>>>
>>>>>>> <dc:identifier>49c1ab86-088a-404b-b1fa-3a54b73a4cbc</dc:identifier>
>>>>>>>
>>>>>>>  </entry>
>>>>>>>
>>>>>>> </feed>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Feb 11, 2010 at 7:07 AM, Bjoern
>>>>>>> Hassler<[hidden email]>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> well done on Matterhorn 0.5!
>>>>>>>>
>>>>>>>> Would it be worth looking at the rss feeds generated by Matterhorn,
>>>>>>>> to see whether there's scope for making these compliant with the
>>>>>>>> Steeple rss/atom recommendations?
>>>>>>>>
>>>>>>>> I should think that the PCF's Miro Communities and the Spanish
>>>>>>>> REDIRIS Arca project would be interested in talking about the feeds
>>>>>>>> too, to see how they could be used in their projects. Tweaking the
>>>>>>>> feeds could be quite useful in a number of ways, for instance
>>>>>>>> Matterhorn would then work nicely with the various portal softwares
>>>>>>>> around (including the Steeple portal).
>>>>>>>>
>>>>>>>> How should we take this forward?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Bjoern
>>>>>>>> _______________________________________________
>>>>>>>> Matterhorn mailing list
>>>>>>>> [hidden email]
>>>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>>>>>
>>>>>>>>
>>>>>>>> To unsubscribe please email
>>>>>>>> [hidden email]
>>>>>>>> _______________________________________________
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Matterhorn mailing list
>>>>>>> [hidden email]
>>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>>>>
>>>>>>>
>>>>>>> To unsubscribe please email
>>>>>>> [hidden email]
>>>>>>> _______________________________________________
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Matterhorn mailing list
>>>>>> [hidden email]
>>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>>>
>>>>>>
>>>>>> To unsubscribe please email
>>>>>> [hidden email]
>>>>>> _______________________________________________
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Matterhorn mailing list
>>>>> [hidden email]
>>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>>
>>>>>
>>>>> To unsubscribe please email
>>>>> [hidden email]
>>>>> _______________________________________________
>>>>>
>>>> _______________________________________________
>>>> Matterhorn mailing list
>>>> [hidden email]
>>>> http://lists.opencastproject.org/mailman/listinfo/matterhorn
>>>>
>>>>
>>>> To unsubscribe please email
>>>> [hidden email]
>>>> _______________________________________________
>>> _______________________________________________
>>> Metadata mailing list
>>> [hidden email]
>>> http://lists.opencastproject.org/mailman/listinfo/metadata
>>
>> --
>> Dr Bjoern Hassler
>> Centre for Applied Research in Educational Technologies &
>> Centre for Commonwealth Education,
>> University of Cambridge, UK
>> Email: [hidden email]
>>
>> Aptivate | (http://www.aptivate.org)
>> The Humanitarian Centre, Fenner's, Gresham Road, Cambridge CB1 2ES
>> Email: [hidden email]
>>
>> Mobile (UK): +44-7952-888939
>> Mobile (Zambia): +26-0978-717308
>> Web: http://www.sciencemedianetwork.org
>>
>>
>
> _______________________________________________
> Metadata mailing list
> [hidden email]
> http://lists.opencastproject.org/mailman/listinfo/metadata
>

_______________________________________________
Metadata mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/metadata
Bjoern Hassler-2 Bjoern Hassler-2
Reply | Threaded
Open this post in threaded view
|

Re: [Metadata] Metadata group meeting

In reply to this post by Schulte Olaf A.
Hi again,

Good point.

Actually, I'm on CEST here (CEST=CAT), so something around 18:30 CEST
onwards could also work.

Bjoern
_______________________________________________
Metadata mailing list
[hidden email]
http://lists.opencastproject.org/mailman/listinfo/metadata