- From: Sanja Bonic <sanja@cv2.me>
- Date: Mon, 24 Aug 2015 04:30:48 +0200
- To: public-cv2@w3.org
- Message-ID: <CABSZ4K2_4s0aXQjb1b7UqHhBVRmwbVOoa3xtzwx5E5C0q3O1gA@mail.gmail.com>
FYI: I apologize - my mouse moved from the table and while trying to catch it my hand pressed several buttons including the Send button! I could not edit my previous e-mail and I wasn't finished yet - but I hope it is still relatively clear why the inital proposal is what it is. Here is a small edit to my last e-mail, regarding this part: -------------------------------------------------- what content would the .cv2 have? -------------------------------------------------- First, we would work on tags. Tags that are close to schema.org types, except that we use the properties as tags and cut out all the additional bulk. Instead of the above schema.org-injected HTML we would have <person> <name>Scrooge McDuck <streetAddress>W3C Headquarters <organization> <name>CV 2.0 Community Group <jobtitle>Participant <description>... You get my point - there are several ways we could achieve this simplicity but I am in no way forcing a new file format. Instead, I would rather invite a discussion about our options without losing the vision of the possibilities for a next-gen resume style. Is there anyone else who would like to offer some input? We are trying to reach consensus decisions if possible.
Received on Monday, 24 August 2015 02:31:17 UTC