OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

legaldocml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Table of content for the Customizing Akoma Ntoso document (NOW with the attachment!)

Dear all, 

as requested here is the table of content of the document on the customization of Akoma Ntoso. Of course most of it will resemble my old document that I shared the, and am attaching again here. 

1    The customization of XML schemas
What it means to customize an XML Schema in a conservative way, in order to respect the fundamental good properties of the base schema and introduce only those constraint you really are interested in. 
Fundamental law: all documents valid according to the customized schema must be valid according to the base schema. Ways to customize are basically restrictions, extensions and translations. 
Fundamental law to customize Akoma Ntoso: respect patterns, compliance rules and metadata. 

2    Restricting Akoma Ntoso
What it means to restrict a schema: add limits to the allowed content model of elements, to allowed values of attributes, etc. In short: go right ahead and do your worst, you will not be able to break the schema. 
How to do that: you can create your own schema, or use existing tools such as the custom schema generator available at XXX (currently http://akn.web.cs.unibo.it/akgenerator/ but will have to move somewhere else). 

3    Extending Akoma Ntoso
What it means to extend a schema in a conservative way. Basically there are only a few things you can do so as not to break things. Breaking Akoma Ntoso is even simpler, so this is a delicate thing to do, but Akoma Ntoso provides you with ways to safely extend things:
3.1    The element <foreign>
3.2    Generic elements
3.3    The <proprietary> section and other ways to add custom metadata

4     Other ways to customize the schema
4.1    Custom attributes  (yes you can)
4.2    Custom elements    (you shouldn't, but if you need you can, as long as you respect the patterns)

5     Translations
Basically, you should not. Really, you shouldn't. But if you insist, there are ways to do so in a safe manner. Generate a correct subschema in the original English language, then translate in your own language all the elements, attributes and attribute values EXCEPT FOR AKOMA NTOSO, and generate a custom namespace that we can recognize, and generate a translation map (which MUST BE 1-1 with the original language) and provide a link to the translation map in the schema. 




Fabio Vitali                                          The sage and the fool
Dept. of Informatics                                     go to their graves
Univ. of Bologna  ITALY                               alike in this respect:
phone:  +39 051 2094872                  both believe the sage to be a fool.
e-mail: fabio@cs.unibo.it                  Where, then, may wisdom be found?
http://vitali.web.cs.unibo.it/   Qi, "Neither Yes nor No", The codeless code

Attachment: Extending Akoma Ntoso.pdf
Description: Adobe PDF document

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]