Elkera BNML Schema contribution to eContracts TC

[<civicsdotcom-oasis@yahoo.com>]

Posted on behalf of Peter Meyer, which he gets his
list posting access sorted...

-----Original Message-----
From: Peter Meyer [mailto:pmeyer@elkera.com] 
Sent: Wednesday, 21 September 2005 11:29 PM
To: Legalxml-Econtracts TC
(legalxml-econtracts@lists.oasis-open.org)
Subject: Elkera BNML Schema contribution to eContracts
TC

Dear TC members,

At the last meeting, the TC resolved to adopt the BNML
Schema prepared by
Elkera as the basis of its eContracts specification.

I have now finalised licensing arrangements and can
contribute the schema to
OASIS to permit the TC to go forward with the Schema.

Attached is a zip file: BNML contribution
2005-09-21.zip. This file contains
a BNML eContracts subset of the Elkera BNML Standard
Schema. The only
practical difference is that it omits the BNML
correspondence document type.
Please unzip the package retaining the directories so
that the files are all
retained in their correct locations.

The BNML eContracts schema is not intended as the
finished eContracts TC
schema. It is merely the platform from which the TC
may create its own
schema to fulfil its requirements. In practical terms,
the BNML eContracts
Schema provides a practical way for the TC's version
to fork off the BNML
Standard schema so it can take on its own, independent
life.

The BNML Standard Schema is now released by Elkera
under an open source
licence called the BNML Schema Public Licence. A copy
of that licence is in
the schema package for information purposes. The TC
does not need to rely on
that licence, but may do so if it wishes. The
eContracts Schema is
contributed under the OASIS Legacy IPR policy that
applies to the eContracts
TC. This grants OASIS a non exclusive licence to
create derivative works
etc.

The package includes:
* Relax NG schema files for the BNML eContracts
Schema, including all BNML
Standard files. In the BNML Standard Schema, the Relax
NG compact syntax
version is the normative schema.

* XSD versions that are automatically generated from
the Relax NG version.

* A DTD version that is intended only to assist TC
members to understand the
schema structure. While it can be used to validate
documents, it is not
structured as a development platform.

* A ReadMe file that provides a quick introduction to
the schema files and
structure.

* The BNML Schema customization guide.

* A set of example contracts and other documents in
XML that are marked up
using the BNML Schema. These documents are all valid
under BNML Standard and
BNML eContracts but they were all created using other
variants in an XML
editor that provides auto numbering and cross
reference facilities. The
files contain attribute values that are not defined in
the included Schema.
They are simply examples to demonstrate use of the
schema. The final
eContracts Schema may or may not include those values.

* An example BNML customization file from Elkera's
XML-2-Go Suite. Normally,
all customization of the BNML Schema is carried out in
a single
customization file, as shown in this example.

I look forward to working with TC members to finalise
the TC's
specification.

Regards
Peter Meyer

------------------------------------------------------------------------
Elkera Pty Limited (ACN 092 447 428)
Email: pmeyer@elkera.com
Ph: +61 2 8440 6900 * Fax: +61 2 8440 6988
http://www.elkera.com

Attachments

889767583-BNML contribution 2005-09-21.zip