dotnet xml: the first thing I searched the internet is what is the XML Binding?
also while I;m reading the eSCORTE4js for SCORM i noticed the following
comment
// these functions handle the conversion to/from the IEEE 1484_11_3 XML
binding values
what this means?

[quoted text, click to view]

It means the functions following that comment are responsible for bridging to
and from the XML representations of objects related to a Computer-managed
Instruction (CMI) system. These objects might be lesson grades, course
enrollments, student preferences, etc.

They can be represented as text values sometimes, for example, "C" can be
used to encode that a lesson is good for credit, and "N" indicates that it is not
for credit. According to 1484.11.1 Data Model, Section 6.2, the "Credit"
data element is the fourth one in the Core object exchanged within CMI
applications.

It follows then, that these records can have an XML schema applied to them
(a markup vocabulary replete with angle brackets, standardized tag names
and expected attributes, and the structure a valid document must conform to
in order to be treated as one of these objects exchanged within a CMI app).

XML binding is, in general, the process of mapping between a business object
model (in the case of eSCORTE4js, objects describing courses, schedules,
student performance, etc.) and an XML document. Normally, it's not just to
get the information from the business objects into any XML document, but
one that conforms to a published XML schema definition (XSD). This lets
the XML document be exchanged and shared across systems written by
potentially different vendors, with some guarantee that properly-conformant
systems will be able to interoperate with each other.

The most common vehicle nowadays for the exchange of these XML docs
is the SOAP envelope, and Web Services, over HTTP.

More information is available in files under,

http://ltsc.ieee.org/wg11/files/

The 1484_11_3_D6.doc is a few years old, however, and is a snapshot from
a time apparently before the Working Group considered an XML binding for
Web Services. It does discuss what formatting was expected (at the time, be
aware that many drafts go obsolete without ever having a concrete implemen-
tation reach market) when CMI objects were posted over the HTTP protocol.
You can probably find more up-to-date information on sites discussing the
SCORM, and other applications based on IEEE 1484.11.


Derek Harmon