idnits 2.17.1 draft-dumler-jsresume-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 30, 2020) is 1428 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Independent Submission M. Dumler 3 Internet-Draft University of Texas at Dallas 4 Intended status: Standards Track April 30, 2020 5 Expires: November 1, 2020 7 JSResume: A JSON representation of resume data 8 draft-dumler-jsresume-00 10 Abstract 12 This specification defines a data model and JSON representation of 13 resume data that can be used for storage and data exchange in human 14 resource and professional networking applications. 16 Status of This Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 Internet-Drafts are working documents of the Internet Engineering 22 Task Force (IETF). Note that other groups may also distribute 23 working documents as Internet-Drafts. The list of current Internet- 24 Drafts is at https://datatracker.ietf.org/drafts/current/. 26 Internet-Drafts are draft documents valid for a maximum of six months 27 and may be updated, replaced, or obsoleted by other documents at any 28 time. It is inappropriate to use Internet-Drafts as reference 29 material or to cite them other than as "work in progress." 31 This Internet-Draft will expire on November 1, 2020. 33 Copyright Notice 35 Copyright (c) 2020 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (https://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. Code Components extracted from this document must 44 include Simplified BSD License text as described in Section 4.e of 45 the Trust Legal Provisions and are provided without warranty as 46 described in the Simplified BSD License. 48 Table of Contents 50 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 51 2. Security Considerations . . . . . . . . . . . . . . . . . . . 2 52 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 53 4. References . . . . . . . . . . . . . . . . . . . . . . . . . 2 54 4.1. Normative References . . . . . . . . . . . . . . . . . . 2 55 4.2. Informative References . . . . . . . . . . . . . . . . . 2 56 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 58 1. Introduction 60 This document defines a data model for resume data in electronic 61 human resource and professional networking applications and systems. 63 Comments are solicited and should be addressed to the author(s). 65 The representation of this data model is defined in the I-JSON format 66 [RFC7493], which is a strict subset of the JavaScript Object Notation 67 (JSON) Data Interchange Format [RFC8259]. Using JSON is mostly a 68 pragmatic choice: its widespread use makes JSResume easier to adopt, 69 and the availability of production-ready JSON implementations 70 eliminates a whole category of parser-related interoperability 71 issues. 73 2. Security Considerations 75 TBD 77 3. IANA Considerations 79 TBD 81 4. References 83 4.1. Normative References 85 [RFC7493] Bray, T., Ed., "The I-JSON Message Format", RFC 7493, 86 DOI 10.17487/RFC7493, March 2015, 87 . 89 4.2. Informative References 91 [RFC8259] Bray, T., Ed., "The JavaScript Object Notation (JSON) Data 92 Interchange Format", STD 90, RFC 8259, 93 DOI 10.17487/RFC8259, December 2017, 94 . 96 Author's Address 98 Matt Dumler 99 University of Texas at Dallas 100 800 W Campbell Rd 101 Richardson TX 750230 102 United States of America 104 Phone: +1469-878-1470 105 Email: mattd3v@protonmail.com