osdir.com
mailing list archive

Subject: RE: XML Schema Question - msg#00034

List: org.user-groups.dotnet.padnug

Date: Prev Next Index Thread: Prev Next Index
You can treat the schema document as an XML instance and validate it against
some other schema.

Andy Miller
Structured Solutions

StoreFront: http://www.sfaddons.com
BVC2004: http://www.bvdaddons.com
Support: http://support.structured-solutions.net

-----Original Message-----
From: padnug@xxxxxxxxxxxxxxx [mailto:padnug@xxxxxxxxxxxxxxx] On Behalf Of
Craig Wagner
Sent: Tuesday, February 07, 2006 10:52 AM
To: padnug@xxxxxxxxxxxxxxx
Subject: Re: [padnug] XML Schema Question

Unless I'm really missing something here, I think those references only
answer half of the question.

Here's the schema from my original message.

<xs:schema xmlns:xs=" http://www.w3.org/2001/XMLSchema"; xmlns:xx="
http://www.mycompany.com";>
<xs:complexType name="SomeType">
<xs:sequence>
<xs:element name="AccountNumber" type="xs:int"
xx:errorAction="fail"/>
<xs:element name="AccountName" type="xs:string"
xx:errorAction="truncate" xx:length="25"/>
</xs:sequence>
</xs:complexType>
</xs:schema>

The first part of the question was how to prevent someone from putting in
xx:foo="bar" when the only valid attributes that should be available are
xx:errorAction and xx:length. If I can get to that point restricting the
actual values associated with those attributes is fairly easy.

Sorry for the poorly worded original message. It was late.

On 2/7/06, Stuart Celarier <scelarier@xxxxxxxxxxxxx> wrote:
>
> You're asking about constraining facets [1] on simple types in XSD.
> Strings [2] can be restricted by enumeration [3]. Ints [4] can be
> restricted by minExclusive [5].
>
> Cheers,
> Stuart
>
> Stuart Celarier | Corillian Corporation
> INETA Membership Manager, PacWest region
>
>
> [1] http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/#SimpleTypeFacets
> [2]
> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#string
> [3]
> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-enu
> meration
> [4]
> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#int
> [5]
> http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-min
> Exclusive
>


[Non-text portions of this message have been removed]




Yahoo! Groups Links














Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

job posted on our website apply online only.

Know anyone interested in this. They need to apply online at http://www.planar.com/Careers/jobslist.html ********************* Essential Functions: Develop interfaces between the BPCS ERP system and other systems, including Customer Service Applications, Supply Chain, eCommerce and other website systems. Elicit and document user requirements. Assist with selection, implementation and support of purchased software, and/or the design, implementation and support of custom systems to meet requirements. Design and program efficient and accurate interfaces, queries and reports. Perform Technical Project Lead role, coordinating IT and cross-functional project activities. Manage multiple priorities. Negotiate and schedule deliverables with end users. "Own" and support assigned applications. Develop training materials and deliver training to system users. Support corporate IT/IS initiatives and programs. Adhere to departmental standards. Drive the development and selection of IT architecture and development tools. Other Responsibilities: Actively participate in Information Technology and customer team meetings and activities. Other tasks as needed to meet departmental and company goals and objectives. Qualifications: B.S. in Computer Science, Information Systems or related discipline. Minimum of eight years experience as a programmer/analyst required. C# and ASP.NET skills required. Minimum one year experience programming in Java. XML experience a plus. Experience with report development in Oracle Discoverer or Crystal Reports tools desired. Experience with Microsoft SQL Server required. Strong written and verbal communication skills. Demonstrated presentation and training skills. Demonstrated dedication to producing quality work and completing tasks within specified time frames. In-depth knowledge of standard software development lifecycle process is required. Julie Aldridge Web Programmer / Analyst Planar Systems, Inc. Phone: (503) 748-7935 www.planar.com ______________________________________________________________________ This e-mail, and any attachments, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. It is the property of Planar Systems, INC. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, any attachments thereto, and use of the information contained, is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the original and any copy thereof. ______________________________________________________________________ [Non-text portions of this message have been removed]

Next Message by Date: click to view message preview

Efficacy of MCSD??

Hi Benjamin and the PADNUG, Is it still worthwhile to get the MCSD at this point? Visual Studio 2005 just came out. It is my understanding that the MCSD exams cover Visual Studio 2003. I can't seem to find any information on the Microsoft web site with regard to the MCSD being updated to reflect the release ot Visual Studio 2005. So...is it worthwhile to get the MCSD at this time, or should one wait until the MCSD is updated to reflect Visual Studio 2005? Sincerely, Victor Soich On 2/7/06, jackdan0921 <jackdan0921@xxxxxxxxx> wrote: > Benjamin, > > PSU offers .NET classes for the MCAD and MCSD Certifications the > class is held at the CAPITAL Center in Beaverton. I am currently > attending this class but the next one will start March, 18th. Here > is the URL for the MCAD and MCSD. > http://www.pdc.pdx.edu/it/mcad.shtml > http://www.pdc.pdx.edu/it/mcsd.shtml > > Dan > > --- In padnug@xxxxxxxxxxxxxxx, "Benjamin" <zobrakster@...> wrote: > > > > > > > > I'm looking for .net classes. I have a base understanding but am > > looking for a school or midlevel classes I can take. My work is > willing > > to pay for them but I can't find anyone offering? > > > > > > > > > > SPONSORED LINKS > > > Portland oregon attorney > Portland oregon home loan > Portland oregon web design > > Portland oregon real estate > Portland oregon real estate agent > Portland oregon real estate listing > > ________________________________ > YAHOO! GROUPS LINKS > > > Visit your group "padnug" on the web. > > To unsubscribe from this group, send an email to: > padnug-unsubscribe@xxxxxxxxxxxxxxx > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. > > ________________________________ > >

Previous Message by Thread: click to view message preview

Re: XML Schema Question

Unless I'm really missing something here, I think those references only answer half of the question. Here's the schema from my original message. <xs:schema xmlns:xs=" http://www.w3.org/2001/XMLSchema" xmlns:xx=" http://www.mycompany.com"> <xs:complexType name="SomeType"> <xs:sequence> <xs:element name="AccountNumber" type="xs:int" xx:errorAction="fail"/> <xs:element name="AccountName" type="xs:string" xx:errorAction="truncate" xx:length="25"/> </xs:sequence> </xs:complexType> </xs:schema> The first part of the question was how to prevent someone from putting in xx:foo="bar" when the only valid attributes that should be available are xx:errorAction and xx:length. If I can get to that point restricting the actual values associated with those attributes is fairly easy. Sorry for the poorly worded original message. It was late. On 2/7/06, Stuart Celarier <scelarier@xxxxxxxxxxxxx> wrote: > > You're asking about constraining facets [1] on simple types in XSD. > Strings [2] can be restricted by enumeration [3]. Ints [4] can be > restricted by minExclusive [5]. > > Cheers, > Stuart > > Stuart Celarier | Corillian Corporation > INETA Membership Manager, PacWest region > > > [1] http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/#SimpleTypeFacets > [2] > http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#string > [3] > http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-enu > meration > [4] > http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#int > [5] > http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-min > Exclusive > [Non-text portions of this message have been removed]

Next Message by Thread: click to view message preview

RE: XML Schema Question

Craig, the short answer is that you cannot stop anyone putting anything in the xml document - however, you can fail the validation. Are you saying you want to know how to validate this doc so that errorAction and length are the only allowed attributes in the xx namespace? Or maybe I am just missing something in my old age :( Shaun McAravey SoftSource Consulting, Inc. 503.476.4427 Cell 971.327.0424 Office 971.327.0445 Fax NOTICE TO RECIPIENT: THIS E-MAIL IS MEANT FOR ONLY THE INTENDED RECIPIENT OF THE TRANSMISSION, AND MAY BE A COMMUNICATION PRIVILEGED BY LAW. IF YOU RECEIVED THIS E-MAIL IN ERROR, ANY REVIEW, USE, DISSEMINATION, DISTRIBUTION, OR COPYING OF THIS E-MAIL IS STRICTLY PROHIBITED. PLEASE NOTIFY US IMMEDIATELY OF THE ERROR BY RETURN E-MAIL AND PLEASE DELETE THIS MESSAGE FROM YOUR SYSTEM. THANK YOU IN ADVANCE FOR YOUR COOPERATION. -----Original Message----- From: padnug@xxxxxxxxxxxxxxx [mailto:padnug@xxxxxxxxxxxxxxx] On Behalf Of Craig Wagner Sent: Tuesday, February 07, 2006 10:52 AM To: padnug@xxxxxxxxxxxxxxx Subject: Re: [padnug] XML Schema Question Unless I'm really missing something here, I think those references only answer half of the question. Here's the schema from my original message. <xs:schema xmlns:xs=" http://www.w3.org/2001/XMLSchema" xmlns:xx=" http://www.mycompany.com"> <xs:complexType name="SomeType"> <xs:sequence> <xs:element name="AccountNumber" type="xs:int" xx:errorAction="fail"/> <xs:element name="AccountName" type="xs:string" xx:errorAction="truncate" xx:length="25"/> </xs:sequence> </xs:complexType> </xs:schema> The first part of the question was how to prevent someone from putting in xx:foo="bar" when the only valid attributes that should be available are xx:errorAction and xx:length. If I can get to that point restricting the actual values associated with those attributes is fairly easy. Sorry for the poorly worded original message. It was late. On 2/7/06, Stuart Celarier <scelarier@xxxxxxxxxxxxx> wrote: > > You're asking about constraining facets [1] on simple types in XSD. > Strings [2] can be restricted by enumeration [3]. Ints [4] can be > restricted by minExclusive [5]. > > Cheers, > Stuart > > Stuart Celarier | Corillian Corporation > INETA Membership Manager, PacWest region > > > [1] http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/#SimpleTypeFacets > [2] > http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#string > [3] > http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-enu > meration > [4] > http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#int > [5] > http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-min > Exclusive > [Non-text portions of this message have been removed] Yahoo! Groups Links
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by