Skip to content

Commit 71f4ef2

Browse files
anders88anders88
committed
Updated readme with descriptions of fields
1 parent 166bd79 commit 71f4ef2

1 file changed

Lines changed: 18 additions & 14 deletions

File tree

‎README.md‎

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -91,20 +91,24 @@ The API returns a list of the published talks for the year. The following format
9191

9292
The following table lists the different fields, and what name we are using to describe this. Feel free to change this if needed (due to short space etc.), but do it intentionally at least ;)
9393

94-
| Field | Name | Field limits | Description given to speaker |
95-
| --- | --- | --- | --- |
96-
| sessionId | _internal field, not for display_ | - |
97-
| title | Title | freetext | Select an expressive and snappy title that captures the content of your talk without being too long. Remember that the title must be attractive and should make people curious. |
98-
| abstract | Description | freetext | Give a concise description of the content and goals of your talk. Try not to exceed 300 words, as shorter and more to-the-point descriptions are more likely to be read by the participants. |
99-
| intendedAudience | Expected Audience and Code Level | freetext | Who should attend this session? How will the participants benefit from attending? Please indicate how code will factor into your presentation (for example "no code", "code in slides" or "live coding"). |
100-
| language | Language | en / no | Which language will you be holding the talk in? It is permitted to use English in your slides, even though you may be talking in Norwegian, but you should write the rest of the abstract in the language you will speak in. We generally recommend that you hold the talk in the language you are most comfortable with. |
101-
| format | Presentation format | presentation / lightning-talk / workshop | In which format are you presenting your talk? Presentation, lightning talk or workshop? |
102-
| level | Experience level | beginner / intermediate / advanced | Who is your talk pitched at? Beginners, Experts or perhaps those in between? |
103-
| keywords | Keywords | list of strings | Suggest up to five keywords that describe your talk. These will be used by the program committee to group the talks into categories. We reserve the right to edit these suggestions to make them fit into this years selected categories. |
104-
| speaker -> name | Speakers name | freetext | Your name |
105-
| speaker -> bio | Short description of the speaker | freetext | Short description of the speaker (try not to exceed 150 words) |
106-
| speaker -> twitter | Twitter handle | freetext | Twitter handle, starting with an @ |
107-
| speaker -> pictureUrl | Picture url | Url | An url to the picture of the speaker. |
94+
| Field | Name | Field limits | Description given to speaker |
95+
|-----------------------|-----------------------------------|------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
96+
| sessionId | _internal field, not for display_ | - |
97+
| title | Title | freetext | Select an expressive and snappy title that captures the content of your talk without being too long. Remember that the title must be attractive and should make people curious. |
98+
| abstract | Description | freetext | Give a concise description of the content and goals of your talk. Try not to exceed 300 words, as shorter and more to-the-point descriptions are more likely to be read by the participants. |
99+
| intendedAudience | Expected Audience and Code Level | freetext | Who should attend this session? How will the participants benefit from attending? Please indicate how code will factor into your presentation (for example "no code", "code in slides" or "live coding"). |
100+
| language | Language | en / no | Which language will you be holding the talk in? It is permitted to use English in your slides, even though you may be talking in Norwegian, but you should write the rest of the abstract in the language you will speak in. We generally recommend that you hold the talk in the language you are most comfortable with. |
101+
| format | Presentation format | presentation / lightning-talk / workshop | In which format are you presenting your talk? Presentation, lightning talk or workshop? |
102+
| level | Experience level | beginner / intermediate / advanced | Who is your talk pitched at? Beginners, Experts or perhaps those in between? |
103+
| keywords | Keywords | list of strings | Suggest up to five keywords that describe your talk. These will be used by the program committee to group the talks into categories. We reserve the right to edit these suggestions to make them fit into this years selected categories. |
104+
| room | Room | text | The room where the talk is scheduled to be held (eg "Room 1") |
105+
| startTime | Start time | datetime (yyyy-mm-ddThh:mm) | The start time of the talk given in local time (Oslo time). (eg 2024-09-05T09:30) |
106+
| endTime | End time | datetime (yyyy-mm-ddThh:mm) | The end time (when the talk is finished) of the talk given in local time (Oslo time). (eg 2024-09-05T09:30) |
107+
| startSlot | Start slot | datetime (yyyy-mm-ddThh:mm) | The start of the slot where the talk is scheduled. For presentations this will be the same as start time, but a lightning talk is scheduled with several other lighting talks. So a lightning talk kan start at 09:20, but the slot is 09:00 because another lightning talk will occur first (eg 2024-09-05T09:00) |
108+
| speaker -> name | Speakers name | freetext | Your name |
109+
| speaker -> bio | Short description of the speaker | freetext | Short description of the speaker (try not to exceed 150 words) |
110+
| speaker -> twitter | Twitter handle | freetext | Twitter handle, starting with an @ |
111+
| speaker -> pictureUrl | Picture url | Url | An url to the picture of the speaker. |
108112

109113

110114
# Private API

0 commit comments

Comments
 (0)