head	1.7;
access;
symbols;
locks; strict;
comment	@# @;


1.7
date	2009.11.25.03.14.37;	author GarryJolleyRogers;	state Exp;
branches;
next	1.6;

1.6
date	2009.11.20.02.45.30;	author LeeBelbin;	state Exp;
branches;
next	1.5;

1.5
date	2007.03.06.17.30.00;	author TWikiGuest;	state Exp;
branches;
next	1.4;

1.4
date	2006.05.04.11.26.28;	author GregorHagedorn;	state Exp;
branches;
next	1.3;

1.3
date	2004.06.21.11.30.04;	author GregorHagedorn;	state Exp;
branches;
next	1.2;

1.2
date	2003.10.16.04.04.19;	author BobMorris;	state Exp;
branches;
next	1.1;

1.1
date	2003.10.11.05.38.36;	author BobMorris;	state Exp;
branches;
next	;


desc
@none
@


1.7
log
@none
@
text
@%META:TOPICINFO{author="GarryJolleyRogers" date="1259118877" format="1.1" version="1.7"}%
%META:TOPICPARENT{name="ClosedTopicSchemaDiscussionSDD09"}%
---+!! %TOPIC%

Complex schemas may look overwhelming (see for example the XML Schema Schema at http://www.w3.org/2001/XMLSchema.xsd) but the fact is, complex schema-based applications can now have their infrastructure written by software. For Java, the Sun Java Databinding API, JAXB, systems like the Castor databinding system, http://www.exolab.org and the "Generate Code" command on XML Spy's DTD/Schema menu will generate all the marshalling and unmarshalling code given the Schema. (The latter two also can generate C++). These frameworks are all you need to convert between objects in the programming language and those in your schema. In particular, if you have an XML Schema for your own descriptive data, the only programing task you will have to emit or consume BDI.SDD_ is to write glue in the programming languge of your choice (if supported by the databinding framework you choose) between the two kinds of data (yours and SDDs). You never need to write anything that produces or consumes XML. That's the job of the framework.


-- Main.BobMorris - 11 Oct 2003@


1.6
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="LeeBelbin" date="1258685130" format="1.1" reprev="1.6" version="1.6"}%
d5 1
a5 1
Complex schemas may look overwhelming (see for example the XML Schema Schema at http://www.w3.org/2001/XMLSchema.xsd) but the fact is, complex schema-based applications can now have their infrastructure written by software. For Java, the Sun Java Databinding API, JAXB, systems like the Castor databinding system, http://www.exolab.org and the "Generate Code" command on XML Spy's DTD/Schema menu will generate all the marshalling and unmarshalling code given the Schema. (The latter two also can generate C++). These frameworks are all you need to convert between objects in the programming language and those in your schema. In particular, if you have an XML Schema for your own descriptive data, the only programing task you will have to emit or consume BDI.SDD is to write glue in the programming languge of your choice (if supported by the databinding framework you choose) between the two kinds of data (yours and SDDs). You never need to write anything that produces or consumes XML. That's the job of the framework.
d8 1
a8 1
-- Main.BobMorris - 11 Oct 2003
@


1.5
log
@Added topic name via script
@
text
@d1 2
d5 1
a5 3
%META:TOPICINFO{author="GregorHagedorn" date="1146741988" format="1.0" version="1.4"}%
%META:TOPICPARENT{name="ClosedTopicSchemaDiscussionSDD09"}%
Complex schemas may look overwhelming (see for example the XML Schema Schema at http://www.w3.org/2001/XMLSchema.xsd) but the fact is, complex schema-based applications can now have their infrastructure written by software. For Java, the Sun Java Databinding API, JAXB, systems like the Castor databinding system, http://www.exolab.org and the "Generate Code" command on XML Spy's DTD/Schema menu will generate all the marshalling and unmarshalling code given the Schema. (The latter two also can generate C++). These frameworks are all you need to convert between objects in the programming language and those in your schema. In particular, if you have an XML Schema for your own descriptive data, the only programing task you will have to emit or consume SDD is to write glue in the programming languge of your choice (if supported by the databinding framework you choose) between the two kinds of data (yours and SDDs). You never need to write anything that produces or consumes XML. That's the job of the framework.
a8 1

@


1.4
log
@none
@
text
@d1 2
@


1.3
log
@none
@
text
@d1 7
a7 6
%META:TOPICINFO{author="GregorHagedorn" date="1087817404" format="1.0" version="1.3"}%
%META:TOPICPARENT{name="SchemaDiscussionSDD09"}%
Complex schemas may look overwhelming (see for example the XML Schema Schema at http://www.w3.org/2001/XMLSchema.xsd) but the fact is, complex schema-based applications can now have their infrastructure written by software. For Java, the Sun Java Databinding API, JAXB, systems like the Castor databinding system, http://www.exolab.org and the "Generate Code" command on XML Spy's DTD/Schema menu will generate all the marshalling and unmarshalling code given the Schema. (The latter two also can generate C++). These frameworks are all you need to convert between objects in the programming language and those in your schema. In particular, if you have an XML Schema for your own descriptive data, the only programing task you will have to emit or consume SDD is to write glue in the programming languge of your choice (if supported by the databinding framework you choose) between the two kinds of data (yours and SDDs). You never need to write anything that produces or consumes XML. That's the job of the framework.


-- Main.BobMorris - 11 Oct 2003
@


1.2
log
@none
@
text
@d1 2
a2 2
%META:TOPICINFO{author="BobMorris" date="1066277059" format="1.0" version="1.2"}%
%META:TOPICPARENT{name="SchemaDiscussion"}%
@


1.1
log
@none
@
text
@d1 1
a1 1
%META:TOPICINFO{author="BobMorris" date="1065850716" format="1.0" version="1.1"}%
d3 2
a4 1
Coming soon
@