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


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

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

Subject: RE: [ubl-ndrsc] Complete Package: UBL_Library_0p70_22-01-03b.zip

Hello Bill,

in (1), we have to ask the LCSC. Otherwise, we can define on complex type and two global declared elements based on this complex type. We need two global elements, because there are two different dictionary entry names. For this requirement, I have to develop a further function. Because, I didn't
implemented this feature yet.

Why and where do you need an namespace and a prefix 'bie'. In the schema for reusable types? Than, we will get always the prefix 'bie' in every instance. Is that the way, which we defined it?

Kind regards,


-----Original Message-----
From: Burcham, Bill [mailto:Bill_Burcham@stercomm.com] 
Sent: Mittwoch, 22. Januar 2003 20:50
To: Stuhec, Gunther; 'ubl-lcsc@lists.oasis-open.org '; 'ubl-ndrsc@lists.oasis-open.org '
Subject: RE: [ubl-ndrsc] Complete Package: UBL_Library_0p70_22-01-03b.zip

Why in (1) do we need another ABIE (Foreign Exchange_ Contract. Details)
with a structure identical to an existing one (Transport_ Contract.
Details).  Why does not ASBIE 'Exchange Rate.Foreign Exchange.Contract'
simply refer to the original ABIE?  (of course, if it did so, its dictionary
entry name would change but you get the point)

Also, as a reminder Ken's issues regarding namespaces: a) targetNamespace
and b) prefix 'bie' are still outstanding.

-----Original Message-----
From: Stuhec, Gunther [mailto:gunther.stuhec@sap.com] 
Sent: Wednesday, January 22, 2003 12:52 PM
To: 'ubl-lcsc@lists.oasis-open.org '; 'ubl-ndrsc@lists.oasis-open.org '
Subject: [ubl-ndrsc] Complete Package: UBL_Library_0p70_22-01-03b.zip

Hello all,

I generated a new package of our UBL Library 0p70 now. You will find this
package as an attached zip-file. 

As agreed, I fixed all issues. That is in detail:

1.) There is in the Excel Spreadsheet a new ABIE, called "Foreign Exchange_
Contract. Details". The structure of this ABIE is the same as "Transport_
Contract. Details" but it will be used in the ABIE "Exchange Rate. Details"
as an ASBIE.

2.) I didn't deleted the ABIE "Accounts_ Contact. Details". Sue said that
this reusable ABIE could be used later. It makes no problems, if we have
this ABIE in our Reusable Types Library.

3.) I deleted the extension ".xsd" from each namespace within the
configuration files.

4.) According Dave, I deleted the attribute "id" from each global declared
element. All complex types and referred elements still have the attribute
"id" with an unique identifier.

After automatic generatic (without any manual manipulating), all schemas are
valid in XMLSpy, now.

If you still find any problems, please let me know, as soon as possible. 

Kind regards,


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

Powered by eList eXpress LLC