Tracker log

An overview of recent activity in the tracker.

Mutinda Kitana added a new response to »Documents cannot be uploaded to the server from the editor«:

To the creators of the Norma Server,

 

Kindly help us out with this issue. It has been pending for quite a while and is now the only thing holding us back. Your quick response would be highly appreciated.

Added 10 day(s) ago.

Fabio Vitali added a new response to »Heading and sidenote«:

The first concept to distinguish is the one between blocks and containers.

* A block is the end of the containment structure. Blocks only contain text and inline elements (that have no internal structure and can appear anywhere in between text). They can be distinguished because you would not expect them to contain other blocks or containers, but only text or inline elements.

* A container does not contain text directly, but contains blocks or other containers that may contain other blocks or other containers and so on, until no further containments of containers is necessary and we only have blocks that actually contain text.

Finally there is the distinction between container and hcontainers.

* An hcontainer, as the name implies, is not completely different from a container. It is in fact a subclass of containers. An hcontainer is a container that has some privileged, identifiable elements at the beginning that in some way identify or qualify or label or introduce the rest of the content. These special elements can be numbers, titles, headings, and so on.

If you can recognize such special elements, then you should use such a special container, i.e., an hcontainer. Otherwise keep on using you normal container.

In your example, the bullet list with a sidenote will be contained in a hcontainer, and the same bullet list without a sidenote will be contained in a simple container.

Added 10 day(s) ago.

Monica Palmirani added a new response to »Heading and sidenote«:

I understand your point of view that is based on a clean an net pattern modelling, but also the user need to have clear guidelines on how to markup.

 

 

Now in DOC we have hcontainer, container, block. So hypothetically we have at least three valid ways to markup the same document: hcontainer, container, block. But in hcontainer it is possible to include TITLE (heading) and SIDENOTE and in the others not.

 

 

So an end user that have a legal notice should have a different behavior if he/she encounter a list of bullets with a sidenote (hcontainer) and the same list without a sidenote (container or blocks).

 

 

Some rules are needed. But probably you have already a solution.

Added 10 day(s) ago.

Fabio Vitali added a new response to »Heading and sidenote«:

Mmmhhhh... I am very wary of doing such modifications.

First of all, you do not need to use act: you can and should use doc if it is not an act. doc has an open content model which allows both hierarchical elements as well as container elements as well as.. well mostly everything. This is the structure that must be used non-structured documents as well as badly structured documents (i.e., those that should, but actually don't, follow some specific drafting rules).

Second, I think we need to clearly understand what a hierarchical element is: a hcontainer is a container that has some "special" content at the beginning, which we may call titles, headings, and so on, and that can EITHER nest with other hcontainers, OR directly contain blocks and other containers.

As such, hcontainers are exactly what you are referring to when you need to specify that there are special elements at their very beginning. It does NOT imply that they should nest: for instance, clauses are hcontainers but do not nest.

For this reasons, I believe that an hcontainer is the right element for these cases. If you can't find the named hcontainer of your choice (section, part, paragraph, chapter, title, book, tome, article, clause, subsection, subpart, subparagraph, subchapter, subtitle or subclause) you can always use the generic element hcontainer itself.

I don't believe we should pollute containers and blocks with such concepts.

Issue state: unconfirmed → rejected. Added 10 day(s) ago.

Fabio Vitali added a new response to »In cases where the notices carries only a title and a paragraph ...«:

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

Issue state: in-progress → resolved. Added 10 day(s) ago.

Monica Palmirani added a new response to »In cases where the notices carries only a title and a paragraph ...«:

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.

 

 

Added 10 day(s) ago.

Kenya Law Reports added a new response to »In cases where the notices carries only a title and a paragraph ...«:

1. In the case that you sent, where Article 1 is split into two clauses, the resulting XML document is perfect.
   

I am only a waiting the legal team to give its implication. Thank you

As for the XML document of my second Question here is the same example with amendments made. i copied the XML doc and saved as word for this purpose and therefore this is how it looks.

N/B: the highlighted part was marked up as title but now displayed as sidenote.

 

 

 

 

Government of Kenya 14th January 1964 LEGAL NOTICE NO. 9 (C/CL/3/2) THE SHOP HOURS ACT (Cap. 231)
Masaku Urban Council—Sunday and Public Holiday Closing (Exemption) Notice	IN EXERCISE of the powers conferred by section 9 of the Shop Hours Act, the Minister for Commerce and Industry hereby grants exemption to shops in the area of jurisdiction of the Urban Council of Masaku from closing on Sundays and public holidays between the hours of eight o'clock in the forenoon and half-past four o'clock in the afternoon. Government Notice No. 265 of 1955 is hereby revoked.
	Made this 6th day of January 1964. G1KONYO K1ANO, Minister for Commerce and Industry.

 

PLease check the link for clarity.

Added 10 day(s) ago.

Raffaele Montanaro added a new response to »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

Issue state: open → in-progress. Added 10 day(s) ago.

admin added a new response to »In cases where the notices carries only a title and a paragraph ...«:

Issue state: unconfirmed → open. Added 10 day(s) ago.

Fabio Vitali added a new response to »Preparation for mark up«:

Please also add a new issue state such as "stable" or "persistent", so that it does not impact with the list of open issues.

Thanks

Added 10 day(s) ago.

Administrator added a new response to »Preparation for mark up«:

We have now added a new TYPE: documentation.

 

The above is in fact more a documentation then an issue. The idea would be to have people to comment/add to the above and then, when we feel it is stable, move the content to a documentation section that we are going to create.

 

Comments and suggestions on how to handle this process are welcome.

 

Issue state: unconfirmed → open. Responsible manager: (UNASSIGNED) → admin. Added 10 day(s) ago.

New issue »Documents cannot be uploaded to the server from the editor« added by Ashok Hariharan

Norma server has been installed and is running on the network, and accessible from the client computer running the editor.

 

Path to server, and path to DTD have been set on the editor.

 

The editor still says "The operation was unsuccessful" when I try to upload documents.

Added 253 day(s) ago.

New issue »Heading and sidenote« added by Monica Palmirani

 

I ask to add "heading" and "sidenote" elements in "blockElements" and "containerElements" content model.

 

In this way we can markup the heading (title) and the sidenote also in the block, container, etc.

 

This is particular usefull for the not-structured documents (such as ordinance, legal notice, etc.),  in other case we are forced to use ACT and hierElements even if there aren't.

Added 268 day(s) ago.

New issue »In cases where the notices carries only a title and a paragraph ...« added by Kenya Law Reports

In cases  where the notices carries only a title and a paragraph;

1. How should the paragraph be marked up:i.e as clause within an article or...?
2. The Norma XML output when displayed shows the "title" as a sidenote. how do we go around it?

See example below:

 

Government of Kenya

14th January 1964

LEGAL NOTICE NO. 9

(C/CL/3/2)

THE SHOP HOURS ACT

(Cap. 231)

Masaku Urban Council—Sunday and Public Holiday Closing (Exemption) Notice

N EXERCISE of the powers conferred by section 9 of the Shop Hours Act, the Minister for Commerce and Industry hereby grants exemption to shops in the area of jurisdiction of the Urban Council of Masaku from closing on Sundays and public holidays between the hours of eight o'clock in the forenoon and half-past four o'clock in the afternoon.

Government Notice No. 265 of 1955 is hereby revoked.

Made this 6th day of January 1964.

G1KONYO K1ANO,

Minister for Commerce and Industry.

Added 274 day(s) ago.

New issue »Preparation for mark up« added by Kenya Law Reports

 

To ensure that the integrity of that legal documents is maintained, this can be done by proofreading the word documents extracted before marking up.

 

1. Extract a Word document and a PDF document then use the PDF as reference.
2. Some of the words where the hyphens are to be removed at the end of the line are supposed to have those hyphens (e.g. sub-paragraph).
3. In case the word document is in text boxes; highlight the sidenotes on the left (say Blue ) and those on the right (Red), select the text boxes and convert to text from the Microsoft word tool bar menu.
4. Ensure that the tables within the text boxes are maintained.
5. Counter check the data in the tables to avoid distorted figures.
6. Delete headings that recur on every page of the document except on the first page where it is necessary to mark up the preface.

 

 

 

 

 

Added 276 day(s) ago.