[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
Due to using the ATG2-UnqualifiedDatatype schema module there is a change
concerning the currency code list. ATG2 has a predefined code list for
currency codes. We assumed that the UBL CurrencyCodeType and
</pre>
</blockquote>
<pre wrap=""><!---->UBLAmountType
</pre>
<blockquote type="cite">
<pre wrap=""> should also use this predefined code list. In order to do this we had to
change the values for code list agency and code list name. As a result
CurrencyCodeType is now located in the SpecializedDataType schema,
</pre>
</blockquote>
<pre wrap=""><!---->because
</pre>
<blockquote type="cite">
<pre wrap=""> it does not have an own simpletype for the content. I think this would
be a
good chance to do this in general, to store all specialized data types in
the SpecializedDataType schema including the code lists. This would be
</pre>
</blockquote>
<pre wrap=""><!---->the
</pre>
<blockquote type="cite">
<pre wrap=""> same behavier like ATG2. Another item is to get rid off UBLAmountType.
It is now redundant.
Anne:
I was under the impression that these 'common' .xsd files would be coming
</pre>
</blockquote>
<pre wrap=""><!---->>from ATG2 (CCT, CCP, UDT and possibly SDT depending on what we needed).
</pre>
<blockquote type="cite">
<pre wrap="">But the diffs I see are:
- the new CBC now has our UBL-defined codes
- SDT has CurrencyCode and AmountType; it used to only have AmountType
- Unspecialized DataTypes is now Unqualified DataTypes
- besides code lists there are several new files in the 'common' directory
- there is no CCT
- CCP is the same
I think it would be helpful at this point to have a mapping from UBL 1.0
common files to UBL 2.0 common files so we
- know where the line is drawn between ubl files and atg2 files,
- can align names of the remaining files,
- can understand what if anything should be kept in the ndrs
in reference to any of the resulting files in 'common'
Regarding 'AmountType', I'm not sure why it was created,
so Tim should take a look and comment on that move.
Separately, regarding schemas, David is suggesting we put all code lists
in SDT.
Category 2
----------
Codes that are created and maintained external to UBL,
some likelihood of changes between UBL releases.
UBL has no control over whether or when they change.
1. UBL-CodeList-AllowanceChargeReasonCode-1.0.xsd (UN/ECE 4465)
Values: See <a class="moz-txt-link-freetext" href="http://www.unece.org/trade/untdid/d03a/tred/tred4465.htm";>http://www.unece.org/trade/untdid/d03a/tred/tred4465.htm</a>.
Notes:
Appears to be exact duplicate of UNECE 4465 code,
'Adjustment reason description code'.
We call it 'AllowanceChargeReasonCode' though.
What is the impact of changing the name of the code to match 4465?
2. UBL-CodeList-ChannelCode-1.0.xsd (UN/ECE 3155)
Values: See <a class="moz-txt-link-freetext" href="http://www.unece.org/trade/untdid/d03a/tred/tred3155.htm";>http://www.unece.org/trade/untdid/d03a/tred/tred3155.htm</a>.
Notes:
Appears to be exact duplicate of the UNECE 3155 code,
'Communication address code qualifier'.
We call it 'ChannelCode, though.
What is the impact of changing the name of the code to match 3155?
3. UBL-CodeList-CountryIdentificationCode-1.0.xsd
Values: See
<a class="moz-txt-link-abbreviated" href="http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1";>www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1</a>.
</pre>
</blockquote>
<pre wrap=""><!---->h
</pre>
<blockquote type="cite">
<pre wrap="">tml
Notes:
We only use the first part of iso 3166 (3166-1).
iso 3166-2 has the country subentities but we didn't implement that.
4. UBL-CodeList-CurrencyCode-1.0.xsd
Values: See
<a class="moz-txt-link-freetext" href="http://www.bsi-global.com/British_Standards/currency/index.xalter";>http://www.bsi-global.com/British_Standards/currency/index.xalter</a>.
Notes:
In the latest schemas from David, this is now in the SDT.
See note under ATG2 codes (category 1a).
Further discussion is probably needed on these.
5. UBL-CodeList-PaymentMeansCode-1.0.xsd
Values: See <a class="moz-txt-link-freetext" href="http://www.unece.org/trade/untdid/d03a/tred/tred4461.htm";>http://www.unece.org/trade/untdid/d03a/tred/tred4461.htm</a>
Notes:
Exact duplicate of UNECE 4461 'Payment Means Code'.
Further considerations:
- This breakdown doesn't take into account that some of the category 2
</pre>
</blockquote>
<pre wrap=""><!---->codes
</pre>
<blockquote type="cite">
<pre wrap=""> will be coming from gefeg. Don't know if we need to make that
distinction.
- In looking at this again, going back to the original lists of codes we
have
in our models, these were only the beginning - the codes we though we had
to define in order to achieve a positive out-of-the-box experience.
- The attached spreadsheet has a complete list of codes as they were in 1.0
Beta. I'm not sure if we should, before 2.0, look at these again and if
we don't add any more codes to the UBL codes, possibly give some guidance
on how to use the codes for which we don't point to un codes or give
values.
- We seem to be going back to a twist on the original model we had where
we provided xml files with the code values (placebo, etc). This is
in some ways comforting, in others disconcerting. I can't recall the
issues raised in that implementation that caused us to pull it, but I
believe the schema template will solve that problem.
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
</pre>
</blockquote>
<pre wrap=""><!---->OASIS
</pre>
<blockquote type="cite">
<pre wrap="">at:
<a class="moz-txt-link-freetext" href="https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php";>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php</a>
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
</pre>
</blockquote>
<pre wrap=""><!---->OASIS
</pre>
<blockquote type="cite">
<pre wrap="">at:
<a class="moz-txt-link-freetext" href="https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php";>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php</a>
</pre>
</blockquote>
<pre wrap=""><!---->
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in OASIS
at:
<a class="moz-txt-link-freetext" href="https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php";>https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php</a>
</pre>
</blockquote>
</body>
</html>
--Boundary_(ID_IEpIWikBja94j47ryZW5+Q)--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]