Re: [ubl-hisc] HISC Teleconference 2005-03-01/02

[Micah Dubinko <micah@dubinko.info>]

Attached is a slightly more updated version. This is about as far as it 
goes without connecting the other thread; writing the XSLT/Python or 
whatever to start generating the spec for each UBL document type.

Thanks, -m

G. Ken Holman wrote:

> Our call this week is Tuesday evening 20:30EST 1 March 2005 in North 
> America, 01:30UTC Wednesday 2 March, morning of 2 March in Asia.
>
> Please review my minutes from last week:
>   http://lists.oasis-open.org/archives/ubl-hisc/200502/msg00017.html
>
> And please comment on Micah's work and my work if you have the time 
> before tomorrow's meeting.  Our posts are in the archive.
>
> I'm particularly interested in implementers being involved so that we 
> can assess the work we are doing to ensure that the specifications we 
> write are implementable.
>
> Please use our usual committee number:
>
>     #############################################
>     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
>     #############################################
>
> "See" you there!
>
> ....................... Ken
>
> At 2005-02-22 20:51 -0500, G. Ken Holman wrote:
>
>> In attendance were only Micah and Ken.
>>
>> We discussed the XPath files posted at:
>>
>>   http://lists.oasis-open.org/archives/ubl-hisc/200501/msg00010.html
>>
>> ... and the use of them posted earlier today at:
>>
>>   http://lists.oasis-open.org/archives/ubl-hisc/200502/msg00015.html
>>
>> Ken reiterated his plan to add cardinality to the XPath expressions.
>>
>> Micah asked about modularization and Ken cited how that was not taken 
>> advantage of in the output specifications as each specification was 
>> produced in a monolithic fashion.  Implementations can be modular, 
>> but sometimes specifications are more easily understood when 
>> monolithic.  No feedback either way was received regarding the 
>> formatting specifications to know if there were any drawbacks to this 
>> approach or not.
>>
>> All seemed well in hand and the meeting ended after only 12 minutes.
>>
>> ..................... Ken
>
>
>
> -- 
> 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/o/
> Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
> Male Breast Cancer Awareness  http://www.CraneSoftwrights.com/o/bc
> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal
>


-- 
  Available for consulting. XForms, web forms, information overload.
  Micah Dubinko                           mailto:micah@dubinko.info
  Brain Attic, L.L.C.                        http://brainattic.info
  Yahoo IM: mdubinko
  Learn XForms today: http://xformsinstitute.com

-- Input Formatting Specifications for UBL document types
---------------------------------------------------------

    Status: Early Draft

    Feedback: to ubl-hisc@lists.oasis-open.org

    Abstract: Everything a form author needs to know to become productive with
    UBL.

-- Glossary
-----------

  The following terms are used in this document.

  SBS -

  W3C -

  XForms -

-- Introduction
---------------

  Forms and XML have much in common--in both cases the technology represents a
  structured exchange of data, as opposed to a "blank page" philosophy of
  interaction. UBL in particular is an application of XML used to represent
  strutured business documents. Some work has been done as modeling this with
  contract semantics, as in
  http://lists.oasis-open.org/archives/legalxml-econtracts/200403/msg00004.html

  Within each document type, UBL defines a large number of XML elements and
  attributes; generally more than any single document will use. For this reason
  part of the job of writing forms against UBL is choosing the proper subset to
  map to form controls. One subset that is gaining traction is the "Small
  Business Subset" (once known as UBL Lite).

-- Input Formatting Specifications
----------------------------------

  This collection contains examples of formatting specifications that can be
  followed to create instances of Universal Business Language (UBL) document
  types as XML. Presentational semantics have not been formalized in this
  version of the UBL schema library, and they may never be formalized due to
  differing international requirements and conventions for the presentation of
  information found in business documents.

  These specifications must not be considered as reference implementations of
  UBL or as normative components of the UBL specification; they are merely
  examples from one of what will probably be many available UBL form libraries
  and transformation products and technologies.

  These specifications follow a guiding principle of UBL under Tool Use and
  Support: "The design of UBL will not make any assumptions about sophisticated
  tools for creation, management, storage, or presentation being available. The
  lowest common denominator for tools is incredibly low (for example, Notepad)
  and the variety of tools used is staggering. We do not see this situation
  changing in the near term."

-- Documentation Conventions
----------------------------

  For each data item in the Small Business Subset, these input specifications
  will list the following pieces of information:

  * The "data collection intent" for this item, without giving specific guidance
  (like "this is a radio button"). Technology-neutral terminology is taken from
  the W3C XForms specification.

  * The data storage location within the UBL XML, specified as XPath.

  * Whether the data item may store a computed value, and if so, the sources and
  expression (again in XPath) used.

  Additionally, for the overall form, the following information will be listed:

  * Overall navigation order, specified as a single bidirectional
  thread.

  For output formatting specifications, you might want to compare notes with
  http://docs.oasis-open.org/ubl/cd-UBL-1.0/fs/


-- Production Notes
-------------------

  This document originated as a plain-text Unicode file, using minimal
  structure. From there, it gets transformed into XML, XHTML, and other formats.
  The XPath details of elements in the SBS were extracted from XML files
  provided in that package.



  [ Each UBL document type will have a separate document, which will have the
  following sections: ]

-- Form-Level Considerations
----------------------------

  TODO:
    Navigation order, as a list,


-- Data item-level Considerations
---------------------------------

  Reference: XPath for each data item:
  http://lists.oasis-open.org/archives/ubl-hisc/200501/msg00009.html

  TODO:
    For each data item:
      * list XPath, data collection intent, and anything else


-- Eventually, a link to a concrete XForms implementation
---------------------------------------------------------

  TODO: