reiver
/
reiver-frames-protocol
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

initial commits

master
Charles Iliya Krempeaux 2024-02-04 16:04:56 -08:00
parent 263d55f6aa
commit dca9f1bad0
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
index.xhtml
View File

@ -82,26 +82,26 @@ The following is <b>bold</b> and <a href="http://example.com/"&gt
</section> </section>
<section> <section>
<h2>HTML &ltmeta&gt; Element</h2> <h2>HTML &lt;meta&gt; Element</h2>
<p> <p>
When creating a <strong>Frames Protocol</strong> application, you can effectively ignore almost all of <abbr title="HyperText Markup Language">HTML</abbr> except for one <abbr title="HyperText Markup Language">HTML</abbr> element — the <abbr title="HyperText Markup Language">HTML</abbr> &ltmeta&gt; element. When creating a <strong>Frames Protocol</strong> application, you can effectively ignore almost all of <abbr title="HyperText Markup Language">HTML</abbr> except for one <abbr title="HyperText Markup Language">HTML</abbr> element — the <abbr title="HyperText Markup Language">HTML</abbr> &lt;meta&gt; element.
</p> </p>
<p> <p>
The <strong>Frames Protocol</strong> only uses the <abbr title="HyperText Markup Language">HTML</abbr> &ltmeta&gt; element. The <strong>Frames Protocol</strong> only uses the <abbr title="HyperText Markup Language">HTML</abbr> &lt;meta&gt; element.
And it (the <strong>Frames Protocol</strong>) uses the <abbr title="HyperText Markup Language">HTML</abbr> &ltmeta&gt; element in a very particular way. And it (the <strong>Frames Protocol</strong>) uses the <abbr title="HyperText Markup Language">HTML</abbr> &lt;meta&gt; element in a very particular way.
</p> </p>
<p> <p>
The <abbr title="HyperText Markup Language">HTML</abbr> &ltmeta&gt; element has been around since the 1990s. The <abbr title="HyperText Markup Language">HTML</abbr> &lt;meta&gt; element has been around since the 1990s.
</p> </p>
<p> <p>
If you look at the old <abbr title="HyperText Markup Language">HTML</abbr 2.0 specification (i.e., <a href="https://datatracker.ietf.org/doc/html/rfc1866">IETC RFC-1866</a> in <a href="https://datatracker.ietf.org/doc/html/rfc1866#section-5.2.5">section 5.2.5.</a>), which was created back in the 1990s, you can see how the <abbr title="HyperText Markup Language">HTML</abbr> &ltmeta&gt; element was defined back then. If you look at the old <abbr title="HyperText Markup Language">HTML</abbr 2.0 specification (i.e., <a href="https://datatracker.ietf.org/doc/html/rfc1866">IETC RFC-1866</a> in <a href="https://datatracker.ietf.org/doc/html/rfc1866#section-5.2.5">section 5.2.5.</a>), which was created back in the 1990s, you can see how the <abbr title="HyperText Markup Language">HTML</abbr> &lt;meta&gt; element was defined back then.
</p> </p>
</section> </section>
<section> <section>
<h2>OpenGraph</h2> <h2>OpenGraph</h2>
<p> <p>
The <strong>Frames Protocol</strong> usage of the <abbr title="HyperText Markup Language">HTML</abbr> &ltmeta&gt; element takes inspiration from the <a href="https://ogp.me/">OpenGraph</a> protocol. The <strong>Frames Protocol</strong> usage of the <abbr title="HyperText Markup Language">HTML</abbr> &lt;meta&gt; element takes inspiration from the <a href="https://ogp.me/">OpenGraph</a> protocol.
</p> </p>
<p> <p>
Here is an example of the <a href="https://ogp.me/">OpenGraph</a> protocol: Here is an example of the <a href="https://ogp.me/">OpenGraph</a> protocol: