Hi Jim,
See inline answers to your questions:
> "Brain, Jim" wrote:
>
> I am asking this question on behalf of the ACORD Insurance standards
> body.
>
> ACORD is working on the next version of their specifications, and
> specifically working on extensibility options to give Insurance
> carriers a way to extend the base insurance schemas to offer carrier
> specific extensions. Xsd:redefine has been proposed as the most
> elegant solution for this issue, but it seems the code generation
> tooling available does not support csd:redefine. Since I have
> previously been active on this group and I use Castor, I'd like to ask
> the principals in development a few questions to relay to the ACORD
> working group:
>
> � Is there a tentative date by which xsd:redefine will be
> accepted and handled within Castor?
No.
> � Is the lack of current support a simple development time
> issue, or is there some issue with support of xsd;redfine and mapping
> it to a suitable OO paradigm?
>
>From my perspective it's more a matter of development time and priority.
Since redefine is based on includes (treated as if the included schema
was part of the including schema) I think it's reasonable to be able to
implement the redefinition support without having difficulties related
to the Java language itself and any programming language paradigms.
Basically the redefine would simply "replace" the included definition,
almost in the same manner that restriction/extension works except that
the original definition would no longer be referenceable from other
schema definitions, only the redefine would be used.
> � Can someone estimate the extent of development time needed to
> fully support this feature of XML Schema?
I would imagine it would take someone at least one man week to code and
test. Note that it is simply an estimation and should not be taken that
such support for redefines will be available in that time frame, or that
anyone has offered to code the support.
> � Is there any apprehension concerning support for this XML
> Schema construct?
>
Not from me, it's simply a matter of priority and time. In my opinion
there are other more pressing issues that deserve my time on Castor, but
that's just me. There may be others out there who feel that xsd:redefine
is critical to their needs.
--Keith
> A timely response would be appreciated, as the working group meets Dec
> 4 to select a final candidate for extensions mechanisms.
>
> Jim Brain
>
> AegonUSA
>
> Jim Brain, [EMAIL PROTECTED]
>
> "Researching tomorrow's solutions today."
>
> (319) 369-2070 (work)
>
> APPLICATIONS ARCHITECT, AFP-IT
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
