XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] XSD Question: what is the current recommendationregarding large values for maxOccurs?

There are some sensibility tests such as number of test steps in a  
logical procedure in the field (testing too low for an environment  
where remove and replace and return UUT to depot makes better  
logistical sense).   The problems
with this scenario:

1.  Field tech may have to skirt the recommendation and get it done  
anyway particularly in forward areas.   This is a policy issue at  
procurement.

2.  The XML production phase is the wrong place to test for that although
it's a handy way to find it in val/ver.

The problems I am seeing with limits (DTD/Schema related) are  
analogous though:  early binding of constraints for the wrong phase of  
the production, eg., requring information or limiting it at the wrong  
stage of production. This shows up when the procurement citation in  
the SOW is for a DTD/Schema designed to validate information at  
delivery (hand-off to customer or downstream distribution) instead of  
during production phases.   We've known about this issue for literally  
decades now and it seems to persist which tells me some XML systems  
training, that is real enterprise application knowledge, is missing.

The so-called 'enterprisey' complaints from web designers damaged the  
ecosystems because they were web-centric and ignored the processes of  
early information providers in very large systems design and fielding  
for the sake of the last programmers in the food chain.

len




Quoting John Cowan <cowan@mercury.ccil.org>:

> Michael Kay scripsit:
>
>> I still find it a little implausible that there are "business
>> requirements" not to have more than 500 Foo elements. What are these:
>> order lines in a purchase order? Employees in a department? Contact
>> names/addresses for a customer?
>
> Widgets in a shipping container, perhaps.
>
> --
> John Cowan   http://ccil.org/~cowan   cowan@ccil.org
> 'My young friend, if you do not now, immediately and instantly, pull
> as hard as ever you can, it is my opinion that your acquaintance in the
> large-pattern leather ulster' (and by this he meant the Crocodile) 'will
> jerk you into yonder limpid stream before you can say Jack Robinson.'
>         --the Bi-Coloured-Python-Rock-Snake
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS