[Nepomuk] RSS Ontology

[Daniel Vrátil]

On Monday 28 of January 2013 22:28:41 you wrote:
> Hi Daniel,

Hi Jörg,

> I like to give a few comments from my side (as I see this from the
> nbib/bibtex publication ontology point of view)
> 
> First: I like your proposal good to see that you are working to get
> this information into nepomuk.
> A few parts however are duplicated and thus not needed
> 
> Like Sebastian said
> nso:title -> nie:title
> nso:description -> nie:description
> nso:publisher -> nco:publisher
> nso:author -> nco:creator
> 
> nso:content -> use nie:plainTextContent and/or nie:htmlContent

Does it mean I should simply remove these properties from nso, and just assume 
others will realize that they should use nie:description or nco:creator?

> 
> Furthermore instead of
> nso:sourceUrl you could use nie:url and save the url as
> nfo:WebDataObject or nfo:Website
> See also [1]
> 
> for nso:length.
> Do you mean to add the encolure always as podcast/video/audio file?
> 
> than maybe there should be 1 or more enclosures that can have an
> nfo:Media Resource that has the nfo:duration instead.

As Sebastian suggested, I will specialize nso:Enclosure by providing 
nso:ImageEnclosure, nso:VideoEnclosure and nso:AudioEnclosure, adding 
nfo:duration (replacing nso:length) to Video and Audio enclosures.

> 
> In case my nbib proposal will get fully release into SDO (hopefully
> before 4.11 ;) [2][3]
> together with my nbib proposal there will be
> nie:publicationDate as a replacement for nso:publishTime

It would be awesome to get it to SDO as soon as possible so that I could reuse 
this since we are aiming for 4.11 with Akregator2 too.

> 
> Also as I designed the nbib proposal with web publications in mind you
> could replace
> nso:Article
> 
> In the sense that each nso:Feed contains several nbib:BlogPost Resources
> so nso:Article -> nbib:BlogPost

But does RSS feed always come from a blog? Does it make sense to store 
articles from CNN.com as nbib:BlogPost?

> Also each nbib:BlogPost (which is a subclass of nbib:Article) can be
> in a collection nbib:Blog
> This would allow to later on combine again blogposts from one blog
> only that are retrieved via
> some kind of planet rss feed where usually several different blogs are
> located (horray for semantic filtering)

Although I love the idea, I'm afraid we don't have this information. A feed 
item only belongs to the feed, there is no information about it's "blog of 
origin".

> 
> Also we could add a new subclass specially for podcasts, but I think
> this might not be necessary.

Podcast is just an audio enclosure, I don't think any special subclass is 
needed here.


Cheers,
Dan

> 
> 
> Cheers,
> Jörg
> 
> 
> [1]
> http://trueg.wordpress.com/2012/02/02/a-little-drier-but-not-that-dry-extra
> cting-websites-from-nepomuk-resources/ [2]
> http://sourceforge.net/apps/trac/oscaf/ticket/124
>     
> https://projects.kde.org/projects/playground/edu/conquirere/repository/revi
> sions/master/show/nbib [3] http://sourceforge.net/apps/trac/oscaf/ticket/126
-- 
dvratil at redhat.com | Associate Software Engineer / BaseOS / KDE, Qt
GPG Key: 0xC59D614F6F4AE348
Fingerprint: 4EC1 86E3 C54E 0B39 5FDD B5FB C59D 614F 6F4A E348
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/nepomuk/attachments/20130129/966e0db8/attachment.sig>