Create a book
BuRST format adaption discussion
From Stellar Deliverable 6.3
Contents |
1 General proposals for the format
This document is intended for discussion of a second version of the publication feed format. Mandatory pieces are referred to with 'MUST', optional stuff is labeled with 'CAN'.
1.1 Entity representations
Represent entities in vCard to include location data (proposal by Till Nagel). Example:
<v:VCard rdf:about="http://www.cs.kuleuven.be" > <v:fn>K.U. Leuven</v:fn> <v:org> <rdf:Description> <v:organisation-name>K.U. Leuven</v:organisation-name> <v:organisation-unit>Dept. Computer Science</v:organisation-unit> </rdf:Description> </v:org> <v:adr> <rdf:Description> <v:street-address>Celestijnenlaan 200A</v:street-address> <v:locality>Heverlee</v:locality> <v:postal-code>3001</v:postal-code> <v:country-name>Belgium</v:country-name> <rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#Work"/> </rdf:Description> </v:adr> <v:geo> <rdf:Description> <v:latitude>50.863</v:latitude> <v:longitude>4.679</v:longitude> </rdf:Description> </v:geo> <v:tel> <rdf:Description> <rdf:value>+32 16 327066</rdf:value> <rdf:type rdf:resource="http://www.w3.org/2006/vcard/ns#Work"/> </rdf:Description> </v:tel> <v:email rdf:resource="mailto:info@cs.kuleuven.be"/> <v:logo rdf:resource="http://www.cs.kuleuven.be/cs/includes/common/_i/logo-kuleuven.gif"/> </v:VCard>
2 Proposals for additional metadata needed in the feeds
Include swrc:cite and swrc:citedBy in the standard
Include swrc:doi in the standard - I don't think its safe or sensible to use swrc:isbn to represent this, but I do think doi is vital to help with disambiguation. I also note that including swrc:isbn in <swrc:Article> or <swrc:Book> renders the feed invalid - if correct, the documentation needs to reflect this.
3 Proposals for the existing metadata
3.1 CHANNEL
Describes the elements which MUST be present in the channel (describing properties of the collection of publications in the feed).
3.1.1 Root element
| Class | Subclasses/Format of literal | Properties (description) | optional | Comments | Proposals | |
|---|---|---|---|---|---|---|
| Channel | channel | see table below | rdf:about (uri of the channel) |
3.1.2 Subclasses of channel
Elements describing the properties of the collection.
| Property | Subclasses/Format of literal | Properties (description) | optional | Comments | Proposals | |
|---|---|---|---|---|---|---|
| Title of the collection | title | free text | ||||
| Description of the collection | description | free text | ||||
| Link to collection/publisher | link | url | e.g. a link to the collection or to the homepage of the publisher | Use RFC 1738 http://www.faqs.org/rfcs/rfc1738.html | ||
| Last update | dc:date | date in the format: YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00), whereby TZD is the time zone designator and describes the offset from the UTC | http://www.w3.org/TR/NOTE-datetime. We need this to ensure proper updating. | |||
| Publisher of feed | dc:publisher | free text | yes | Define a format for institutions | ||
| Items | items | rdf:Seq | Items in the sequence as they appear in the feed |
3.1.3 Sublasses of rdf:Seq
URIs of all publications must be listed here.
| Property | Subclasses/Format of literal | Properties (description) | optional | Comments | Proposals | |
|---|---|---|---|---|---|---|
| Item | rdf:li | rdf:resource (uri of the publication) |
3.2 ITEMS
3.2.1 Root element
| Property | Subclasses/Format of literal | Properties (description) | optional | Comments | Proposals | |
|---|---|---|---|---|---|---|
| Item | item | see table below | rdf:about (uri of the item) xml:lang (language of the item - optional) | The URI must be the same as in the items list in the channel. Items must be also be in the same sequence | Specify a list of languages that are available; we could use 639.1 http://www.loc.gov/standards/iso639-2/php/code_list.php |
3.2.2 Sublasses of item
Put here all the information that you would like to have displayed in feed readers/applications capable of displaying RSS feeds. This is not the metadata commonly perused by the Open Archive. This information should be ennclosed in burst:publication (see below)
| Property | Subclasses/Format of literal | Properties (description) | optional | Comments | Proposals | |
|---|---|---|---|---|---|---|
| Title of publication | title | free text | ||||
| Description of publication | description | free text | ||||
| Link to the publication | link | url | If available, put here the link to the fulltext. Otherwise a link to page where the publication can be obtained. | Use RFC 1738 http://www.faqs.org/rfcs/rfc1738.html | ||
| Last update | dc:date | date in the format: YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00), whereby TZD is the time zone designator and describes the offset from the UTC | http://www.w3.org/TR/NOTE-datetime We need this to ensure proper updating. | |||
| Authors | dc:creator | LASTNAME, FIRSTNAME; LASTNAME, FIRSTNAME,... | yes | |||
| Keywords | dc:subject | free text | yes | Use a tag per keyword | Define characters that are not allowed, e.g. comma, semicolon | |
| Connection to publication metadata | burst:publication | see table below |
3.2.3 Subclasses of burst:publication
The link between the RSS item and the RDF metadata part is done by burst:publication. First, specify the document type (take one ot the classes below):
| Document type | Class | Subclasses/Format of literal | Properties (description) | optional | Comments | Proposals |
|---|---|---|---|---|---|---|
| Unspecified publication | swrc:Publication | see table below | ||||
| Publication in journal | swrc:Article | see table below | There seems to be no way to express the quality (peer-reviewed or not) in SWRC | |||
| Publication in conference proceedings | swrc:InProceedings | see table below | There seems to be no way to express the quality (peer-reviewed or not) in SWRC | |||
| Book chapter | swrc:InBook | see table below | ||||
| Book | swrc:Book | see table below | ||||
| Research report | swrc:ProjectReport | see table below | ||||
| Proceedings | swrc:Proceedings | see table below | ||||
| Thesis | swrc:Thesis | see table below | We could be even more specific here; swrc offers MasterThesis and PhDThesis as subclasses | |||
| Other | swrc:Misc | see table below | ||||
| Document type: Workshop | swrc: Workshop | see table below | swrc:Workshop is actually a subclass of swrc:Event |
3.2.4 Subclasses of document type
Put here all the metadata you have about the publication:
| Root element | Class/Property | Subclasses/Format of literal | Properties (description) | optional | Comments | Proposals |
|---|---|---|---|---|---|---|
| Author | swrc:author | swrc:Person | Fallback: dc:creator. | |||
| Title | swrc:title | free text | xml:lang (language of the title - optional) | Fallback: title | Specify a list of languages that are available; we could use 639.1 http://www.loc.gov/standards/iso639-2/php/code_list.php | |
| Writing year | swrc:year | YYYY | e.g. 2009 | |||
| Writing month | swrc:month | MM | yes | e.g. 06 | ||
| Publication date | swrc:date | YYYY-MM-DD | yes | In case you want to be more specific, you can use this instead of swrc:year and swrc:month. e.g. 2009-06-17 | ||
| Abstract | swrc:abstract | free text | yes | Fallback: description. I'm not to sure about this fallback though - The item description may contain more/different content than the original abstract. | ||
| Book title | swrc:booktitle | free text | The title of the containing publication. Could also be the title of the proceedings, or a journal title | |||
| Commercial Editor (publisher) | swrc:publisher | free text | yes | |||
| Conference title | swrc:atEvent | free text | yes | Specify conference, e.g. ECTEL 2009 | ||
| ISBN | swrc:isbn | isbn | yes | e.g. 978-3-642-04635-3 | ||
| Keywords | swrc:keywords | keywords separated by comma | yes | Fallback: dc:subject | ||
| Pages | swrc:pages | FROM_PAGE-TO_PAGE | yes | e.g. 99-110 | Allow one number as well for one-pagers | |
| Place | dc:spatial | CITY, COUNTRY | yes | Unfortunately, there is no geographical information in swrc. e.g. Graz, Austria | Use genoames here .. We need better location data than just city and country | |
| Project | swrc:describesProject | free text | yes | Specify name of the project here | ||
| Research team | swrc:projectInfo | free text | yes | Specify research group here | ||
| Scientific Editor | swrc:editor | swrc:Person | yes | |||
| Series | swrc:series | text (series) | yes | |||
| Volume | swrc:volume | text (volume) | yes |
3.2.5 Subclasses of swrc:Person
Put here all the metadata you have about the authors/editors:
| Root element | Class/Property | Subclasses/Format of literal | Properties (description) | optional | Comments | Proposals |
|---|---|---|---|---|---|---|
| Name | swrc:name | LAST NAME, FIRST NAME | ||||
| Affiliation | swrc:affiliation | free text | yes | Specify organization here |
3.3 EXAMPLE
<?xml version="1.0" encoding="utf-8"?>
<rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:foaf="http://xmlns.com/foaf/0.1/"
xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:burst="http://xmlns.com/burst/0.1/">
<channel rdf:about="http://know-center.tugraz.at/download_extern/papers/feed">
<title>Know-Center Publications</title>
<link>http://know-center.tugraz.at/</link>
<description>Austria's Competence Center for Knowledge Management</description>
<dc:date>2009-09-01T09:00:00+01:00</dc:date>
<dc:publisher>Know-Center</dc:publisher>
<items>
<rdf:Seq>
<rdf:li rdf:resource="http://know-center.tugraz.at/papers/473" />
</rdf:Seq>
</items>
</channel>
<item rdf:about="http://know-center.tugraz.at/papers/473" xml:lang="en">
<title xml:lang="en">Getting to Know Your User – Unobtrusive User Model Maintenance within Work-Integrated
Learning Environments</title>
<link>http://know-center.tugraz.at/download_extern/papers/Lindstaedt_UserModelServices-ECTEL_CameraReady.pdf</link>
<description>Lindstaedt, S. N., Beham, G., Kump, B., Ley, T. (2009): Getting to Know Your User – Unobtrusive
User Model Maintenance within Work-Integrated Learning Environments, In: Learning in the Synergy of Multiple
Disciplines: Proceedings of the 4th European Conference on Technology Enhanced Learning, ECTEL 2009, Nice, France,
September/October 2009, pp. 73--87.</description>
<dc:date>2009-08-22T10:30:02+01:00</dc:date>
<burst:publication>
<swrc:InProceedings>
<swrc:title xml:lang="en">Getting to Know Your User – Unobtrusive User Model Maintenance within
Work-Integrated Learning Environments</swrc:title>
<swrc:author>
<swrc:Person>
<swrc:name>Lindstaedt, Stefanie N.</swrc:name>
<swrc:affiliation>Knowledge Management Institute, TU Graz</swrc:affiliation>
<swrc:affiliation>Know-Center</swrc:affiliation>
</swrc:Person>
</swrc:author>
<swrc:author>
<swrc:Person>
<swrc:name>Beham, Günter</swrc:name>
<swrc:affiliation>Knowledge Management Institute, TU Graz</swrc:affiliation>
<swrc:affiliation>Know-Center</swrc:affiliation>
</swrc:Person>
</swrc:author>
<swrc:author>
<swrc:Person>
<swrc:name>Kump, Barbara</swrc:name>
<swrc:affiliation>Knowledge Management Institute, TU Graz</swrc:affiliation>
<swrc:affiliation>Know-Center</swrc:affiliation>
</swrc:Person>
</swrc:author>
<swrc:author>
<swrc:Person>
<swrc:name>Ley, Tobias</swrc:name>
<swrc:affiliation>Know-Center</swrc:affiliation>
<swrc:affiliation>Cognitive Science Section, University of Graz</swrc:affiliation>
</swrc:Person>
</swrc:author>
<swrc:abstract>Work-integrated learning (WIL) poses unique challenges for user model design: on the one hand
users’ knowledge levels need to be determined based on their work activities – testing is not a
viable option; on the other hand users do interact with a multitude of different work applications –
there is no central learning system. This contribution introduces a user model and corres-ponding services
(based on SOA) geared to enable unobtrusive adaptability within WIL environments. Our hybrid user model
services interpret usage data in the context of enterprise models (semantic approaches) and utilize heuristics
(scruffy approaches) in order to determine knowledge levels, identify subject matter experts, etc. We give an
overview of different types of user model ser-vices (logging, production, inference, control), provide a
reference implementation within the APOSDLE project, and discuss early evaluation results.</swrc:abstract>
<swrc:projectInfo>APOSDLE</swrc:projectInfo>
<swrc:atEvent>ECTEL 2009</swrc:atEvent>
<dc:spatial>Nice, France</dc:spatial>
<swrc:booktitle>Learning in the Synergy of Multiple Disciplines: Proceedings of the 4th European Conference on
Technology Enhanced Learning, ECTEL 2009, Nice, France, September/October 2009</swrc:booktitle>
<swrc:editor>
<swrc:Person>
<swrc:name>Cress, U.</swrc:name>
</swrc:Person>
</swrc:editor>
<swrc:editor>
<swrc:Person>
<swrc:name>Dimitrova, V.</swrc:name>
</swrc:Person>
</swrc:editor>
<swrc:editor>
<swrc:Person>
<swrc:name>Cress, U.</swrc:name>
</swrc:Person>
</swrc:editor>
<swrc:year>2009</swrc:year>
<swrc:month>09</swrc:month>
<swrc:pages>73-87</swrc:pages>
<swrc:isbn>978-3-642-04635-3</swrc:isbn>
<swrc:series>LNCS</swrc:series>
<swrc:volume>5794</swrc:volume>
<swrc:keywords>user model, service-oriented architecture, work-integrated learning, adaptivity</swrc:keywords>
</swrc:InProceedings>
</burst:publication>
</item>
</rdf:RDF>