This post is a proposal on parts of the .cv2 syntax for the CV 2.0. Things will still be missing and we need to discuss more in order to create a specification, so feel free to join in on the discussion via the mailing list.<\/p>\n
\\\\ 2 backslashes for section start<\/mark><\/p>\n Additional information for a section can be added anywhere into the .cv2. The parser will recognize everything from a beginning \\\\ to the next \\\\ as one section. If two sections are the same, the properties will be recognized as belonging to the same section. Newer (i.e. further down in the file) values will replace older values if they address the same tag, much like cascading stylesheets.<\/p>\n \/* comments *\/<\/mark> <\/p>\n \\{} Special Characters and Escaping Characters<\/mark><\/p>\n The above example syntax is borrowed from LaTeX, although Umlauts and other symbols should be recognized since .cv2 will have UTF-8 encoding as requirement in our specification, so there should only be the need to escape, for example, company names with two backslashes in them or other names that interfere with our .cv2 syntax which should happen rarely if at all. Anything that is input via a form needs to be sanitized and escaped correctly. This is a main security point in our specification.<\/p>\n “Values spanning<\/mark><\/p>\n several lines”<\/mark> [] Enumerations and Value Ranges<\/mark> Enumerations and value ranges are created using name: [x-y]<\/mark> for value ranges or name: [a, b, c, d, \u2026]<\/mark>\u00a0for enumerations and must be created before their first reference. They can be addressed via the usual escaping\/referencing syntax: \\{name:value}<\/mark><\/p>\n We will still have to define most tag names. Some tag names are suggested in the\u00a0Notes<\/a>\u00a0post, such as: faoname<\/strong> stands for “For Attention Of” as used in letters and is used to designate the proper salutation. We cannot use first and last name since many cultures around the world use a different concept and people need their full name on their resume as well as some option to tell how they would prefer to be addressed.<\/p>\n Some properties have multiple tags, such as jobs and education. The choice is to either group them in parentheses, making them harder to separate or concatenate anywhere else in the document and also harder to read eventually. So the approach is to treat them similarly to objects in a programming language, addressing the property followed by a dot and the tag. Example:<\/p>\n The Alias concept has been borrowed from SQL and can be used for any multi-tag properties. Aliases must be created for user-defined properties such as skills or custom tags. Example:<\/p>\n Cross-referencing is very important for the visualizations so additional links can be clearly shown and visualized in various ways, for examples skills can be linked to jobs or jobs to education, etc. Example:<\/p>\n The syntax for cross-references is \\{tagname}<\/mark> including the cross-referenced tag name in the curly brackets.<\/p>\n URLs and external files like pictures and logos can be added to a .cv2 using \\{externaltag}<\/mark> where “externaltag” for now only has the options of url:<\/mark>, mailto:<\/mark>, and file:<\/mark>. Example:<\/p>\n According to the charter (section Decision Process), we need a group consensus or at least a 2\/3 majority vote on this proposal where agreement as well as silence implies consensus.<\/p>\n If no objections arrive by October 11th<\/sup> 2015<\/strong>, this proposal is regarded as accepted. A small reminder: if you agree, please reply to the public mailing list – if all participants agree or disagree\u00a0before the 11th<\/sup> of October, we can already move forward with our work. Thank you!<\/p>\n","protected":false},"excerpt":{"rendered":" This post is a proposal on parts of the .cv2 syntax for the CV 2.0. Things will still be missing and we need to discuss more in order to create a specification, so feel free to join in on the … Continue reading \\\\ Personal\r\n...\r\n\r\n\\\\ Professional\r\n...\r\n\r\n\\\\ Education\r\n...\r\n\r\n\\\\ Skills\r\n...\r\n\r\n\\\\ Personal\r\n...\r\n<\/pre>\n
\nAs usual in many programming languages, comments can be added in between a slash, asterisk – asterisk, slash combination. Example:<\/p>\n\/* comments optional - filename: john_doe_timestamp.cv2 *\/<\/pre>\n
\/* a name with umlaut as an example of how to escape characters *\/\r\nfullname: John D\\{\"o}e\r\n<\/pre>\n
\nAs newline is our ending character, we need a sign to tell the parser that a\u00a0value spans several lines. Example:<\/p>\nj1.description: \"this text spans several lines and is rendered similar\r\nto the pre tag in HTML - preserving line breaks\"<\/pre>\n
\nEnumerations and value ranges are important for custom tags that are defined by the user and have no defined meaning as well as value ranges for skills in order to create visualizations and charts. Example:<\/p>\n\\\\ Skills\r\nCSS AS css\r\nJava AS java\r\nProject Managemenet AS pm\r\n \r\nscale1: [0-100]\r\nscale2: [Beginner, Intermediate, Expert]\r\n \r\ncss.level: \\{scale1:67}\r\ncss.category: markup languages\r\n \r\njava.level: \\{scale1:85}\r\njava.category: programming languages\r\n \r\npm.level: \\{scale2:Expert}\r\npm.category: organizational\r\n<\/pre>\nTag Names<\/h2>\n
\nfullname, faoname, email, birthDate, birthLocation, citizenship, name, dateStart, dateEnd, role, description, degree, level, category, \u2026<\/p>\nMulti-Tag Properties<\/h2>\n
j1.name: Some Company Name\r\n<\/pre>\n
Aliases<\/h2>\n
job1 AS j1\r\n\r\nj1.name: Some Company Name\r\nj1.dateStart: date in format dd.mm.yyyy\r\n<\/pre>\n
Cross-References<\/h2>\n
j2.description: \"created blah, e-mail me: \\{email}\"\r\nj2.additionalInfo: some more blah, had a contract for \\{j1} while doing this<\/pre>\nURLs and External Files<\/h2>\n
j2.description: \"created \\{url:http:\/\/blabla.org} in this job,\r\nemail to \\{mailto:myaddress@here.com} for questions\"<\/pre>\nFYI<\/h2>\n