#4 — In cases where the notices carries only a title and a paragraph ...

About the first question

 

Actually the core of your proposed example is constituted by differents parts; so we can mark up it as you see in attachment joint here

For the second question:

Could you kindly give me further  details about your problem with Norma Xml:? I’m very sorry but I’m not understand very well what’s the problem.

Thanks

In principle this kind of documents are not ACT but ordinances of a Ministry and the structure is mostly "free".

 

In other words it should be "DOC" not an "ACT" as type of document (see in Norma-Editor Meta-Type menu in the Preface bar).

 

• ACT permits only a body that contains only hierarchical elements.
• DOC permits also Block elements and Container elements without use in artificial way ARTICLE and CLAUSE1 and CLAUSE2.

The main problem is that: the block and the container elments not admit TITLE and SIDENOTE in this release. 

I should ask to Fabio to take care to this problem.

 

Finally the difference between TITLE and SIDENOTE:

• Title is the main topic of the article/section/block.
• Sidenote is a classification of a part of the text and there are involved also subparts (items, letters, commas, etc.). The classification depends from the internal division of the statute book.
  

So in this case it is definetly a TITLE.

Please find the XML markup of the document with DOC type.

 

 

I agree with Monica that this is not an act, but a doc.

However I have two comments about this:

First, I would not want the impression to be spread that the only difference between acts and docs is in the fact that act wants hierarchical elements while doc also allows blocks and containers. This is in fact not correct. The real distinction is that act is used to mark up an act, and doc is used to mark up a document that is NOT an act, nor a bill, etc.

Second, the hcntainer element is the best to use if you have the situation you mention. Let me rephrase it as follows:

What we have here is a document that is NOT an act (therefore we must use a doc element). As correctly evoked by Monica, this has a maincontent element that allows hierarchical containers as well as plain containers and block elements.

The content is composed of something that has a initial heading, and two sub-elements (two blocks) that contain the actual normative text. Now BY CONSTRUCTION, a hcontainer is an element that has privileged elements at the beginning (which we call, as needed, num, or heading, or sidenote, or subheading). Therefore this is the class of elements we must look into. We need to exclude all named hcontainers (section, part, paragraph, chapter, title, book, tome, article, clause, subsection, subpart, subparagraph, subchapter, subtitle, subclause) as no such name is explicitly used in the document. Therefore we must use the generic element hcontainer.

This we fill with a heading and a content, which in turn contains our two block elements. Since there is no real reason to remain generic at this point, we might as well call them p instead of block. That's it.

So, as a general rule: if you have an element that does NOT NATURALLY FIT into a named element, ALWAYS use the corresponding generic element. Use the attribute name to give it the name that is used in the document, if any such name exist, or "unnamed" otherwise.

Most of the elements that give structure to the document are container and hcontainers. If you are undecided about which one to use, check whether the element has relevant, privileged elements at the beginning, such as a number or a heading. In this case use a hcontainer element (if an element with the correct name exists, use it, or use the generic hcontainer if none exists). If no privileged elements exist at the beginning, then use a container. Never use block unless you want to imply that the element contains text directly (i.e., without any further intermediary).

I hope you find this explanation clear and useful and that you agree with me.

Fabio