Internet Draft G. FitzPatrick, Medianet draft-many-ical-ski-00.txt N. Hjelm, Soft Applications P. Lannero, Medianet Expires six months from: 1999-09-13 SKiCal - an adaptation of iCalendar for describing public events Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC-2026 [1]. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This Memo defines the SKiCal format. SKiCal is a machine readable format for describing public events and other phenomena in time and space. SKiCal is based on and extends the iCalendar format as defined by RFC-2445, Internet Calendaring and Scheduling Core Object Specification (iCalendar) [3]. SKiCal objects are basically iCalendar objects containing VEVENT components with the additions of experimental properties, constructed according to the specification in RFC-2445 section 4.8.8.1. SKiCal is an attempt to adapt iCalendar to the common needs of many organizers of public events (e.g. culture, sports, tourist attractions), and potential attendees of those events. The format has been developed through the combined effort of several Swedish national agencies. draft-many-ical-ski-00.txt Table of Contents 1. Reading instructions and conventions .............................3 2 SKiCal specific property parameters ................................3 2.1 Person's Role ...................................................3 2.2 Thing's Role ....................................................4 3. SKiCal specific component properties .............................4 3.1 WHAT properties .................................................5 3.1.1 Title ..........................................................5 3.1.2 Persons ........................................................6 3.1.3 Think ..........................................................7 3.1.4 Things .........................................................7 3.1.5 Part of another event ..........................................8 3.1.6 Language used at the event .....................................9 3.1.7 Orientation ...................................................10 3.1.8 What URL ......................................................10 3.1.9 Event Unique Identifier .......................................11 3.2 WHEN properties ................................................12 3.2.1 Opening times .................................................12 3.2.2 Scheduled times ...............................................13 3.2.3 Geo related natural times. ....................................13 3.2.4 Relative Times ................................................13 3.3 WHICH properties ...............................................14 3.3.1 Venue .........................................................14 3.4 WHERE properties ...............................................15 3.4.1 Directions ....................................................15 3.4.2 Place name ....................................................16 3.4.3 Media addresses. ..............................................16 3.5 WHOW (HOW) properties ..........................................17 3.5.1 Qualification for admission ...................................17 3.5.2 Qualification for participation ...............................18 3.5.3 Price .........................................................19 3.5.4 Ticketing .....................................................20 3.5.5 Reservations ..................................................21 3.5.6 Smoking .......................................................22 3.5.7 Parking .......................................................22 3.5.8 Handicap facilities ...........................................23 3.5.9 Accepted method of payment ....................................24 3.5.10 Rules for the consumption of alcohol ........................24 3.5.11 Food ........................................................25 3.5.12 Transportation ..............................................26 3.6 WHY properties .................................................27 3.6.1 Motivation ....................................................28 3.6.2 Promotion .....................................................28 3.6.3 Third party review ............................................29 3.7 WHO properties .................................................29 3.7.1 Responsible ...................................................30 3.7.2 Other agents ..................................................31 3.7.3 Association ...................................................31 3.8 MANAGEMENT properties ..........................................32 3.8.1 Checksum ......................................................33 3.8.2 Publisher .....................................................33 4 Choosing values from lists ........................................34 5 Intended use ......................................................36 6 Security considerations ...........................................37 draft-many-ical-ski-00.txt 7 Internationalization/localization .................................37 8 References ........................................................37 9 Acknowledgments ...................................................38 10 Authors' addresses ..............................................38 Full Copyright Statement.............................................38 1. Reading instructions and conventions This document is intended to be read alongside RFC-2445 [3]. The same basic grammar and formatting conventions apply. The notation used in this memo is the ABNF notation of RFC-2234 [4]. Readers intending on implementing the format defined in this memo should be familiar with this notation in order to properly interpret the specifications of this memo. Also, they MUST be familiar with the iCalendar core object specification (RFC-2445 [3]). The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [2]. The word "event" is to be widely interpreted as a resource existing in time and space. For example a museum, which is indeed a persistent resource, but which can be described in terms of time, location and subject category. Another example is a TV show. It has no traditional location, but it can be described by a SKiCal object as an event. 2 SKiCal specific property parameters The following are general SKiCal property parameters not previously defined by RFC-2445: 2.1 Person's Role Parameter Name: DIPROLE Purpose: To clarify the role of a person(s) in the event. Note: The abbreviation DIP stands for "by Description Identifiable Person" which basically means person. See [9] for discussion. Format Definition: The property parameter is defined by the following notation: personroleparam = "DIPROLE" "=" ("PRESENT" ; At the event / "REFERENCED" ; Not present at the event / "PERFORMER" ; Appearing at the event / "CREATOR" ; Not necessarily present Description: This parameter can be specified on X-SKI-PERSONS property. The parameter declares whether named persons will actually be at the event, or referred to. draft-many-ical-ski-00.txt Example: X-SKI-PERSONS;DIPROLE=REFERENCED:Marilyn Monroe X-SKI-PERSONS;DIPROLE=CREATOR:Beethoven, Ludwig van 2.2 Thing's Role Parameter Name: DITROLE Purpose: To clarify the role of a named thing(s) in the event. Note: The abbreviation DIT stands for "by Description Identifiable Thing" which basically means thing. See [9] for discussion. Format Definition: The property parameter is defined by the following notation: thingroleparam = "DITROLE" "=" ("PRESENT" ; At the event / "REFERENCED" ; Not present at the event ; Default is PRESENT Description: This parameter can be specified on X-SKI-THINGS property. The parameter declares whether named things will actually be at the event, or referred to. Example: X-SKI-THINGS;DITROLE=PRESENT:Car models of 2001 3. SKiCal specific component properties The class of SKiCal objects is a superset of the class of iCalendar objects. Therefore any component property which MAY appear in a VEVENT iCalendar component is also allowed in a SKiCal object. In addition, component properties with names beginning "X-SKI-" are defined in this memo. It is RECOMMENDED that publishers fetch the terms used as TEXT type property values from authoritative lists of terms. Those publishers who consequently use terms found in such lists will facilitate very extensive automatic treatment of their information. For example, if such a list is being translated into several languages, then it will be possible to get accurate results when searching for events described in languages other than that used in the query. For reasons of clarity the properties self-describing the iCalendar object are presented under the "MANAGEMENT" header (Calendar object management), while properties describing the real life event are presented under the interrogative headers; "WHAT", "WHEN", "WHERE", "WHO", "WHY", "WHICH" and "WHOW". These headers, which we call the WHA interrogatives, have no technical significance today. draft-many-ical-ski-00.txt 3.1 WHAT properties The following properties answer questions about the event such as "What is it?" and "What is happening?". The properties defined in RFC-2445 [3] that the SKiCal working group considers related to WHAT are: 4.8.1.1 Attachment 4.8.1.2 Categories 4.8.1.5 Description 4.8.1.12 Summary In addition to the properties named above as defined in RFC-2445, a SKiCal object may include the following properties; 3.1.1 Title Property Name: X-SKI-TITLE Purpose: This property specifies the title of the event described. Value Type: TEXT. Property Parameters: Non-standard and language property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Public events often have titles associated with them. The title may not always be a good SUMMARY of the event, but it is a piece of information which the publisher of the event will expect to be able to convey to the audience. It might also be a copyrighted name that the publisher wishes to see included in the calendar object. Format Definition: The property is defined by the following notation: x-ski-title = "X-SKI-TITLE" titleparam ":" text CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. titleparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) / ; the following is optional, ; and MAY occur more than once (";" xparam) draft-many-ical-ski-00.txt ) Example: The following are examples of this property: X-SKI-TITLE:Les Miserables X-SKI-TITLE;LANGUAGE=se:En kvall med Victor Borge X-SKI-TITLE;LANGUAGE=en:One night with Victor Borge 3.1.2 Persons Property Name: X-SKI-PERSONS Purpose: This property specifies named persons associated with the event. Persons expected to perform or participate, act or speak, contribute or be honored. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Persons at an event may be an artist, a sports team, a guide, a disc jockey or a presenter, for example. Format Definition: The property is defined by the following notation: x-ski-persons = "X-SKI-PERSONS" personsparam ":" text CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. personsparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) /(";" personroleparam ) / ; the following is optional, ; and MAY occur more than once (";" xparam) ) Example: The following are examples of this property: X-SKI-PERSONS;DIPROLE=PERFORMER:The Rolling Stones X-SKI-PERSONS:Victor Borge X-SKI-PERSONS:DIPROLE=CREATOR:Woody Allen X-SKI-PERSONS:DIPROLE=PRESENT:The king of Spain draft-many-ical-ski-00.txt X-SKI-PERSONS;DIPROLE=PERFORMER:AIK, a-laget i fotboll X-SKI-PERSONS:The Hawthorn High School class of 2000 X-SKI-PERSONS;DIPROLE=REFERENCED:Nelson Mandela 3.1.3 Think Property Name: X-SKI-THINK Purpose: This property specifies an idea, philosophy, concept, that is not a physical PERSON or a material THING Value Type: TEXT Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: A think could be a theory, revelation, philosophy etc. Format Definition: The property is defined by the following notation: x-ski-think = "X-SKI-THINK" thinkparam ":" text CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. thinkparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) / ; the following is optional, ; and MAY occur more than once (";" xparam) ) Example: The following is an example of this property: X-SKI-THINK:World Peace 3.1.4 Things Property Name: X-SKI-THINGS Purpose: This property specifies things of significance exhibited, featured or referred to at the event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be draft-many-ical-ski-00.txt specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Things at an event may be a book, painting, furniture, Gucci Handbags, Wrangler Jeans, famous wines. Format Definition: The property is defined by the following notation: x-ski-things = "X-SKI-THINGS" thingsparam ":" text CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. thingsparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) /(";" thingroleparam ) / ; the following is optional, ; and MAY occur more than once (";" xparam) ) Example: The following are examples of this property: X-SKI-THINGS:German Antiques X-SKI-THINGS:Fritidsbatar X-SKI-THINGS:Ming Dynasty Porcelain X-SKI-THINGS:Thai cuisine X-SKI-THINGS;DITROLE=REFERENCED:The holy Grail 3.1.5 Part of another event Property Name: X-SKI-PARTOF Purpose: This property specifies another event, of which the described event is part. This does not imply an inheritance of properties from the named PARTOF-event but rather a relevance. Value Type: TEXT. (UID for another SKiCal/iCalendar object.) Property Parameters: Non-standard property parameters can be specified on this property. It is RECOMMENDED that a Common Name parameter (cnparam) be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. draft-many-ical-ski-00.txt Description: This property allows for the publisher of an event to indicate that the event is part of another event, such as a festival or a package of tourist attractions. This property resembles the RELATED-TO;RELTYPE=parent property, but that relationship is determined by a calendar user. Format Definition: The property is defined by the following notation: x-ski-partof = "X-SKI-PARTOF" partofparam ":" text CRLF partofparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) / (";" cnparam ) / ; the following is optional, ; and MAY occur more than once (";" xparam) ) Example: The following are examples of this property: X-SKI-PARTOF;CN=Vattenfestivalen:<19990401T080045Z- F192713@stoinfo.se> X-SKI-PARTOF;CN=2004 Winter Olympics:<19991202@olympic.org> X-SKI-PARTOF: 3.1.6 Language used at the event Property Name: X-SKI-EVENT-LANGUAGE Purpose: This property specifies the language used at the event, knowledge of which is needed in order to appreciate the event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Language used at the event. For example, the main language of a theatre play. If the event is being translated, the information about what languages are being translated should be published under RESOURCES. If one can appreciate the event without knowledge of any specific language, this property should not be specified. Format Definition: The property is defined by the following notation: draft-many-ical-ski-00.txt x-ski-event-language = "X-SKI-EVENT-LANGUAGE" ":" language CRLF language = Example: The following is an example of this property: X-SKI-EVENT-LANGUAGE:en X-SKI-EVENT-LANGUAGE:sv 3.1.7 Orientation Property Name: X-SKI-ORIENTATION Purpose: This property can, without implying inclusion or exclusion of calendar users, facilitate event searches. It can indicate that an event has a specific target audience, or that it is somehow related to a specific cause, faith, professional group, gender, ethnic group etc. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Format Definition: The property is defined by the following notation: x-ski-orientation = "X-SKI-ORIENTATION" orientparam ":" text CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. orientparam = *(";" text) ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. Value Type: TEXT. Example: The following is an example of this property: X-SKI-ORIENTATION;Religious:Methodist X-SKI-ORIENTATION;Political:Liberal X-SKI-ORIENTATION;Age:>65 X-SKI-ORIENTATION;Gender:Female X-SKI-ORIENTATION;Sexual:Gay 3.1.8 What URL Property Name: WHURL draft-many-ical-ski-00.txt Purpose: This property defines a Uniform Resource Locator (URL) associated with the event the SKiCal object is describing. Value Type: URI Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: This property may be used in a calendar component to convey a location where a more dynamic rendition of the event described by the calendar component can be found. This memo does not attempt to standardize the form of the URI, nor the format of the resource pointed to by the property value. If the URL property and Content-Location MIME header are both specified, they MUST point to the same resource. Format Definition: The property is defined by the following notation: whurl = "WHURL" whurlparam ":" uri CRLF whurlparam = *(";" xparam) Example: The following is an example of this property: WHURL:http://www.medianet.org/ 3.1.9 Event Unique Identifier Property Name: EUID Purpose: This property defines the persistent, globally unique identifier for the Event. Value Type: TEXT Property Parameters: Non-standard property parameters can be specified on this property. Description: The EUID itself MUST be a globally unique identifier. The generator of the identifier MUST guarantee that the identifier is unique. There are several algorithms that can be used to accomplish this. The identifier is RECOMMENDED to be the identical syntax to the [RFC-822] addr-spec. A good method to assure uniqueness is to put the domain name or a domain literal IP address of the host on which the identifier was created on the right hand side of the "@", and on the left hand side, put a combination of the current calendar date and time of day (i.e., formatted in as a DATE- TIME value) along with some other currently unique (perhaps sequential) identifier available on the system (for example, a process id number). Using a date/time value on the left hand side and a domain name or domain literal on the right hand side makes it draft-many-ical-ski-00.txt possible to guarantee uniqueness since no two hosts should be using the same domain name or IP address at the same time. Though other algorithms will work, it is RECOMMENDED that the right hand side contain some domain identifier (either of the host itself or otherwise) such that the generator of the message identifier can guarantee the uniqueness of the left hand side within the scope of that domain. Note: This method is identical to that recommended for the creation of UID's as described in RFC-2445, section 4.8.4.7. This property is an important method for determining the definite, authoritative and unique source of an event. We must separate the management of calendar objects from the management of events. There MUST be only one EUID for an event, though there MIGHT exist several Calendar Objects, each with their own UID describing the exact same event. Format Definition: The property is defined by the following notation: euid = "EUID" euidparam ":" text CRLF euidparam = *(";" xparam) Example: The following is an example of this property: EUID:20021001T090045Z-4000F192713-0052@qwack.com 3.2 WHEN properties The following properties answer time and date related questions about the event, such as "When does it happen?". The properties defined in RFC-2445 [3] that the SKiCal working group considers related to WHEN are: 4.8.2 Date and Time Component Properties 4.8.3 Time Zone Component Properties 4.8.5 Recurrence Component Properties In addition to the properties named above as defined in RFC-2445, a SKiCal object may include the following properties; 3.2.1 Opening times Property Name: X-SKI-OPENINGTIMES Description: Opening times is currently under discussion in the CalSch working group. There are arguments for including OPENINGTIMES as a component property or a property parameter. This could necessitate some rule and syntax changes for; 4.8.5.1 Exception Date/Times, 4.8.5.2 Exception Rule,4.8.5.3 Recurrence Date/Times, 4.8.5.4 Recurrence Rule. draft-many-ical-ski-00.txt In brief we would like to see the following hierarchical syntax for Opening times: TERM SEASONS IDENTICAL DAYS TIME SLOT EXCEPTIONS Where: TERM(mandatory), expressed with DTSTART and DTEND, sets the limits for the declaration of an event's opening times. Any dates and times outside the limits of the TERM will be parsed as not-defined. SEASONS(optional), expressed with DTSTART and DTEND, set the limits for periods of consecutive days, which are assumed to reoccur during the TERM. It is assumed that seasons could be used at the convenience of the publisher to define reoccurring sets of IDENTICAL DAYS. IDENTICAL DAYS(optional), are days made up of exactly identical TIME SLOT schedules. IDENTICAL DAYS are first declared with TIME SLOT sets, given unique names and then related to days of the week (by- named day) or days of the month or days of the year or by Date. TIME SLOTS(mandatory), define the start and stop times for: OPEN and CLOSED times qualified OPEN and CLOSED times by free text named times, at the discretion of the publisher. EXCEPTIONS(optional) relate non-conforming dates to matching IDENTICAL DAYS 3.2.2 Scheduled times Property Name: X-SKI-SCHEDULINGTIMES Scheduling times is currently under discussion in the Calsch working groups and will hopefully be classified as a new iCalendar property. 3.2.3 Geo related natural times. With the aid of geographic location, altitude and compass course cross-referencing authoritative registries, there are capabilities for including "Natural" time and date properties. ex. Sunup, Sundown, High-tide and Low-tide, full moon and solar eclipses etc, as well as Lunar calendar based events. 3.2.4 Relative Times Relative Time properties are times dependent upon the times for other events. They cannot exist independently. draft-many-ical-ski-00.txt Example: the bar at the opera always opens one hour before the performance. Can be declared by the bar tender, with out any knowledge of the Opera Company's repertoire and schedule. 3.3 WHICH properties WHICH is used to signify a choice of venues, or media, a question which transcends the semantic limits of WHERE. The following property answers the question, "In which context does the event occur?" There is no property defined in RFC-2445 [3] that the SKiCal working group considers related to WHICH. 3.3.1 Venue Property Name: X-SKI-VENUE Purpose: This property defines the "physical" room in which an event takes place. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: The venue parameter divides events into a number of distinctly different groups, which is useful when there is a need to quickly reduce the number of events in a selection. For example: When searching for outdoor sports events to take part in, it will help not having to browse through listings of all sports TV shows. Format Definition: The property is defined by the following notation: x-ski-venue = "X-SKI-VENUE" ":" venuetype CRLF venuetype = "Internet"/ "Radio"/ "TV" / "Outdoors"/ "Indoors"/ "Travel-transit" Conformance: This property CAN be specified within a "VEVENT" calendar component. Example: The following is an example of this property: X-SKI-VENUE:Outdoors draft-many-ical-ski-00.txt 3.4 WHERE properties The following properties answer questions about the event such as "Where does it happen?" and "Where do I find the event?". The properties defined in RFC-2445 [3] that the SKiCal working group considers related to WHERE are: 4.8.1.6 Geographic Position (GEO) 4.8.1.7 Location SKiCal objects SHOULD use vCards as ALTREP parameter to the LOCATION property parameter, in order to provide machine readability and maintain information structure when exchanging data. In addition to the properties named above as defined in RFC-2445, a SKiCal object may include the following properties; 3.4.1 Directions Property Name: X-SKI-DIRECTIONS Purpose: This property can be used to specify helpful directions for finding the event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Very often when a public event is published, there are instructions other than the address for finding the location. In metropolitan areas this could be just the name of a subway stop, while on the sea it could possibly be a path defined by a series of GEO (longitude+latitude) coordinates which will help sailors avoid shallow water. Format Definition: The property is defined by the following notation: x-ski-directions = "X-SKI-DIRECTIONS" directionsparam ":" text CRLF directionsparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) / (";" altrepparam ) / (";" travelbyparam) / (";" geo-path) / ; the following is optional, ; and MAY occur more than once (";" xparam) draft-many-ical-ski-00.txt ) travelbyparam = "TRAVELBY" "=" ("walk" / "bicycle" / "boat" / "car" / "rail" / "air" / "public_transportation" / "frequency" / "uri" ) geo-path = "GEO-PATH" "=" 1*(float "," float ",")(float "," float) ; machine readable directions ; coordinate pair sequence approaching destination Example: The following is an example of this property: X-SKI-DIRECTIONS;TRAVELBY=public_transportation;LANGUAGE=se:Tunne lbanestation Globen X-SKI-DIRECTIONS:Rum 207, plan 2 X-SKI-DIRECTIONS;GEO-PATH=17.76545,59.8766,17.76532,59.8755,17.76 525,59.8726;TRAVELBY=walk:Walk the path along the lake, turn lef t after the waterfall, follow yellow signs 3.4.2 Place name Property Name: X-SKI-PLACENAME Purpose: This property can be used to specify a well known name of the place where the event takes place. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Names which have reached a status of common knowledge among a significant portion of the populace (eg. Taxi drivers). If the exact name is chosen from a naming list as discussed in this memo, section 4, further details may be available to the uninitiated. Format Definition: The property is defined by the following notation: x-ski-placename = "X-SKI-PLACENAME" languageparam ":" text CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. Example: The following is an example of this property: X-SKI-PLACENAME;Globen 3.4.3 Media addresses. draft-many-ical-ski-00.txt The European Broadcasting Union, in conjunction with the introduction of new digital television and radio broadcasting, is currently developing a standard for media addresses, such as frequencies and frequency ranges, satellite ranges, cable ranges and so forth. Time permitting, the SKiCal working group hopes to take part of and interact with this work, resulting in recommendations for appropriate properties and property parameters. 3.5 WHOW (HOW) properties WHOW properties are arguably SKiCal's most significant addition to iCal. These properties represent the mechanics of coupling an event seeker to an event, the conditions, rules, qualifications, economics, quirks and hindrances involved. These properties answer questions such as "Can I bring a camera?", "How can I get a ticket?", "Is there an age requirement, or parental guidance?", for example. There is no property defined in RFC-2445 [3] that the SKiCal working group considers related to WHOW. 3.5.1 Qualification for admission Property Name: X-SKI-ADMISSION Purpose: This property can be used to specify a qualification for gaining admission to an event. Note that admission and participation are not the same thing. You may be allowed admittance to a bowling alley but you may be prohibited from actually bowling. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: This property can be used to specify a condition of the attendee. It could be a recommendation, a requirement or the reverse, which helps in the decision as to whether or not the receiver of the SKiCal object whishes to attend the event or not. Format Definition: The property is defined by the following notation: x-ski-admission = "X-SKI-ADMISSION" qualparam ":" text ";" qualifier CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. draft-many-ical-ski-00.txt qualparam = *(";" text) ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. For an example of a qualparam ; list see 4.1 qualifier = *1("REQUIRED" / "NOTREQUIRED" / "RECOMMENDED" / "NOTRECOMMENDED" / "PROHIBITED" / "NOTPROHIBITED" / "ENFORCED" / "NOTENFORCED") Example: The following are examples of this property: X-SKI-ADMISSION;BIRTH-DATE: = 19550403 ;REQUIRED X-SKI-ADMISSION;AGE: gt 7 with adult accompaniment ;REQUIRED X-SKI-ADMISSION;GENDER:Female ;NOTRECOMMENDED X-SKI-ADMISSION;MEMBERSHIP: Lions Club ;REQUIRED X-SKI-ADMISSION;ACCOMPANIEDBY: adult ;REQUIRED X-SKI-ADMISSION;LAWS: Kingdom of Spain ;ENFORCED X-SKI-ADMISSION;CERTIFICATE: Drivers License ;REQUIRED X-SKI-ADMISSION;SKILL:Horse Riding experience ;RECOMMENDED X-SKI-ADMISSION;PRE-BOOKING: lt 20021003 ;REQUIRED X-SKI-ADMISSION;POSSESION-OF: pets ;PROHIBITED X-SKI-ADMISSION;POSSESION-OF: alcohol ;PROHIBITED X-SKI-ADMISSION;TIMESLOT: lt T180000 ;REQUIRED X-SKI-ADMISSION;WEATHER: No rain ;REQUIRED X-SKI-ADMISSION;DEPENDENCIES:Perot wins ;REQUIRED X-SKI-ADMISSION;DEPENDENCIES:gentlemanly contact ;REQUIRED 3.5.2 Qualification for participation Property Name: X-SKI-PARTICIPATION Purpose: This property can be used to specify a qualification for participating in an event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: This property can be used to specify a property of the attendee. It could be a recommendation, a requirement or the reverse, which helps the receiver of the SKiCal object know if they are qualified to participate in the event. Format Definition: The property is defined by the following notation: x-ski-participation = "X-SKI-PARTICIPATION" qualparam ":" text ";" qualifier CRLF ; It is RECOMMENDED that the text value be draft-many-ical-ski-00.txt ; chosen from a list, as described in section 4 ; of this memo. qualparam = *(";" text) ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. For an example of a qualparam ; list see 4.1 qualifier = *1("REQUIRED" / "NOTREQUIRED" / "RECOMMENDED" / "NOTRECOMMENDED" / "PROHIBITED" / "NOTPROHIBITED" / "ENFORCED" / "NOTENFORCED") Example: The following are examples of this property: X-SKI-PARTICIPATION;RESERVATIONS: Personal instructor ;PROHIBITED X-SKI-PARTICIPATION;DEPENDENCIES: Eagles beat Vikings ;REQUIRED X-SKI-PARTICIPATION;HEIGHT gt 150cm ;REQUIRED X-SKI-PARTICIPATION;CERTIFICATE: AAPG ;REQUIRED X-SKI-PARTICIPATION;POSSESSION-OF:Warm clothes ;RECOMMENDED X-SKI-PARTICIPATION;POSSESSION-OF:Warm clothes ;NOTRECOMMENDED X-SKI-PARTICIPATION;POSSESSION-OF:Camera ;PROHIBITED X-SKI-PARTICIPATION;POSSESSION-OF:Ruber soled shoes ;REQUIRED X-SKI-PARTICIPATION;CERTIFICATE:Blood test ;REQUIRED X-SKI-PARTICIPATION;WEATHER:Snow at 200 meter line ;REQUIRED X-SKI-PARTICIPATION;LAWS: Sports Federation ;ENFORCED X-SKI-PARTICIPATION;AREA: Danger Zone ;PROHIBITED X-SKI-PARTICIPATION;PLUS-COSTS: 5USD for entrance to The back room ;REQUIRED X-SKI-PARTICIPATION;TIMESLOTS: gt T180000 ;NOTRECOMMENDED X-SKI-PARTICIPATION;SKILLS: keeping quiet ;ENFORCED 3.5.3 Price Property Name: X-SKI-PRICE Purpose: This property gives pricing information about the event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: This property can be used to provide information about the pricing of an event. Due to the largely divergent pricing structures that exist, perhaps not all aspects of pricing will be possible to represent in a machine readable format using SkiCAl (eg. "Especially for you" prices and negotiable discounts). But at least this attempt will allow for the more easily described structures to be defined. draft-many-ical-ski-00.txt Format Definition: The property is defined by the following notation: x-ski-price = "X-SKI-PRICE" priceparam ":" price CRLF priceparam = *(";" text) / *(";" xparam) ; The text value SHOULD be ; chosen from a list, as described in section 4 ; of this memo. Such a list will probably ; contain words such as: ; Admission ; Breakfast ; Room ; Happy hour ; Monthly fee price = "FREE" / isoprice / ; still in development isoprice = float ; same structure as that defined in W3C micropayments ; specification[6]. Example: The following are examples of this property: X-SKI-PRICE;Admission:FREE X-SKI-PRICE;Admission:+135SEK X-SKI-PRICE;Monthly fee:2.75USD 3.5.4 Ticketing Property Name: X-SKI-TICKETS-AT Purpose: This property defines where and when tickets for the event can be obtained. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. DTSTART and DTEND parameters SHOULD be specified to indicate when tickets are available. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Tickets (or other means needed to attend the event) can often be obtained during a well defined period before the event, or if the event is a recurring, at certain hours from ticketing agents (or directly from the event organizer). Both timing and contact info is valuable to the potential attendee and therefore to the organizer as well. draft-many-ical-ski-00.txt Format Definition: The property is defined by the following notation: x-ski-tickets-at = "X-SKI-TICKETS-AT" ticketparam ":" text CRLF ticketparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) / (";" altrepparam ) / ; the following is optional, ; and MAY occur more than once (";" startparam) / (";" endparam) / (";" xparam) ) startparam = "DTSTART" "=" date-time endparam = "DTEND" "=" date-time Example: The following is an example of this property: X-SKI-TICKETS-AT;DTSTART=19980313T141711Z:Ticketron biljetter X-SKI-TICKETS-AT;DTSTART=19980410;DTEND=19980514;altrep="http\: //www.ticket.com/find.asp?858789":WebTickets X-SKI-TICKETS-AT;DTSTART=19991104:At the ticket booth outside of the concert hall X-SKI-TICKETS-AT;DTSTART=19991104;DTEND=19991214:Telephone: +1- 800-HOCKEYTIX 3.5.5 Reservations Property Name: X-SKI-RESERVATIONS Purpose: This property defines where and when reservations for the event can be obtained. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. DTSTART and DTEND parameters SHOULD be specified to indicate when reservations are available. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Reservations are almost equal to tickets, but usually does not imply the exchange of money. Format Definition: The property is defined by the following notation: x-ski-reservations = "X-SKI-RESERVATIONS" ticketparam ":" text CRLF Example: The following is an example of this property: draft-many-ical-ski-00.txt X-SKI-RESERVATIONS;DTEND=19990514:tel +46 (8) 123 456 3.5.6 Smoking Property Name: X-SKI-SMOKING Purpose: This tells the event seeker what the smoking rules are at the event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Advance notice of the smoking rules at an event. Format Definition: The property is defined by the following notation: x-ski-smoking = "X-SKI-SMOKING" qualparam ":" text ";" qualifier CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. qualparam = *(";" text) ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. For an example of a qualparam ; list see 4.1 qualifier = *1("REQUIRED" / "NOTREQUIRED" / "RECOMMENDED" / "NOTRECOMMENDED" / "PROHIBITED" / "NOTPROHIBITED" / "ENFORCED" / "NOTENFORCED" / Example: The following is an example of this property: X-SKI-SMOKING;AGE: gt 18 ;ACCEPTED X-SKI-SMOKING;LAWS: CALIFORNIA ;ENFORCED X-SKI-SMOKING;AREA: The smoking section ;NOTPROHIBITED X-SKI-SMOKING;TIMESLOTS: DTSTART T230000 ;PROHIBITED 3.5.7 Parking Property Name: X-SKI-PARKING Purpose: This tells the event seeker about the parking facilities. Value Type: TEXT. draft-many-ical-ski-00.txt Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Parking resources. Format Definition: The property is defined by the following notation: x-ski-parking = "X-SKI-PARKING" qualparam ":" text "-" qualifier CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. qualparam = *(";" text) ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. For an example of a qualparam ; list see 4.1 qualifier = *1("AVAILABLE" / "NOTAVAILABLE") Example: The following is an example of this property: X-SKI-PARKING;AREA: behind the restaurant ;AVAILABLE X-SKI-PARKING:;NOTAVAILABLE X-SKI-PARKING;AREA: The parking section ;AVAILABLE X-SKI-PARKING;MEMBERSHIP: Rotarians only ;AVAILABLE 3.5.8 Handicap facilities Property Name: X-SKI-HANDICAP-FACILITIES Purpose: This property defines the accessibility of the event for persons with special needs. Value Type: BOOLEAN. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: People with disabilities and other special needs are among those who have the most to gain from the availability of well structured and therefore easily searchable information about objects in the real world. Especially in parts of the world where law requirements on accessibility are not as high as they are in the United States of America. draft-many-ical-ski-00.txt The SKiCal working group has not been able to find any existing machine readable descriptions about the accessibility of buildings and other potential locations of events. Therefore it is suggested that SKiCal objects have boolean property to indicate the availability of handicap facilities. Format Definition: The property is defined by the following notation: x-ski-handicap-facilities = "X-SKI-HANDICAP-FACILITIES" facilityparam ":" boolean CRLF facilityparam = text / ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. *( ; the following is optional, ; and MAY occur more than once (";" xparam) ) Example: The following are examples of this property: X-SKI-HANDICAP-FACILITIES;wheelchair-ramps:TRUE X-SKI-HANDICAP-FACILITIES;elevator:TRUE 3.5.9 Accepted method of payment Property Name: X-SKI-PAYMENT-METHOD Purpose: This property defines the accepted methods of payment for the event. Value Type: TEXT Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: This property parameter has been explicitly requested by the tourism organizations. The SKiCal working group has not finished discussions about how this is to be represented. Example: The following are examples of this property: X-SKI-PAYMENT-METHOD:VISA X-SKI-PAYMENT-METHOD:SET 3.5.10 Rules for the consumption of alcohol draft-many-ical-ski-00.txt Property Name: X-SKI-ALCOHOL Purpose: This tells the event seeker what about the availability of alcohol and the rules governing its consumption at the event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Advance notice of the alcohol rules at an event. Format Definition: The property is defined by the following notation: x-ski-alcohol = "X-SKI-ALCOHOL" qualparam ":" text ";" qualifier CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. qualparam = *(";" text) ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. For an example of a qualparam ; list see 4.1 qualifier = *1("REQUIRED" / "NOTREQUIRED" / "RECOMMENDED" / "NOTRECOMMENDED" / "PROHIBITED" / "NOTPROHIBITED" / "ENFORCED" / "NOTENFORCED") Example: The following is an example of this property: X-SKI-ALCOHOL;AGE: gt 21 ;ALLOWED X-SKI-ALCOHOL;LAWS: CALIFORNIA ;ENFORCED X-SKI-ALCOHOL;AREA: The Royer Lounge ;AVAILABLE X-SKI-ALCOHOL;AREA: The Mansour Room ;NOTAVAILABLE X-SKI-ALCOHOL;TIMESLOTS: DTSTART T240000 ;PROHIBITED X-SKI-ALCOHOL;CERTIFICATE: positive ID ;PROHIBITED 3.5.11 Food Property Name: X-SKI-FOOD Purpose: This tells the event seeker what the availability of food at the event and/or the rules for its consumption. Value Type: TEXT. Property Parameters: Non-standard property parameters can be draft-many-ical-ski-00.txt specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Advance notice of the food rules at an event. Format Definition: The property is defined by the following notation: x-ski-food = "X-SKI-FOOD" qualparam ":" text ";" qualifier CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. qualparam = *(";" text) ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. For an example of a qualparam ; list see 4.1 qualifier = *1("REQUIRED" / "NOTREQUIRED" / "RECOMMENDED" / "NOTRECOMMENDED" / "PROHIBITED" / "NOTPROHIBITED" / "ENFORCED" / "NOTENFORCED") Example: The following is an example of this property: X-SKI-FOOD: ;AVAILABLE X-SKI-FOOD:Chinese, Vietnamese, Thai ;AVAILABLE X-SKI-FOOD: Vegetarian ;NOTAVAILABLE X-SKI-FOOD;PLUSCOST: night time snack ;AVAILABLE X-SKI-FOOD;AREA: The pews ;PROHIBITED X-SKI-FOOD;TIMESLOTS: DTSTART T230000 ;NOTAVAILABLE 3.5.12 Transportation Property Name: X-SKI-TRANSPORTATION Purpose: This tells the event seeker what the availability of transportation to the event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Advance notice of the transportation possibilities for getting to an event . draft-many-ical-ski-00.txt Format Definition: The property is defined by the following notation: x-ski-transportation = "X-SKI-TRANSPORTATION" ";" travelbyparam qualparam ":" text ";" qualifier CRLF ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. travelbyparam = "TRAVELBY" "=" ("walk" / "bicycle" / "boat" / "car" / "rail" / "air" / "public_transportation" / "frequency" / "uri" ) qualparam = *(";" text) ; It is RECOMMENDED that the text value be ; chosen from a list, as described in section 4 ; of this memo. For an example of a qualparam ; list see 4.1 qualifier = *1("REQUIRED" / "NOTREQUIRED" / "RECOMMENDED" / "NOTRECOMMENDED" / "PROHIBITED" / "NOTPROHIBITED" / "ENFORCED" / "NOTENFORCED" Example: The following is an example of this property: X-SKI-TRANSPORTATION;TRAVELBY=public_transportation: ;AVAILABLE X-SKI-TRANSPORTATION:Bus from downtown every half hour ;AVAILABLE X-SKI-TRANSPORTATION: Public ;RECOMENDED X-SKI-TRANSPORTATION;PLUSCOST: limousines ;AVAILABLE X-SKI-TRANSPORTATION;AREA: steam train around the perimeter ;RECOM ENDED X-SKI-TRANSPORTATION;TRAVELBY=Nightbus;TIMESLOTS:DTSTART T230000 ; NOTAVAILABLE X-SKI-TRANSPORTATION;TRAVELBY=extra trains;DEPENDENCIES: if overb ooked ;AVAILABLE 3.6 WHY properties The following properties answer questions about the event such as "Why should I attend?" and "Why would this be interesting?". WHY gathers promotional, instructive, informational material under one roof. The SkiCal WG has an ulterior motive for doing so. Many of the up and coming SKiCal applications will be operating in a narrow bandwidth environment, this is specially the case with mobile browsers. By placing content which might be bulky and bandwidth consuming in a specifically defined area of the Calendar Object, the event seeker as well as the event publisher is given greater control in separating lightweight "prima vista" data transfers from heavyweight "the whole picture" data transfers. draft-many-ical-ski-00.txt There is no property defined in RFC-2445 [3] that the SKiCal working group considers related to WHY. 3.6.1 Motivation Property Name: X-SKI-MOTIVATION Purpose: This property allows for the organizer of the event to publish subjective information about the event. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: Short textual information, basically the sales pitch for an event. Must not be longer than 255 characters. Format Definition: The property is defined by the following notation: x-ski-motivation = "X-SKI-MOTIVATION" motivationparam ":" text CRLF motivationparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) / (";" encodingparam ) / ; the following is optional, ; and MAY occur more than once (";" xparam) ) Examples: The following are examples of this property: X-SKI-MOTIVATION;LANGUAGE=en:This is going to be a great party. Ev erybody will be there. If you're not - you will regret it. X-SKI-MOTIVATION;LANGUAGE=sv;ENCODING=QUOTED-PRINTABLE:F=F6rbundet firar bara 60 =E5r en g=E5ng. 3.6.2 Promotion Property Name: X-SKI-PROMO Purpose: This property allows for the organizer of the event to refer to advertising material, in various forms. Value Type: URI Property Parameters: Non-standard property parameters can be draft-many-ical-ski-00.txt specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: This property could be a link to online versions of a movie trailer, a web campaign, a radio spot or a newspaper ad. Format Definition: The property is defined by the following notation: x-ski-promo = "X-SKI-PROMO" ":" uri CRLF Example: The following is an example of this property: X-SKI-PROMO:http://www.stadsteatern.se/affischer/othello2000.gif X-SKI-PROMO:http://www.torget.se/kampanj/julsonger.i.huset.html 3.6.3 Third party review Property Name: X-SKI-REVIEW Purpose: This property allows for the organizer of the event to refer to third party information about the event. Value Type: URI Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: This property could be a link to a review, a rating, or other third party comment on the event being described by the SKiCal object. Format Definition: The property is defined by the following notation: x-ski-review = "X-SKI-REVIEW" languageparam ":" uri CRLF Example: The following is an example of this property: X-SKI-REVIEW;LANGUAGE=en:http://www.alltomstockholm.se/reviews/12/ X-SKI-REVIEW:http://www.dn.se/literatur/990505.html 3.7 WHO properties The following properties answer questions about the event such as "Who is responsible for the event?". They refer to the organizer of the event. It is important to clearly establish the "WhoDoUsue" for each event. draft-many-ical-ski-00.txt The properties defined in RFC-2445 [3] that the SKiCal working group considers related to WHO are: 4.8.4.2 Contact It is RECOMMENDED that SKiCal objects use vCards as ALTREP parameter to the CONTACT property parameter, in order to provide machine readability and maintain information structure when exchanging data. In addition to the properties named above as defined in RFC-2445, a SKiCal object may include the following properties; 3.7.1 Responsible Property Name: X-SKI-RESPONSIBLE Purpose: This property indicates who is responsible for the event. Value Type: TEXT. (MAILTO) Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: In some countries, any planned public event with more than 5 persons attending must have a person or an organization which is legally responsible for the event. Any public business must have a person who is legally responsible for that business. We call these responsible persons and organization the "WhoDoUsue". This property is intended to identify and define the WhoDoUsue. Format Definition: The property is defined by the following notation: x-ski-responsible = "X-SKI-RESPONSIBLE" resonsibleparam ":" uri CRLF ; the value MUST be a MAILTO URI, as defined ; by RFC-1738 [7]. responsibleparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) / (";" cnparam ) / ; the following is optional, ; and MAY occur more than once (";" xparam) ) Example: The following is an example of this property: draft-many-ical-ski-00.txt X-SKI-RESPONSIBLE;CN=Nobelkommitten:MAILTO:info@nobel.se X-SKI-RESPONSIBLE;CN=Opera house:MAILTO:info@opera.de X-SKI-RESPONSIBLE:MAILTO:jean-marie@petiteville.fr 3.7.2 Other agents Property Name: X-SKI-OTHERAGENTS Purpose: This property is intended to identify persons and organizations which are in some way contributing to the event, but not as the main WhoDoUsue. Value Type: TEXT. (MAILTO) Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: At football games, for example, there are often several organizations involved: The owner of the stadium, the two teams, the ticketing agency and sometimes the organizer of a tournament. This property makes it possible to indicate all of these organizers, not to be confused with the legally responsible organizer. Examples: The following are examples of this property: X-SKI-OTHERAGENTS:MAILTO:info@ematelstar.se X-SKI-OTHERAGENTS;CN=Stockholms stad:MAILTO:kultur@stadshuset.a.se 3.7.3 Association Property Name: X-SKI-ASSOCIATION Purpose: This property can be specified to indicate organizations of which the organizer is a member. Value Type: TEXT. Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: If, for example, a little known organizer of an event is a member of a well known organization, this information will be very valuable to anybody considering to participate. We expect that this information will be verifiable with an online authoritative source Format Definition: The property is defined by the following notation: draft-many-ical-ski-00.txt x-ski-association = "X-SKI-ASSOCIATION" associationparam ":" uri CRLF ; the value MUST be a MAILTO URI, as defined ; by RFC-1738 [7]. associationparam = *( ; the following is optional, ; but MUST NOT occur more than once (";" languageparam ) / (";" cnparam ) / ; the following is optional, ; and MAY occur more than once (";" xparam) ) Example: The following are examples of this property: X-SKI-ASSOCIATION;CN=Svenska Turistforbundet:MAILTO:info@stf.se X-SKI-ASSOCIATION;CN=Rotary international:MAILTO:rotary@rotary.org 3.8 MANAGEMENT properties The above SKiCal component properties all describe the event itself (description) and not, as is the case with many iCalendar component properties, the entry in a calendar user agent (CUA) or calendar server (CS) (self-description). It is possible that several, or even many calendar objects could refer to the same event. And each of these calendar objects could have their own publisher. While the event has only one responsible authority. It is the ambition of the SKiCal WG to empower the event with the same means of identification and validation as the Calsch WG has given the calendar object. A point in case is the property: 4.8.4.3 ORGANIZER, which as described in RFC-2445 defines the organizer for a calendar component - not the organizer for the event. SKiCal would have preferred to call this property PUBLISHER and retain the term ORGANIZER for the actual organizer of the event itself. In lieu of this happening we are using the term RESPONSIBLE for the Event's WhoDoUsue and recommend the term PUBLISHER for the publisher of the Calendar object. The properties defined in RFC-2445 [3] that the SKiCal working group considers related to MANAGEMENT are: 4.8.1.3 Classification 4.8.1.4 Comment 4.8.1.11 Status draft-many-ical-ski-00.txt 4.8.4.3 Organizer 4.8.4.5 Related-to 4.8.4.6 Uniform Resource Locator 4.8.4.7 Unique Identifier 4.8.5 Recurrence Component Properties 4.8.7.1 Date/Time Created 4.8.7.2 Date/Time Stamp 4.8.7.3 Last Modified 4.8.7.4 Sequence Number 3.8.1 Checksum Property Name: X-SKI-CHECKSUM Purpose: This parameter can be used to confirm that the calendar object remains unaltered. Value Type: INTEGER Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. Description: This property is not yet fully defined. Format Definition: The property is defined by the following notation: x-ski-checksum = "X-SKI-CHECKSUM" ":" calculatedsum CRLF calculatedsum = ; Work in progress Example: The following is an example of this property: X-SKI-EVENT-CHECKSUM:948 3.8.2 Publisher Property Name: X-SKI-PUBLISHER Purpose: Describes the organization which publishes the event object. Value Type: URI Property Parameters: Non-standard property parameters can be specified on this property. Conformance: This property CAN be specified within a "VEVENT" calendar component. draft-many-ical-ski-00.txt Description: In the case of public events, the organizer of an event is not always the one who makes the information about the event available. Format Definition: The property is defined by the following notation: x-ski-publisher = "X-SKI-PUBLISHER" ":" mailto CRLF Example: The following is an example of this property: X-SKI-PUBLISHER:mailto:info@timeout.co.uk 4 Choosing values from lists It is RECOMMENDED that text values be chosen from "authoritative naming lists" whenever possible. Doing this, the publisher will increase the level of machine readability and thus increase the accumulated global value of all iCalendar/SKiCal objects. It is expected that such lists will become widely available and accessible online, possibly in the RDF [8] format. The informal SKiCal working group is looking into this possibility, but the design of this is not further elaborated in this memo. One example of such a naming list is the list of words describing tourist resources, which is being published by the European Tourist Councils. Each entry in this list has a translation into all European languages, and events using entries from this list as values of the Categories property may therefore be correctly presented in event databases all around Europe (provided that the software knows how to fetch the translation from the list). Another example is the Olson database of time zones, as mentioned in RFC-2445, section 4.8.3.1. 4.1 List example for qualparam SkiCal sorts qualification parameters under the following headings: Attendee related parameters: a) the physical attributes of the attendee. Visible, roughly apparent. AGE BIRTH-DATE GENDER HEIGHT WEIGHT ;extensions of this list could also include attributes ;such as blood type, hair color, biceps measurements ;and so forth. draft-many-ical-ski-00.txt b) Knowledge-level/position/ownership status that the attendee has obtained and/or documents which the attendee might possess for the purpose of verifying that status SKILL ; implies a level of physical/intellectual attainment MEMBERSHIP ; implies the existence of a verifiable list or an ; event officials first ; hand knowledge that the attendee belongs to a certain ; group of organization CERTIFICATE ; credentials of proof that the attendee meets ; with criteria specified by the Event Organizers. ; Both SKILL and MEMBERSHIP might be verified by a ; CERTIFICATE which the attendee is carrying or they ; might be verifiable on-line or from a list at the ; "gate", or the attendee may be trusted to be self- ; verifying. c) what an attendee has in her possession. POSSESSION-OF ; This parameter is about physical objects e.g. guns, ; cameras, water bottles, binoculars, warm clothes, ice ; skates, bathing suits, literature, and animals which ; the event seeker would or would not have in their ; possession when attending the event. External factor parameters: d) responses to Natural conditions WEATHER e) relationship to legal jurisdiction LAWS f) relationship to external events DEPENDENCIES Event related parameters: g) specific sub-divisions of WHERE AREA f)specific sub-divisions of WHEN draft-many-ical-ski-00.txt TIMESLOTS Transactional parameters: h) additional costs PLUS-COSTS e) reservation rules PRE-BOOKING RESERVATIONS 5 Intended use The exchange and proliferation of event related information. Event organizers can publish their information (for example on web servers), in the SKiCal format as defined by this memo. This will enable calendar publishers to launch software spiders that collect this information. This eliminates the need for publishers to manually enter the information into their databases, and makes it much easier for event organizers to get their information across to the eventual interested audience. 5.1 Differences between SKiCal and iCalendar. Here are some of the major differences between the potential users of iCalendar (iCal) and SKiCal. A typical iCal user will consider their Calendar application an important, if not indispensable, tool in their interaction with fellow workers in the same company - or same cross-company project. Most SKiCal users will not use a computer based calendar program more than casually, if at all. iCal objects will invariably end up in a user's calendar. SKiCal objects will more likely be printed in newspapers & print-on-demand compilations, presented in mobile browsers (WAP) and desktop browsers, shown on text television, auto-voiced over telephones, pushed or called-up through an assortment of yet to be invented digiphernalia. Most iCal objects will be created by known organizers, for known attendees, of a known quantity, meeting in known places, dealing with known topics. Many SKiCal objects will be created by unknown organizers, for unknown attendees, of an unknown quantity, meeting in unknown places, to take part in unknown events. SKiCal users will typically search for certain property combination outcomes amongst millions of possible property combinations. iCal users will be invited to join in on specific events, many of which will not come as a surprise. draft-many-ical-ski-00.txt SKiCal knowledge retrieval processes will be both and crisp and fuzzy. iCal processes will almost always be crisp. A SKiCal object is always the description of an external (to the SKiCal object) thing. An iCal object will often be self descriptive with some references to external things, such as a meeting room. 6 Security considerations Anybody could produce a SKiCal compliant file containing false information. Calendar publishers will need to be cautious, or they may end up publishing invalid information. Security can be achieved either by choosing to index SKiCal files only from trusted servers, or by employing a moderator who can correct or refuse corrupt information. Nobody should consider information from non-encrypted SKiCal files 100% reliable, just as nobody should blindly trust printed advertisements or email. More reliable information can be expected once safe connections to electronic commerce solutions are established. Event organizers and publishers should be aware of legal implications from spreading personal information in electronic media. 7 Internationalization/localization Text valued properties containing non-us-ascii characters should be properly encoded with base-64 or quoted-printable, as specified in [3]. Timezones are handled with VTIMEZONE components, as specified in [3]. 8 References 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997 3 RFC-2445, Dawson, F. and D. Stenerson, "Internet Calendaring and Scheduling Core Object Specification - iCalendar", November 1998. 4 RFC-2234 Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", November 1997. 5 RFC-1766, Alvestrand, H., "Tags for the Identification of Languages", March 1995. 6 "Common Markup for Web Micropayment Systems", Thierry Michel, W3C Working Draft, 9 June 1999, http://www.w3.org/TR/WD-Micropayment- Markup/#Price draft-many-ical-ski-00.txt 7 RFC-1738, Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform Resource Locators (URL)", December 1994. 8 Resource Description Framework (RDF) Model and Syntax Specification, O. Lassila and R. Swick, W3C Recommendation, February 1999, http://www.w3.org/TR/REC-rdf-syntax 9 Greg FitzPatrick, August 1999, "DIP and DOP", http://www.skical.org/ftp/dip%20and%20dop.ppt 9 Acknowledgments The following persons have contributed to the specification of the SKiCal format: Ingemar Eriksson of the Swedish Travel & Tourism Council, the Event Working group at Stockholm Information Service, Johan Hjelm of Ericsson/W3C, Patrik Faltstrom of Tele2, Jenny Pileus of the Swedish_Nationwide Theatre (Riksteatern), Benny Regner of the National Agency for Education, Bengt Wittstrom of the Swedish National Board of Culture, Ulla Persson of the Swedish Sports Confederation, Stefan Johansson of Handikapp.se (special needs organizations' confederation for ICT related issues), Ingvar Hallgren of the Swedish Concert Institute (Rikskonserter), Stanley Almqvist of Crossnet AB, Daniel Bergstrom of Melody AB, Lars Aronsson of Spray AB, Mary Omming of Utbildningsradion (public service educational TV channel), NUTEK and of course Frank Dawson of Lotus, Doug Royer of Sun Microsystems, Steve Mansour of Netscape Communications, Paul B Hill of the MIT , Lisa Lippert of Microsoft, Patricia Egen of Egen consulting, and the other members of the CALSCH WG. 10 Authors' addresses Greg FitzPatrick Medianet Niklas Hjelm Medialab AB/Soft Applications AB Par Lannero Svenska Kalenderinitiativet Full Copyright Statement "Copyright (C) The Internet Society (1999). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this draft-many-ical-ski-00.txt document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. draft-many-ical-ski-00.txt Expires 2000-03-13