Diff:Mar 2008 & Nov 2008

This release comprises a major modification in naming of elements, introducing a systematic usage of  camel case, settling a long-standing issue about incoherence in the usage of lower and uppercase characters in element names (as well as one element group). This change is thus fixing an overall problem of coherence in element naming, rather than a concrete problem of descriptiveness or completeness of the vocabulary.

Content differences:

• The spelling “judgment” has been replaced with “judgement” in observance to the above-mentioned mail by Mariya Badeva. This relates to all elements and attributes containing the word judgement.
• All Top Level Classes have now a proposed syntax for IDs (that was up to this day only mentioned as TBD).
• Element comment has been renamed scene according to remarks about adopting a vocabulary more connected to screenplays.
• Elements ActType, ActTitle, ActNumber, ActProponent, ActDate, and ActPurpose have been renamed docType, docTitle, docNumber, docProponent, docDate, and docPurpose so as to reflect a vocabulary apt to describe more than just legislation.
• Element recordedTime has now a new attribute type to allow for the specification of recorded times for the beginning of event (startEvent) and end of events (endEvent) if necessary
• A new inline element remark has been added to specify editorial inclusions within the main text (for instance the caption of the speaker in the new page continuing from the previous one). An attribute type with an initial list of remark types (sceneDescription, phenomenon, caption, translation) is also added.

Case differences (specific to the camelCase release):

• A specific policy for case in names has been decided. It only and specifically regards structure names in the schema (these include names for attributes, elements, simple types, complex types, attribute groups and element groups) that are composed of two separate terms in plain English. The policy is as follows:

• A name that is composed of a simple term is all in lowercase (e.g., section, act, publication).

• A name that is composed of two or more full terms has the first one in lowercase, and all the others have their initial letter in uppercase (that I call camelCase, as a reduced form of CamelCase). For instance, courtType, actDate, mainContent.

• A name that is composed of an acronym plus one or more full terms has the acronym in all capital letters and the remaining terms in camelCase (i.e., the first is all lowercase and the others have the first letter in uppercase). For instance, FRBRManifestation, TLCPerson.

• The element groups, complex types and simple types EventType, VersionType, InlineCM, SpeechSection,  HierarchicalStructure, OpenStructure, DebateStructure, JudgmentStructure and DocumentTypes are now eventType, iversionType, inlineCM, speechSection, hierarchicalStructure, openStructure, debateStructure, judgementStructure (note new spelling for judgement) and documentType (note, also singular now) in camelCase.

• 17 elements have changed their case in order to adopt the camelCase approach: elements activeModifications, activeRef, akomaNtoso, attachmentOf, debateRecord, efficacyMod, forceMod, hasAttachment, mainContent, meaningMod, noteRef, passiveModifications, passiveRef, proceduralMotions, scopeMod, textualMod, and tocItem.

Click here to see the differences between the releases.