OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-dev message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ubl-dev] Treasury Tag Pattern: to 'glue' two instances having different schemas

I note an errata below:

The ATG2 SBDH package has a pattern
suggesting that the top element (the tag
name of the 'Treasury Tag') is called

An example of how part of such a document
might look:

<?xml version="1.0" encoding="UTF-8"?>
xmlns:xbrli="http://www.xbrl.org/2001/instance"; ...
<!-- not all the various namespaces needed to have been declared here -->
xmlns:xbrli="http://www.xbrl.org/2001/instance"; ...
... rest of XBRL-GL ledger document ...
... rest of UBL Order document ...

The schema for this StandardBusinessDocument
would have the document schemas imported
and just the single element and complex type:

<xsd:element name="StandardBusinessDocument"
<xsd:complexType name="StandardBusinessDocumentType">
    <xsd:element ref="po:Order"/>
    <xsd:element ref="xbrli:group"/>

I'd suggest that there are the following reasons
for the Treasury Tag / StandardBusinessDocument
pattern above:

1.  specifies interface between, say, finance systems
2.  facilitates storage
3.  facilitates processing such as to flat file for legacy systems
4.  facilitates simplicity of specification for interoperability
      such as "must use XBRL-GL + UBL + ..."

All the best

Stephen Green

----- Original Message ----- 
From: "Stephen Green" <stephen_green@seventhproject.co.uk>
To: <ubl@lists.oasis-open.org>; <ubl-dev@lists.oasis-open.org>
Sent: Monday, July 11, 2005 8:49 AM
Subject: [ubl-dev] Treasury Tag Pattern: to 'glue' two instances having
different schemas

> Regarding the issue of how to bring together a document and data from
> another schema (thanks to Duane for the suggestion along the lines below):
> I guess what we need is the XML equivalent of a 'treasury tag'.
> This treasury tag is then a 'pattern' (in the software design sense)
> rather than a specific schema.
> It goes something like this:
> Treasury Tag Pattern
> ------------------------
> Requirement: a way to clip together two or more XML documents
> so that these can be treated as a single file.
> Structure:
> A schema is created with a document top level element. The top level
> element can have any name but a suggestion is 'StandardDocument'.
> This acts as a container element to one or more elements which
> are the document top level elements of the XML files to be contained.
> The schema imports the schemas of the contained XML files.
> Consequences:
> There is no need to use xsd:any and all data may be associated
> with namespaces
> This has the following benefits and liabilities -
> benefits - data is more easily recognised as being appropriate
> liabilities - a schema has to be created for each set of documents
> There is also the benefit that the set of documents may be validated
> as one.
> For storage it may be preferable to remove the containing element
> so that each document is stored separately with its own namespace
> and types.
> All the best
> Stephen Green
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]