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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-hisc message

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


Subject: some notes on shell input, was [ubl-hisc] Minutes for 2006-02-21 HISC teleconferences




-----Oprindelig meddelelse-----
Fra: G. Ken Holman [mailto:gkholman@CraneSoftwrights.com]
Sendt: 23. februar 2006 21:01
Til: Bryan Rasmussen
Emne: Re: SV: [ubl-hisc] Minutes for 2006-02-21 HISC teleconferences


This is great, Bryan ... just what I was hoping to see:  the things 
implementers need without having to be a UBL TC member and without 
having to delve into the humongous UBL to try and find for themselves.

Another thing I didn't think about before as an advantage of having 
an input specification:  different vendors will implement their 
solutions the same way, so end users don't see vagaries across 
different implementations.

Once you get posting privileges, please take the time to list the below.

Thanks again, Bryan.

. . . . . . . . . . . . . . Ken

At 2006-02-23 15:47 +0100, you wrote:
>I think in the context of what should be done for people implementing forms
>and such, maybe something like the following:
>
>1. Definition of some pseudocode handling of input types, and then matching
>of input type to the specific pseudocode - as an example a Governmental
>agency here at one point had some forms that were accepting user input for
>different elements, these elements were of type xsd:token. The form fields
>did not perform any string normalization before creating elements, thus at
>times user input errors could lead to invalid documents.
>
>2. Referencing of elements that take codelists to codelist, pseudocode?
>
>3. One of the things I provided for the online validator for our efaktura
>implementation was a stylesheet for doing calculation and comparison.
>
>I suppose the input document should identify calculation algorithms for each
>format. This might be something that we could ask someone like Stephen Green
>to write down, if it isn't written down somewhere else already.
>
>Some other stuff I'm sure. Will get to that in the following days.


--
Upcoming XSLT/XSL-FO hands-on courses: Washington,DC 2006-03-13/17
World-wide on-site corporate, govt. & user group XML/XSL training.
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/m/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/m/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal



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