Okay/Spec: Difference between revisions

Line 45:

=== looking for stuff ===

=== linking to stuff ===

~~Links~~ in ~~Okay follow~~ the ~~same rules~~ as in standard ~~HTML~~.

Unless otherwise specified, michaelformats can be included inline or '''linked''' in a <code><a/></code> or <code><link/></code> element, using the michaelformat's name as the <code>rel</code> attribute.

As an example, each of these elements are functionally equivalent:<syntaxhighlight lang="html">

</div>

<a href="/rooms/" rel="ok-rooms">Room Directory</a>

When a client encounters a URI with a fragment, it must search for an element with a matching <code>id</code> in the linked document. If the specified element is present, the client must not scan the document for the desired markup, and instead consider the linked element to be the desired markup. If multiple instances of the same <code>id</code> exist in the document, the client must ignore all but the first instance. make this make sense

@@ Line 45: / Line 45: @@
 === looking for stuff ===
 === linking to stuff ===
-Links in Okay follow the same rules as in standard HTML.
+Unless otherwise specified, michaelformats can be included inline or '''linked''' in a <code><a/></code> or <code><link/></code> element, using the michaelformat's name as the <code>rel</code> attribute.
+As an example, each of these elements are functionally equivalent:<syntaxhighlight lang="html"><!-- a room directory, rendered inline -->
+<div class="ok-rooms">
+    <!-- ... -->
+</div>
+<!-- a room directory, linked with an anchor tag -->
+<a href="/rooms/" rel="ok-rooms">Room Directory</a>
+<!-- a room directory, linked with an link tag -->
+<link href="/rooms/" rel="ok-rooms"></syntaxhighlight>The value of the <code>href</code> attribute <span class="must">must</span> be a ''valid URL potentially surrounded by spaces'', as [https://html.spec.whatwg.org/multipage/urls-and-fetching.html#valid-url-potentially-surrounded-by-spaces defined in the HTML standard].
 When a client encounters a URI with a fragment, it <span class="must">must</span> search for an element with a matching <code>id</code> in the linked document. If the specified element is present, the client <span class="mustnt">must not</span> scan the document for the desired markup, and instead consider the linked element to be the desired markup. If multiple instances of the same <code>id</code> exist in the document, the client <span class="must">must</span> ignore all but the first instance. <span class="todo">make this make sense</span>