Re: [ubl] Minutes of Atlantic UBL TC call 29 June 2005 - DECISIONON REUSABLE

[Tim McGrath <tmcgrath@portcomm.com.au>]

I confess to be confused and disappointed that the point of this 
proposal seems to have been lost.

We are trying to establish a scalable architecture for managing BIE 
libraries.  As spreadsheets are are primary modeling tool it doesn't add 
any value to say it wouldn't be necessary if we weren't using them.

As far as the CCTS interpretation goes, I agree with Stephen that there 
should be no 'core' BIEs because it clashes with the concepts of CCTS. 
 But it does not follow there cannot be 'common' BIEs.  In fact Michael 
Dill has been advocating this for some time with his 're-use of BIEs' 
ideas.  BIEs can (and should) be re-used wherever possible.  It follows 
then that we can (and should) have 'common' ones.

The whole idea behind this proposal was to make the library of 'common' 
BIEs more manageable and modular.

The CCTS approach of adding context by indicating the context drivers is 
not an alternative (in fact it complements this idea).  It is a variant 
on the idea of adding a column to the spreadsheet and marking it 
"procurement", "transportation" or "common".  We already have the column 
and it is called "Context: Business Process".

What we are suggesting is that the UBL 2.0 spreadsheet is likely to have 
well over 1000 'common' BIEs in one spreadsheet.  Many of these are only 
'common' to one context (eg procurement). So why not split the 
spreadsheet into more managable chunks based on this criteria?  I don't 
think this has anything to do with CCTS.

The problem we now have is that over the next 5 weeks we have to build 
the stage 1 models for UBL 2.0 and we are moving away from making 
decisions about how to do this.  We need a timeframe for when this issue 
is to be resolved and it should be days rather than weeks.

>DECISION ON REUSABLE
>
>   AGREED that the proposed change is primarily for users of the
>   spreadsheets and would not be necessary if using a tool that
>   was context-aware.
>
>   StephenG: Strictly speaking, there are no "common" or "core"
>   BIEs; they exist only in context.  Furthermore, it appears that
>   this problem is addressed by the CCTS mechanism for specifying
>   context and that we might get the intended benefit by
>   completely implementing the CCTS context code lists etc.
>
>   AGREED that we should check with our CCTS experts to determine
>   whether the CCTS approach provides a suitable solution before
>   continuing this discussion.
>
>  
>
-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160

DOCUMENT ENGINEERING: Analyzing and Designing Documents for Business Informatics and Web Services
http://mitpress.mit.edu/catalog/item/default.asp?sid=632C40AB-4E94-4930-A94E-22FF8CA5641F&ttype=2&tid=10476