validFrom, validTo removed; edition numbers converted to dates
2005-OCT-01 TA
adding translation element and changing lang element in IPCEntry
purpose: language support for 3rd, 4th etc. language
2012-AUG-07 SzZ,TA
conversion to XSD
wrapper for multiple revisionPeriod-s
root for ipcr_scheme_...files
exchange data of more (independent) revision periods can be stored in a single XML file
schemes in one revisionPeriod
In one revisionPeriod, that could be a "prereform","reformed" or "simplified" revision period,
more ipcEdition-s can be stored (typically: in reformed IPC, core and advanced)
one IPC edition (core or advanced)
Comment
May contain a single en or fr element, or a sequence of translation-s
single language files are allowed
History
20061001 TA
modified added 'translation' element
English scheme
French scheme
Scheme in a non-authentic language.
e.g. 20060101
prereform editions: always core level
revision periods in reformed IPC may contain a core and an advanced ipcEdition
after simplification there is only a single advanced level ipcEndition-s
Obsolete technical attribute.
authentic language scheme
Content is compatible to the translation element.
authentic language version of the IPC scheme
translation of IPC to a national language
History
20061001 TA
added: for national language versions
non-authentic language version of the IPC scheme
final text of IPC in a single language
Comments
in ipcr_scheme... files: the structure is embedded (parent-child relationship of data is reflected by the XML parent-child relationship)
The structure allows non-embedded presentation of IPC entries
some attributes may be considered as redundant, for allowing staticIpc as root element (in RIPCIS).
IPC sections, i.e. kind attribute is 's'
Obsolete technical attribute.
representation of structured and non-structured elements of the IPC text
for structured entries the symbol attribute must be unique in one language
non-structured entries are identified by symbolTo attribute in case the scope of the non-structured entry overlaps more structured entries that are on the same level as the start of the scope
a note that belongs to a sequence of ipcEntries is presented in the list
of the parent of the highest entry within its scope
a non-structured entry (note,guidance heading, subsection title, line)
must not contain embedded ipcEntry entries
ipcEntry in compilation files has a different structure
History
20051001 TA
language code allows any two-letter language code
obsolete EF language code maybe used at language-independent cases, e.g. deletions; EF is a non-existing 2-letter language code
may be empty in prereform editions, e.g. removed notes
a subdivision of the parent ipcEntry or non-structured ipcEntry within the scope of the parent