Extending xCIL

[colin.wallis@ssc.govt.nz]

Hi Group

I'd appreciate your views on this thread circulating around NZ government at present..

Thanks
Colin


Hi, Guys,

Aye, that sounds like exactly the kind of issue that we are coming across with xCIL and I'm afraid I don't have any nice solutions. 

It's a bit hard to say how to handle it, not knowing what your requirements are, but you could extend the Record ComplexType and reuse it in your schema but then of course you'll end up with a Customer element from your instance schema namespace. Possibly? Maybe?


One option is to actually remove the offending <xs:any> from my version of
xCIL but this would contravene the current standard (but would probably
work with the new one when it comes out).


That sounds like exactly one of the options I've considered for tightening up the schema definitions but it has versioning issues and it effectively means rewriting the OASIS standard which I'm very hesitant about. 

I'd be very interested to see these questions / issues raised within the working group because it's not just an xCIL issue it's the kind of issue that will be relevant to implementing any formal schema as an E-Govt standard.

Sorry not to be of more help but it is comforting to hear that we are all sharing the same woes.

Cheers,

Fraser
Fraser Crichton
Web Developer
www.solnetsolutions.co.nz


Colin.Wallis@ssc.govt.nz wrote: 
Hi Antony

You are quite right with respect to the status of xs:any . It has been voted
to remove it from the next revisions due out next year on both xCIL and
xNAL, NL, AL etc.

We do not have personal experience of xCIL here..yet.

But I have copied Paul and Fraser (via Solnet) who might know. Fraser has
first hand experience of the joys of xCIL..don't you Fraser!

Cheers

Colin

-----Original Message-----
From: Antony Williams (Government Agency name ommitted by CW)
Sent: Friday, 29 October 2004 11:17 a.m.
To: Colin.Wallis@ssc.govt.nz
Subject: Extending xCIL


Colin, I am attempting to define a schema based on OASIS' xCIL. I need
to add additional attributes to the customer record. I have tried to do
this by extending the xCIL customer and adding the attributes to the sub
type. The problem is that xCIL defines the <xs:any> element which
prevents me from doing this. I don't want to extend using this <xs:any>
because it only allows you to add one attribute and it is a pretty ugly
way of doing it.

I have contacted OASIS regarding this and they say that they have had
discussions around this and are probably going to remove <xs:any> from
the schema.

Have you encountered this problem and do you have any suggestions. One
option is to actually remove the offending <xs:any> from my version of
xCIL but this would contravene the current standard (but would probably
work with the new one when it comes out).

cheers
Antony