# The following variables need to be adapted by you: # JJJJ=Year in which the final papers of the proceedings were produced # YYYY=Year in which the workshop took place (in most cases YYYY=JJJJ) # NNNN=Acronym of the Workshop # DD=Day of submission of the workshop proceedings to CEUR-WS.org # MM=Month of submission of the workshop proceedings (MM=01,02,03,04,05,06,07,08,09,10,11,12) # The variable # XXX=Volume number of the proceedings with CEUR-WS.org # shall be adapted by CEUR-WS.org. CEUR-WS.org shall also set the publication date. # # # (*) Replace title of the workshop in the title element # (*) Replace title of the workshop in the heading h1 element # (*) Note that the style file ceur-ws.css and the image CEUR-WS-logo.png are referring to files within # the CEUR-WS.org web site; they are not part of the submission directory # (*) the lines starting with # shall be removed by you when preparing the file index.html # # Some elements are tagged with a "class=CEUR..." clause. Be careful to maintain these tags! # They are used both for formatting purposes and for identifying bibliographic elements. # The CEUR class tags are as follows: # CEURLANG: the main language of the proceedings (eng, ger, fre, spa, rus, ita, por, ...) # CEURVOLNR: the volume number of the proceedings **set by us** # CEURPUBYEAR: the year in which the proceedings volume was created (see also YYYY) # CEURURN: the URN of the volume **set by us** # CEURVOLACRONYM: the acronym of the workshop plus YYYY (year of the workshop) # the acronym may contain '-'; between acronym and year is either a blank # or a '-'. The year is exactly 4 digits, e.g. 2012 # CEURVOLTITLE: the title of the proceedings # CEURFULLTITLE: the long title of the proceedings # CEURCOLOCATED: the acronym and year of the conference where this workshop was # co-located with; use "NONE" if the workshop was not co-located with a conference # CEURLOCTIME: the place and time when the workshop took place # CEURVOLEDITOR: full name of an editor of the proceedings # CEURTOC: indicator for the start of the table of contents # CEURSESSION (optional): separator for a section within the table of contents # CEURTITLE: title of a paper within the table of contents # CEURPAGES (optional): numerical range of pages of a paper, e.g. 10-20 # CEURAUTHORS: comma-separated list of authors of a paper (use full names, do not include affiliations) # CEURPUBDATE: the precise date of publication at CEUR-WS.org **set by us** # # AUXTITLE,AUXPAGES,AUXAUTHORS: like their CEUR-counterparts but not to be indexed by DBLP # AUXSESSION: like CEURSESSION but will be ignored for indexing; use for sessions where all # papers are described by AUX tags #
# The layout of the proceedings title can be adapted to your needs. # Make sure to include all proceedings editors and their affiliations. # Links to home pages are fine but not required. Some workshops have # a special logo. This could be included here as well. But avoid logos # of sponsors. #
# use full names, but omit any academic title
# The table of contents normally is a plain list of papers (with titles/authors). # The paper title should be linked to the paper URL (usually pdf). # You may include "session" subsections e.g. to reflect the track structure of your workshop. # Authors should be specified as comma-separated lists with full author names # (like John Smith). Avoid glue words like 'by' and 'and'. If applicable, then lookup how # the author is spelled out by DBLP. # You may also provide additional material such as preface, bibtex files, complete # proceedings as a single pdf, and similar items. The additional items should be # clearly separated from the paper list, preferably after the table of contents. # Please only tag original papers with the CEURTITLE/CEURAUTHORS scheme. Rather do not tag # additional material with this scheme! # For the time being, presentation slides should also not be tagged by CEURTITLE/CEURAUTHORS. #
# Each CEURSESSION must be followed by at least one paper using the li clause # You can also use h3 subtitles without the CEURSESSION tag. Then, no # restriction is imposed. #
# paper links must follow directly the li element. Note that special characters like accents must be specified in their HTML command form! # intro2.pdf is an example of a multi-page paper with page numbers
# The following examples are only for exceptional cases; please only provide such items if # you believe they are essential; these items are supposed to be NOT indexed by DBLP and # other digital library services! Use AUXSESSION if all items are tagged by AUXTITLE; # otherwise, use CEURSESSION # # The first item is an example of a paper that is not included as full text. Such entries are regarded more as a comment rather than a part of the table of contents. # The second item (paper6-copy.pdf) is an example of an extended abstract whose full version was published elsewhere