|
0.6.2
build date: 2004.05.01
deliveryDate: 2004.05.01
builder: EM |
XRN has improved as far as migration is concerned. The concept of visibility has been replace by the concept of importance.
[func]
| Visibility and Importance
The concept of importance was definitively badly expressed though the "visibility" concept: this has been replaced by the 'importance' concept.
XSD: the attribute 'visibility' has been replaced by 'importance'.
Use the new migration feature in order to upgrade your XRN XML release notes files.
|
[tech]
| XRN migration
Ant: added the 'migrate' parameter that enables to automatically migrate the version of the XML release notes file up to the version of the XRN wrapped in the Ant jar.
Since the XSLT are also present in the zip, you can perform the migration via pure XSLT.
|
[vsc]
| These are the CVS change logs since the previous version.
2004-04-29 09:45 source/inspiration/PloneDiscusstion20042904.txt A discussion on #plone IRC chat concerning intersting things...Edouard Mercier
2004-04-27 08:37 source/java/org/apache/tools/ant/taskdefs/optional/clearcase/CCChangeLog.java The Ant task that enables to generate the ClearCase change log history under the XML format.Edouard Mercier
2004-04-21 08:56 source/java/org/ed/pack/xmlreleasenotes/XMLReleaseNotes.java Fixed the documentation of the task.Edouard Mercier
2004-04-21 08:45 setup/ReleaseNotes.xml Updated for the V0.6.1.Edouard Mercier
2004-04-21 08:43 build.xml Now, uses the XSLT CVS model for generating the release notes.
Updated for the V0.6.1.Edouard Mercier
2004-04-21 08:43 XMLReleaseNotes.iws no messageEdouard Mercier
2004-04-21 08:42 source/XML/XMLReleaseNotes.xsd Added the 'Feature/@why' attribute.
Added the 'Feature/@type' new possible value 'vsc'.Edouard Mercier
2004-04-21 08:41 source/XML/XMLReleaseNotes.css Added the 'vscType' class selector that enables to render a different way the VSC features.Edouard Mercier
2004-04-21 08:26 source/plugin/CVSModel.xsl The XSLT model plugin that enables to integrate CVS change logs into the release notes.Edouard Mercier
2004-04-21 06:12 source/java/org/ed/pack/xmlreleasenotes/XMLReleaseNotes.java Made the e-mail feature an inner element.Edouard Mercier
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| [from 0.5.1] | Ant 1.5.0+ |
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant.
|
| [from 0.3.2] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
-
Added the migration XSLT in the Ant jar library.
download
|
|
0.6.1
build date: 2004.04.21
deliveryDate: 2004.04.21 |
This release fixes bad previous designs, and proposes a first plugin for the integration of CVS change logs into the release notes.
[func]
| Versioning Control System
Enables a deeper integration with the VCS systems, so that it is possible to track down the source changes.
This enables to produce more accurate and exhaustive release notes, dedicated to the support of the component.
This opens the framework to the versioning system and enhance this information, that is too often restricted to developers, when they take the time to make views...
This is now possible for CVS via the 'plugin/CVSModel.xsl' XSLT model file: beta for the moment, because it lacks integration...
|
[tech][bug-fix]
| Ant task mail re-engineering
It was definitively a bad idea to inline the mail task at the same XML hierarchy level as the XRN task's. The mail task is now an inner XML element, and the 'mail' parameter is discarded.
You can now provide a specific subject to the sent-mail via the 'subject' parameter of the inner 'mail' XML element.
|
[func]
| Feature new type
Added the 'vsc' feature type so as to render this feature a different way via the XSLT: not yet taken into account.
|
[func]
| The 'why' feature attribute
Added the 'why' attribute to the 'Feature' XML element, in order to better understand the reason for the feature. This enables to better understand the evolution of the component.
This enables to open the framework to existing solutions that deal with the needs collecting.
This attribute is not yet taken into account...
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| [from 0.5.1] | Ant 1.5.0+ |
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant.
|
| [from 0.3.2] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
-
Added the 'plugin' directory that should contain all the plugins in the future.
download
|
|
0.6.0
build date: 2004.04.20
deliveryDate: 2004.04.20 |
This version adds the Ant 'mailing' feature, proposes to inline the CSS, so as to make possible stand-alone HTML release notes pages.
[tech]
| Mail
Ant: added the opportunity to mail the release notes directly from the task, since the task derives from the official Ant 'Mail' task.
|
[tech]
| Improvement of the Feature ID
A better HTML rendering of the feature inheritance and its identifier is now performed.
|
[tech]
| Feature visibility
XSL: added CSS selector classes named 'featureVisibilityN' in order to give control to a feature visibility, where N ranges from 1 to 4.
|
[tech]
| CSS inlined
Ant: it is now possible to inline the CSS content within the generated HTML, so as to be make some HTML stand-alone. This is possible via the 'inlineCSS' parameter.
|
[tech][bug-fix]
| New dependency, composition, requirement
XMLReleaseNotes2HTML.xsl: fixed the problem of the '[from M.m.µ]' display when [new] also appears (dependencies, requirements, composition).
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| [from 0.5.1] | Ant 1.5.0+ |
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant.
|
| [from 0.3.2] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
|
|
0.5.1
build date: 2004.04.15
deliveryDate: 2004.04.15 |
Some XSLT technical improvements and some functional additions is the HTML rendering.
[func]
| Feature 'ID' attribute
Made this 'Feature/@ID' attribute a string, so that mnemonics may be used.
|
[tech]
| URI resolver and parameters
Ant: added the opportunity to use URI resolvers in the XSLT provided by the user via the inner 'xmlcatalog' XML element within the 'model' and 'layout' elements. This is the native Ant XMLCatalog element.
Ant: added the possibility to provide XSLT parameters in the task via the inner 'param' element within the 'model' and 'layout' elements. This is a copy of the built-in 'XSLT' task Ant feature.
|
[tech]
| HTML content
Enable a better way to express that some HTML tags may be used within the XML release notes, as far as textual content is concerned: the 'contentType' attribute has been added to nearly all textual possible places. When set to 'html', you can use HTML tags. This is now possible but do not abuse it
because you have to think that those release notes may be output in other formats than HTML!...
|
[tech]
| Reuse of the Feature ID
Pay more attention to the 'ID' of a 'Feature' element and refer to it if already defined in the past. Now hyperlinks are displayed for already defined features.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| Beware of the Ant requirement that has changed. |
| [new] | Ant 1.5.0+ |
This version of Ant is required because we use the XMLCatalog class that only appeared from this version of Ant.
|
| [from 0.3.2] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
|
|
0.5.0
build date: 2004.04.14
deliveryDate: 2004.04.14 |
Opened the framework so that it is possible some external information from the outer via the Ant task.
[func]
| Abstract
Provided the opportunity to define an abstract for each feature, through an 'Abstract' element within the 'Features/Feature' XML element: this enables to name the feature shortly.
|
[func]
| Additional XSLT
Ant: added the possibility to use additional XSLT in order to open the framework via the 'model' and 'layout' inner elements.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| [from 0.3.2] | Ant 1.4.1+ | Only if you want to use with Ant: the task has been tested from this version of Ant. |
| [from 0.3.2] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
-
The zip now contains a 'doc' folder, where you can find two XSLT examples.
download
|
|
0.4.1
build date: 2004.04.13
deliveryDate: 2004.04.13 |
Better package of the delivery, introduction of the concept of version of the framework.
[tech][bug-fix]
|
Fixed the bug of the delivery download hyperlink that was wrong.
|
[tech]
|
XSL: enable to remove the default banner at the bottom via a 'banner' parameter. Don' disable it, otherwise the tool won't be known and there will be little support and enhancements.
|
[tech]
|
Added a version attribute that enables to track the version of the framework used. This may be very useful as far as migration and converstions are concerned.
XSD: added the 'version' attribute indicates the version of the XMLReleaseNotes framework it complies to.
XSL: outputs this version in the bottom banner and outputs a warning if the XML release notes and the XSD are not the same version.
|
[tech][bug-fix]
|
Fixed the release which missed the release notes! How possible is it?
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| [from 0.3.2] | Ant 1.4.1+ | Only if you want to use with Ant: the task has been tested from this version of Ant. |
| [from 0.3.2] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
-
Fixed the content of the delivery. The naming convention of the delivery file name has changed and is now 'XMLReleaseNotes-M.m.p.zip' The sources ar now placed within the 'src' directory. A readme file has been added.
download
|
|
0.4.0
build date: 2004.04.12
deliveryDate: 2004.04.12 |
This is a technical release that makes the framework more integrable.
[tech]
|
Ant: removed the default 'stylsheet.css' file into a directory named 'XMLReleaseNotes' into the jar library, so as to possible avoid conflicts with the rest of the classpath.
|
[tech]
|
Ant: added the 'deploy' parameter that enables to deploy the framework resources from the jar library, so as to be able to use the XSD, the CSS...
|
[tech]
|
XSL: turned the 'standAloneHTML' parameter default value to 'false'.
|
[tech][bug-fix]
|
Fixed the bug concerning the 'Requirements', 'Dependencies' and 'Composition' display, which were not always present as required.
|
[func]
|
Made the 'Release/@deliveryDate' optional, because you can build releases without never spreading them!
|
[tech]
|
XSD: the schema now belongs to the 'http://xmlreleasenotes.free.fr' target namespace, which should be refered as 'xrn'.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| [from 0.3.2] | Ant 1.4.1+ | Only if you want to use with Ant: the task has been tested from this version of Ant. |
| [from 0.3.2] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
|
|
0.3.3
build date: 2004.04.07
deliveryDate: 2004.04.07
builder: EM |
The website is more elaborated. Just changed a few key things within the XSD.
[tech]
|
Replaced the term 'item' by 'feature' because it si more appropriate.
Added the 'BuildingBlock' within the 'Feature' element, in order not mix the complex element with text.
|
[func]
|
Added the opportunity to define a release builder via the 'builderID' attribute on the 'Release' element.
|
[func]
|
XMLReleaseNotes2HTML.xsl: added the 'delivery' parameter that enables not to output de "Delivery" column, which enables to download the artefacts.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| [from 0.3.2] | Ant 1.4.1+ | Only if you want to use with Ant: the task has been tested from this version of Ant. |
| [from 0.3.2] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
-
The validation XSD and XSL files have been added to the distribution.
download
|
|
0.3.2
build date: 2004.04.01
deliveryDate: 2004.04.01 |
The idea is to provide a first basic Ant integration.
[tech]
|
Added a task Java library that enables XMLReleaseNotes HTML transformation seamless integration to Ant.
asking: EM
contributor: EM
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| The requirements have changed concerning the Ant integration, which is a new feature. |
| [new] | Ant 1.4.1+ | Only if you want to use with Ant: the task has been tested from this version of Ant. |
| [new] | XSLT | You need to have an XSLT implementation library like Saxon or Xalan in your Ant 'lib' directory. |
|
-
An additional Ant Java task library is available under 'lib' and a new directory 'doc' has been created.
download
|
|
0.3.1
build date: 2004.03.31
deliveryDate: 2004.03.31 |
This is a very tiny incrementation compared to the previous release.
[func]
|
Added an an about page on the web-site.
|
[func]
|
The releases sorting is better thought. The need of a documentation is now needed.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
|
|
0.3.0
build date: 2004.03.30
deliveryDate: 2004.03.30 |
This is a version that can already be used as far as HTML transformation is concerned..
[func]
|
Added the concept of visibility for each item, so that it is possible to filter when rendering into HTML, for instance. It is adviced to use a value that ranges from 0 to 4, 4 meaning that the item is the most visible. This is now possible through the 'visibilityThreshold' XSLT parameter.
|
[func]
|
Now, enables to tell whether the dependencies and requirements should be inherited from the previous versions. How does it work? For each 'Release' XML element...
|
[func]
|
XMLReleaseNotes2HTML.xsl: added the possibility to filter the type of items to be documented through the 'typeFilter' parameter. This enable to remove for instance the technical information into a functional release notes dedicated to end-users.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
|
|
0.2.6
build date: 2004.03.26
deliveryDate: 2004.03.26 |
This is a version that presents a better HTML transformation.
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
|
|
0.2.5
build date: 2004.03.21
deliveryDate: 2004.03.21 |
Added the opportunity to use a CSS when transforming into HTML via the 'XMLReleaseNotes2HTML.xsl'.
[func]
|
XMLReleaseNotes2HTML.xsl: you can now define the lower and upper limits of the versions for which the HTML is generated.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
-
The delivery now contains the licenses and a default CSS stylesheet named 'stylesheet.css'.
download
|
|
0.2.4
build date: 2004.03.21
deliveryDate: 2004.03.21 |
There is no new delivery, only the web site generation has changed and contains the internal AntDoc.
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| No delivery |
|
0.2.3
build date: 2004.03.21
deliveryDate: 2004.03.21 |
This is patch and the top-child 'Deliveries' XML element has been adde so as to enable to express the delivery root URL.
[func]
|
Added the opportuniy to add a 'ReleaseNotes' 'Deliveries' XML element direct child that can specify the common HTTP URL (via the 'href' attribute) where the deliveries are gathered.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
|
|
|
0.2.2
build date: 2004.03.21
deliveryDate: 2004.03.21 |
This is the very first downloable release.
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| Requirements |
| This is just how to show that you may not inherit from the previous requirements. |
| The V0.2.0 and V0.2.1 were not OK, as far as the automatic delivery process is concerned.
-
The delivery is a simple zip, not yet totally properly organized.
download
|
|
0.2.0
build date: 2004.03.21
deliveryDate: never |
This is still a very basic release, just made of two files: the XSD XMLReleaseNotes.xsd and an XML release notes example, XMLReleaseNotes.xml. It also includes the XSLT transformation XMLReleaseNotes2HTML.xsl.
[tech]
|
The architecture and files of the projets are now OK; the resources are under CVS and all the delivery engine should work, through an Ant buildfile.
|
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| No delivery |
|
0.0.beta
build date: 2004.03.18
deliveryDate: never |
This is a bit more elaborate version, since new ideas have come to my mind, and this is the reason why I make a 'todo' release in order to express them. The principle is that the 'Release' XML element should be sorted from the latest to the oldest.
| Dependencies |
| [from 0.0.alpha] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [from 0.0.alpha] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [from 0.0.alpha] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| No delivery |
|
0.0.alpha
build date: 2004.03.18
deliveryDate: never |
This version is a first try to build a tiny XML release notes framework.
| Dependencies |
| [new] | XSD 1.0 | The first version 'Dependencies' XML element will initialize the dependencies of the component. If you redefine another 'Component' XML element in a later release version with the same 'ID' attribute, the current one will be considered obsolete. |
| [new] | XML 1.0 | All the tiny framework is expressed in XML, so this is off course required to build it. |
| [new] | XSL 1.1 | The obvious idea is that this framework enables to transforms the XML release notes in whatever text format, and HTML above all. |
| No delivery available at this stage.No delivery |