[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: SV: [ubl] Business Rule Action (SG): Re: [ubl] Agenda forPacificUBL TC call 10|11 Oct
Bryan
The rule to which I'm refering (and this is in the relevant
scope of UBL 1.0 for this exercise, as I should have
pointed out, sorry) is
"[IND5] UBL conformant instance documents MUST NOT contain an element devoid of
content or null values."
Of course this means that the rule isn't broken if the element content is null but
not one or more of its attributes.
All the best
Steve
>>> Bryan Rasmussen <brs@itst.dk> 10/10/05 10:43:58 >>>
When you say:
"And although UBL does have a rule itself that an element cannot
be present with a null value, I thought it best to add this in the
rule."
I brought up at one point that it would be nice if the elements that were
obligatory that had string or tokenized string datatypes were constrained to
not be empty. This was vetoed on conference call though as I recall.
Is this what you mean by a null value?
Cheers
Bryan Rasmussen
-----Oprindelig meddelelse-----
Fra: Stephen Green [mailto:stephen_green@bristol-city.gov.uk]
Sendt: 10. oktober 2005 11:31
Til: ubl@lists.oasis-open.org
Emne: SV: [ubl] Business Rule Action (SG): Re: [ubl] Agenda for
PacificUBL TC call 10|11 Oct
Hi Bryan
The top level 'if' statement looks unnecessary but it does
indicate that there may be no occurances of the 'for-each'
and allows the final statement that where there is at least
one occurance then there must also be ...
I've not really intended to make the business rule a good
example of formal pseudo-code :-) (Ken would do a far better
job of that in actually writing the Schematron rules)
And although UBL does have a rule itself that an element cannot
be present with a null value, I thought it best to add this in the
rule.
All the best
Steve
>>> Bryan Rasmussen <brs@itst.dk> 10/10/05 10:11:43 >>>
I'm not sure if I understand the top level if then, given that the for each
itself seems to handle the requirements. What do you mean especially by not
null value though?
I'm thinking it seems reasonably easy to do as a schematron rule.
Cheers
Bryan Rasmussen
-----Oprindelig meddelelse-----
Fra: Stephen Green [mailto:stephen_green@bristol-city.gov.uk]
Sendt: 10. oktober 2005 10:34
Til: ubl@lists.oasis-open.org
Emne: [ubl] Business Rule Action (SG): Re: [ubl] Agenda for Pacific UBL
TC call 10|11 Oct
Here is the business rule for my action item from last week:
This is just a typical rule among an imaginary set of likely business rules
regarding the TaxTypeCode in a Value Added Tax (VAT) context:
(namespace prefixes omitted for clarity)
******************************************************************
If there is at least one occurance of an InvoiceLine which has
InvoiceLine/TaxTotal/TaxSubTotal/TaxCategory/TaxScheme/TaxTypeCode = 'VAT'
then
{
for each occurance of
InvoiceLine/TaxTotal/TaxSubTotal/TaxCategory[/TaxScheme/TaxTypeCode = 'VAT']
{
the corresponding InvoiceLine/TaxTotal/TaxSubTotal/TaxCategory/ID and
InvoiceLine/TaxTotal/TaxSubTotal/TaxCategory/Percent must each have a not
null value
and
if the corresponding InvoiceLine/TaxTotal/TaxSubTotal/TaxCategory/Percent
that value does not equal 0 or 0.0 or 0.00, etc
there must be an occurance
Invoice/TaxTotal//TaxSubTotal/TaxCategory[/TaxScheme/TaxTypeCode = 'VAT']
which has
Invoice/TaxTotal//TaxSubTotal/TaxCategory/ID =
InvoiceLine/TaxTotal/TaxSubTotal/TaxCategory/ID
}
}
and there must be one occurance of
Invoice/SellerParty/PartyTaxScheme/TaxScheme/TaxTypeCode = 'VAT' with a
corresponding non null Invoice/SellerParty/PartyTaxScheme/CompanyID
******************************************************************
NOTE: TaxScheme/TaxTypeCode here appears in three semantically separate
contexts (for the purpose of this rule) -
InvoiceLine/TaxTotal/TaxSubTotal/TaxCategory
Invoice/TaxTotal/TaxSubTotal/TaxCategory
and
Invoice/SellerParty/PartyTaxScheme
each having a potentially separate but likely equivalent set of enumerations
of which there is at least one member - 'VAT'
******************************************************************
All the best
Stephen Green
>>> <jon.bosak@sun.com> 10/10/05 00:20:16 >>>
Western hemisphere participants: note that this meeting takes
place Monday evening in your time zones.
AGENDA FOR PACIFIC UBL TC MEETING
00H30 - 02H30 UTC TUESDAY 11 OCTOBER 2005
17h30 - 19h30 Mon San Francisco
20h30 - 22h30 Mon Washington
08h30 - 10h30 Tue Hong Kong, Singapore, Perth, Beijing
09h30 - 11h30 Tue Seoul, Tokyo
10h30 - 12h30 Tue Sydney
#############################################
STANDING INFORMATION FOR UBL CONFERENCE CALLS
U.S. domestic toll-free number: (866)839-8145
Int. access/caller paid number: (865)524-6352
Access code: 5705229
#############################################
STANDING ITEMS
Additions to the calendar:
http://ibiblio.org/bosak/ubl/calendar.htm
Liaison reports: Tax XML TC, ebBP TC
Subcommittee reports: HISC, SBSC, PSC, TSC
Team reports: Code List, Digital Signatures, Catalogue
Review of Atlantic and Europe/Asia calls
Schedule review:
http://lists.oasis-open.org/archives/ubl/200508/msg00167.html
ACTION ITEM REVIEW
ACTION: TM to document the spreadsheet structure and format by
the first week of October. This means a prose description of
each column in the spreadsheets that we are now using.
(From Atlantic call) To be completed by 10/14.
ACTION: JB to revise the UBL 2.0 schedule to separate the core
2.0 package from the informative materials.
Almost done.
ACTION: SG to think through an example business rule based on
taxcode for later use in showing schematron applications.
Pending.
THIS MEETING
- UN/CEFACT discussion
- Code lists
Jon Bosak
Chair, OASIS UBL TC
---------------------------------------------------------------------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
---------------------------------------------------------------------
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:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]