I'd love to hear more about this if you've got the time - offline if needed. Especially some of the pros and cons you found. Thanks a lot!
Brady Gaster Executive Technology Services [EMAIL PROTECTED] 480.575.3625 office 602.790.2081 mobile > -----Original Message----- > From: Hurley, Mark [mailto:Mark.Hurley@;TURNER.COM] > Sent: Tuesday, October 29, 2002 2:29 PM > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] Creating dynamic types from XSD > > > Brady, > > I'm just catching up to the discussion. > > But when we began to write our application in Beta1, we did just that. > > To keep my explanation short: > > 1) we leveraged Xsd's as a contract between client and middle > tier (the server validated the received xml upon receipt) > 2) we leveraged Xsd's on the client to provide basic > validation on the winforms > 3) look up values stored in the database (ie: enums) are > dumped to Xsd enumeration files which are included into the > main Xsd's. > > The Xsd's provide both pros and cons, when compared to using the WSDL. > > HTH... > > Mark > > :> -----Original Message----- > :> From: Brady Gaster [mailto:Brady.Gaster@;WELLSFARGO.COM] > :> Sent: Tuesday, October 29, 2002 12:27 PM > :> To: [EMAIL PROTECTED] > :> Subject: Re: Creating dynamic types from XSD > :> > :> > :> Ah - that's the next hurdle. It's KINDA what I'm working > on. :> In essence, I'm :> thinking of ways to actually wrap > UI around these schema so :> that forms can :> be created to > collect data that'll be put into XML (that's :> then > validated :> against the schema, of course :)) and saved back > to the :> database. Could you :> send some links about > xsd:appInfo - I'm unfamilliar with that and its :> > usefulness. :> :> :> Brady Gaster :> Executive Technology > Services :> [EMAIL PROTECTED] :> 480.575.3625 > office :> 602.790.2081 mobile :> :> :> > -----Original > Message----- :> > From: Philip Nelson > [mailto:panmanphil@;YAHOO.COM] :> > Sent: Tuesday, October 29, > 2002 9:17 AM :> > To: [EMAIL PROTECTED] > :> > Subject: Re: [ADVANCED-DOTNET] Creating dynamic types > from XSD :> > :> > :> > > Here's the problem - i'd like to > have the ability to read :> > schema as it :> > > is > extracted from the database. Then, using the schema :> > > itself, create :> > > ASP.NET (or whatever else i can think > of) forms to collect :> > data that :> > > will be used by > other areas of the system. \ :> > :> > Most likely for any > real sort of generated UI, you will need :> > metadata not > present in the database to help you. Are :> > booleans check > boxes? The application may limit values to :> > specific > choices, but how do you get that from a database and :> > > present a radio button group? The schema answer to this is > :> > the xsd:appInfo annotations. However, xsd provides no > support :> > at all AFAIK so you would have to parse the > schema as xml and :> > access the data that way. On the ui > side you could look at :> > XUL for ideas, which is an xml > language to describe user :> interfaces. :> > :> > This > sounds like a really big project to me ;-) :> > :> > :> > :> > > :> > > :> > > [1] :> > > <?xml version="1.0" > encoding="utf-8"?> :> > > <xs:schema > xmlns:mstns="http://mysite.com/ontology > :> > > <http://mysite.com/ontology> " > xmlns="http://mysite.com/ontology :> > > > <http://www.wellsfargo.com/ontology> " :> > > elementFormDefault="qualified" :> > > > targetNamespace="http://mysite.com/ontology > :> > > <http://www.wellsfargo.com/ontology> " > :> > > xmlns:xs="http://www.w3.org/2001/XMLSchema > :> > > <http://www.w3.org/2001/XMLSchema> "> > :> > > <xs:element name="AccountHolder" type="AccountHolder" /> > :> > > <xs:complexType name="AccountHolder"> > :> > > <xs:sequence> > :> > > <xs:element name="BankCustomer" type="Customer" /> > :> > > <xs:element name="AccountInformation" type="Account" /> > :> > > </xs:sequence> > :> > > </xs:complexType> > :> > > <xs:complexType name="Customer"> > :> > > <xs:sequence> > :> > > <xs:element name="Firstname" type="xs:string" /> > :> > > <xs:element name="Lastname" type="xs:string" /> > :> > > <xs:element name="Gender" type="Gender" /> > :> > > </xs:sequence> > :> > > </xs:complexType> > :> > > <xs:simpleType name="Gender"> > :> > > <xs:restriction base="xs:string"> > :> > > <xs:enumeration value="Male" /> > :> > > <xs:enumeration value="Female" /> > :> > > </xs:restriction> > :> > > </xs:simpleType> > :> > > <xs:complexType name="Account"> > :> > > <xs:sequence> > :> > > <xs:element name="Balance" type="xs:float" /> > :> > > </xs:sequence> > :> > > </xs:complexType> > :> > > </xs:schema> > :> > > > :> > > Brady Gaster > :> > > Executive Technology Services > :> > > [EMAIL PROTECTED] > :> > > 480.575.3625 office > :> > > 602.790.2081 mobile > :> > > > :> > > > :> > > You can read messages from the Advanced DOTNET > archive, :> unsubscribe :> > > from Advanced DOTNET, or > subscribe to other :> DevelopMentor lists at :> > > > http://discuss.develop.com. :> > :> > :> > > __________________________________________________ > :> > Do you Yahoo!? > :> > HotJobs - Search new jobs daily now > :> > http://hotjobs.yahoo.com/ > :> > > :> > You can read messages from the Advanced DOTNET archive, > :> > unsubscribe from Advanced DOTNET, or subscribe to other > :> > DevelopMentor lists at http://discuss.develop.com. > :> > > :> > :> You can read messages from the Advanced DOTNET archive, > :> unsubscribe from Advanced DOTNET, or > :> subscribe to other DevelopMentor lists at > http://discuss.develop.com. :> > > You can read messages from > the Advanced DOTNET archive, unsubscribe from Advanced > DOTNET, or subscribe to other DevelopMentor lists at > http://discuss.develop.com. > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
