Re: [ubl-lcsc] pre-draft model for appraisal and initial change log

["Stephen Green" <stephen_green@seventhproject.co.uk>]

Hi all

 

I do apologise for burdening everyone with large attachments again in this e-mail. This is in advance of discussion on Tuesday.

 

They include (all with contents as in the beta, just with extra whitespace removed):

a) an amended version of Michael's spreadsheet (DataType columns replaced and TBG17 columns moved to the right hand side)  (UBL-Combined-1_0-draft-0-1.zip)

b) as in a) but document models in separate spreadsheets (UBL-1_0-models-draft-0-1.zip)

 

The second, b) , in line with Tim's suggestion, still has the TBG17 data (minus the extra rows of headings) but on the right. It allows the use of UBLish (tried successfully) as well, I hope as (with adjustment?) Michael's EF. Tim prefers the complete

separation of the two formats into two spreadsheets but perhaps the fact that UBLish isn't affected means we

could benefit from the minimising of maintenance because of the easier use of formulae with this combination.

On the other hand, it does require a bit of diversion from what we have been doing till now. One might of course

just use this side-by-side structure for pre-submission maintenance and delete the TBG17 columns, after copying their contents

(as strings) into another spreadsheet for submission, before publishing the former as UBL without the TBG17 side.

 

I reckon that b) includes a means of distinguishing documents from reusable

(as per ND Rules?, though documents could be treated as just extra ABIEs in reusable and with something like

<xsd:element name="Invoice" type="cat:Invoice/>

in a document Schema - perhaps out of the question,

though perhaps a step towards greater BBIE reuse e.g. of IssueDate which could then be cat:IssueDate).

I don't see that combining the models into one spreadsheet allows this as it is - whereas separate spreadsheets seem

more in line with the TBG17 submission format as well as being more intuitive ( a spreadsheet per document ). How,

without prior knowledge of what is a document for a separate Schema, would one (i.e. a tool) know what to include in reusable as an ABIE and should be separated into a unique top-level document Schema?

A new bit of syntax for this would have to be devised and time is now very short.

 

All the best

 

Steve

 

UBL-Combined-1_0-draft-0-1.zip

UBL-1_0-models-draft-0-1.zip