<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: faenor</title>
    <description>The latest articles on DEV Community by faenor (@faenor).</description>
    <link>https://dev.to/faenor</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F5799%2F2397128.png</url>
      <title>DEV Community: faenor</title>
      <link>https://dev.to/faenor</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/faenor"/>
    <language>en</language>
    <item>
      <title>Standards/RFCs a web-dev should know about!?</title>
      <dc:creator>faenor</dc:creator>
      <pubDate>Sat, 13 Mar 2021 23:36:29 +0000</pubDate>
      <link>https://dev.to/faenor/standards-rfcs-a-web-dev-should-know-about-2dk</link>
      <guid>https://dev.to/faenor/standards-rfcs-a-web-dev-should-know-about-2dk</guid>
      <description>&lt;h3&gt;
  
  
  &lt;a href="https://en.wikipedia.org/wiki/ISO_8601"&gt;ISO8601 Date + Duration + Time Interval&lt;/a&gt;
&lt;/h3&gt;

&lt;p&gt;This one will be very familiar to a lot of you. I guess this is the format that is most commonly used for date/timestamp representation. But despite that, many people don't know that this standard also defines a format for durations and time intervals.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;a href="https://tools.ietf.org/html/rfc6749"&gt;OAuth&lt;/a&gt;
&lt;/h3&gt;

&lt;p&gt;The OAuth spec is an authorization framework that describes how a third-party app can access resources own behalf of a user. It has various flows depending on the trustworthiness or the use case of the developed client. OAuth is used by many well known names that also function as authorization provider.&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;a href="https://tools.ietf.org/html/rfc7946"&gt;geoJSON&lt;/a&gt;
&lt;/h3&gt;

&lt;p&gt;Describes a format based on JSON that is used to interchange geospatial data. &lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;a href="https://tools.ietf.org/html/rfc5545"&gt;iCalendar&lt;/a&gt; / &lt;a href="https://tools.ietf.org/html/rfc7265"&gt;jCal&lt;/a&gt;
&lt;/h3&gt;

&lt;p&gt;Often seen as iCal or &lt;code&gt;.ics&lt;/code&gt; files, iCalendar is a specification to exchange calendar and scheduling information. There is a variety of use cases where this format is used (calendar events, to-dos, journal entries, and free/busy information for e.g. meeting rooms). So if you accept a meeting invitation and put it into your calendar app, there is a good chance it was sent in iCalendar format.&lt;/p&gt;

&lt;p&gt;(jCal is the JSON representation)&lt;/p&gt;

&lt;h3&gt;
  
  
  &lt;a href="https://tools.ietf.org/html/rfc6350"&gt;vCard&lt;/a&gt; / &lt;a href="https://tools.ietf.org/html/rfc7095"&gt;jCard&lt;/a&gt;
&lt;/h3&gt;

&lt;p&gt;These rfc describes a format for exchanging a variety of information about individuals (name, phone number, email, etc...). If you want to share a contact from your smartphone, often vCard is used to share that infos.&lt;/p&gt;

&lt;p&gt;(jCard is again the JSON representation)&lt;/p&gt;




&lt;p&gt;What standards/rfcs am I missing that you use in your daily work? Let me know&lt;/p&gt;

</description>
      <category>discuss</category>
      <category>webdev</category>
      <category>learning</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
