search

yekigoc / akomantoso

Automatically exported from code.google.com/p/akomantoso
0 stars 0 forks source link

Ambiguous name of element <body> #3

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
The container element <body> can be confused with the xhtml "body" element,
as Akoma Ntoso uses certain XHTML elements (but not <body>). 

It is suggested that the element be renamed to <ActBody> or similar

Original issue reported on code.google.com by ashok.ha...@gmail.com on 26 Oct 2007 at 1:36

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
The xhtml body element does not currently belong, nor will it ever, to the 
Akoma Ntoso vocabulary (not an 
appropriate container). Also, for real clarity it should be said that Akoma 
Ntoso does not use any XHTML 
elements, even though this may be said in the documentation for brevity. 
Rather, Akoma Ntoso uses elements 
in the Akoma Ntoso namespace that are synonyms and semantically equivalent to a 
few elements in the 
XHTML namespace. This does not imply complete derivation of the xhtml, nor the 
need to avoid xhtml names 
in the Akoma Ntoso namespace.

Also let me add that Monica and myself came to the body proposal after long and 
blood-thirsty discussions, 
including an alternative terms for clauses (now content) that was (apparently) 
inappropriate, and I for one 
would be very wary of any alternative term for body. 

ActBody is surely unacceptable, as it is not aimed the Body of the Act (but 
rather at the body of a hierarchical 
container actually containing the text of the fragment. ActBody also is too 
close to ActDate and ActTitle which 
have completely different purposes and content models. 

So I suggest to reject this proposal.

Original comment by fvit...@gmail.com on 26 Oct 2007 at 10:50

GoogleCodeExporter commented 8 years ago 
LET ME FIRST APOLOGISE IF YOU RECEIVE THIS MESSAGE AND FEW TO FOLLOW TWICE. I 
WAS
RIGHTLY MADE TO NOTE BY FABIO THAT I SHOULD HAVE ENTERED MY NOTES IN THE ISSUE
TRACKER AND NOT RESPOND BY E-MAIL. SORRY FOR ...

Here I am suggesting to use HierarchyBody or something of the sort because we 
should
avoid, as much as possible, to have name such <body> that to really be 
understood
require a thorough reading of the Release Notes.

Then, I would like Fabio to consider to add in the next Release a paragraph to
explain in more details fact that "Akoma Ntoso does not use any XHTML elements".

I suggest to still consider if a better name can be found.

Original comment by flavio.z...@gmail.com on 27 Oct 2007 at 12:32

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
1) Adding such a note has been done.

2) Searching a new name: as I told you, Monica and I spent the best part of an 
hour discussing for a name that 
could satisfy both. It needs to be short. It needs to be unambiguous. It needs 
to be correct. It is not easy.

Original comment by fvit...@gmail.com on 18 Nov 2007 at 5:02