Re: [regrep] Re: Core Components Specifications

[David RR Webber - XMLGlobal <Gnosis_@compuserve.com>]

Message text written by Philip Goatly
> 
David,
             Please could you indicate what a verb script would look/looks
like .

             Is it a piece of 'Java,VB script, VB , Java Script C++, COBOL
:-)' code or some new ebXML language?

Thanks

Phil<

>>>>>>>>>>>>>>>

Phil,

XML provides four ways of doing this, either an inline CDATA section
where the script language source is embedded, or a URL reference
to an external script, with a MIMETYPE indicating the type of
executable content, or by using the XML itself as the script - as in done
with W3C SMIL multimedia script language, and of course the ebXML
BPSS points to steps and conditionals, or a Web service and WSDL
and SOAP connection details.   So in implementing verb
there are multiple ways, and you are not constrained to any one
particular executable language, and indeed you may provide one
or more instances depending on the operating environments you
need to support.

In addition the CCR/CRI can reference such external artifacts 
and provide 'wrapper' information about them - what BPSS 
they apply to, description, owner, version, industry domain
classification, and  noun elements that apply, and so forth.

So thinking about the ACORD example of "Amount Due" you can
construct the element definition and then point to either a JavaScript,
or Java class or VBScript or web service that is the verb 
calculation part.

Notice this is very much design time orientated, and if I had to
pick right now for runtime - I'd pick the web service approach,
followed next by having mirrored copies of verbs downloaded 
and verified from the registry but then running off my own server
to ensure the integrity of my local systems.

DW.