In this web-page we present a method of publishing HTML-text that basically anyone can refer to ANY PART of it. ¶
The core concept of our proposal is the addition of ID attributes on all elements of an HTML text.
For example:
<h1 id="idXxxx">...</h1>
or
<p id="idYyyy">...</p>
That's all. Now we can refer to any part of the document!!!
¶
The IDs must be unique.
You can use as ID whatever you want. We sugest to begin with "id" in order to be distinguished from other words in the text and do not contain spaces. For example:
idProposal, idHeader, idIndex-income, ...
¶
The IDs must be visible to the reader.
The reader, in order to refer to any part of the document, must know the ID of this part of the file. This can be done by adding a hidden element in this part of the file that will be visible when the mouse is over this text. But if this hidden-element is and a link-element, then the reader could copy the address of this part of the file from the address-bar of his browser. Here are some examples of the simple code we have to add to reach our goal.
<h1 id="idXxxx">...
<a class="hide" href="#idXxxx">¶</a></h1>
or
<p id="idYyyy">...
<a class="hide" href="#idYyyy">¶</a></p>
With this code, when the reader has the mouse over an HTML-element (a part text), at the end appears the ¶ symbol. Putting the mouse over this symbol, s|he can see the ID of this text and clicking on this symbol he can copy from the address-bar the address of this particular part of the text. The paragraph you are reading now has the feature we are talking about and you can experiment with it.
¶
ID Patterns.
If the author of a doc uses patterns to write the IDs of a text-file, it helps the reader to quickly identifies the parts of the file. Example:
- idA4 (article)
- idA4P2 (paragraph)
- idP2 (Part)
- idP2T1 (Title)
- idP2T1C2 (Chapter)
- idP2T1C2S2 (Section)
¶
The next important feature an HTML-text must have is heading-elements that correctly represent the structure of the text.
Browsers' blugins create automatically the table-of-contents (outline) of HTML-texts with headings and make the reading easier. Example:
In Chrome, the TableOfContents extension. TableOfContents also gives the "big-picture" of what you are reading when you click on a heading in the text.
In Firefox, the HeadingsMap add-on.
¶
HTML5 (not yet a final standard) introduced the <section> element. We are using it because shows more crearly the structure of text than the heading-elements alone. ¶
CSSs separate content from presentation. We use a css for harmonization in the appearance of documents and better control. ¶
By setting IDs in all elements of a text, we can refer to any part of a document. Then we can use links in all places in a text we refer to another place inside a document or outside of it. Law-texts are full of references. Find the references it is difficult and sometimes impossible. If the references are one "click" away, then reading law will become easier. ¶
ID-HTML5-files (what we are proposing here) improve the functionality of the indexes of text-files.
First, by setting as ID on each index-entry the pattern "idIndex-term", the reader will have very quick access to the entries.
Second, by storing ALL the terms a text uses, the reader will understand the text easier.
Third, by setting the definition and related attributes of the concept of the term, the reader will understand quickly the text.
SNA2008.html is an example with an index.
¶
This website presents many examples with our proposal. Reading their code is the best way to understand what really we are proposing. ¶
see law-page.
UN-SNA-2008:
The System of National Accounts (SNA) is the internationally agreed standard set of recommendations on how to compile measures of economic activity. The SNA describes a coherent, consistent and integrated set of macroeconomic accounts in the context of a set of internationally agreed concepts, definitions, classifications and accounting rules.(http://unstats.un.org/unsd/nationalaccount/sna.asp)
¶