|
[XML-DEV Mailing List Archive Home]
[By Thread]
[By Date]
[Recent Entries]
[Reply To This Message]
Re: What techniques do you employ to ensure that your datais p
- From: Stephen D Green <stephengreenubl@gmail.com>
- To: "Costello, Roger L." <costello@mitre.org>
- Date: Tue, 25 Sep 2012 08:58:22 +0100
In working on a few business document markups a matter of high "level of importance" was the difference between an invoice and a credit note. I saw and heard various proposals for how
to do this which illustrate good and not-so-good practices: 1) have a document which is neither invoice nor credit note and add an attribute for documentType whose value could
be enumerated and include "Invoice" and "CreditNote" [not good, I thought] 2) have a document which is in essence an invoice let the amounts and totals be negative if it is a credit note
[not good, I thought] 3) have a separate invoice markup and credit note markup with the top elements 'Invoice' and 'CreditNote' respectively [good, I thought, and we did this for UBL]
Another example follows on from point 2): how to specify a negative amount in such a document - maybe people would prefer two separate elements for PositiveAmount and NegativeAmount, though in UBL we just decided to let
the minus sign or lack of it in the value for the Amount be the indicator.
---- Stephen D Green
On 24 September 2012 17:12, Costello, Roger L. <costello@mitre.org> wrote:
Hi Folks,
How carefully do you specify your data? Is it free from ambiguity and misinterpretation?
Although all data should be specified precisely and without ambiguity, the consequences of data being imprecise or ambiguous ranges from minor to catastrophic. There is a name for the latter data: level 1 data.
Level 1 (critical) data: the data must be specified
precisely with absolutely no ambiguity. For if the data
is misinterpreted, then there is a real
possibility of a loss of human life or financial,
political, or personal calamity.
When you create your XML Schemas do you identify the level of the data? For example, do your XML documents contains a <level> element:
<Document>
<level>level 1 (critical) data</data>
...
</Document>
Has anyone created an XML Schema for the various levels?
[Key Question:] If you have level 1 data what techniques do you employ to ensure that there is virtually zero chance for the data to be misunderstood or misinterpreted?
/Roger
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
|
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
| RSS 2.0 |
 |
| Atom 0.3 |
 |
| |
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
|
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please
click here.
|
|
Cart
