NDR SC portal: http://www.oasis-open.org/committees/ubl/ndrsc/
We will meet by phone on Wednesday, 13 February 2002, at:
8-10am PT (GMT -8)
11am-1pm ET (GMT -5)
5-7pm Eur (GMT +1)
Please use the following dial-in information, which will remain the same
through at least March 27:
Toll-free (from the U.S.) +1 888 232 0361
International access/caller-paid +1 805 240 9673
Participant code 165-412
Agenda:
1. Roll call (till x:05)
See member list at http://www.oasis-open.org/committees/ubl/ndrsc/
2. Acceptance of minutes of previous meetings (till x:06)
6 February 2002 telecon:
http://lists.oasis-open.org/archives/ubl-ndrsc/200202/msg00020.html
3. Adoption of agenda (please send suggestions *before* meeting) (till x:07)
4. Planning for March 11 deadline (till x:15)
- Feb 7-13: Finish tag structure/data dictionary issues and code
lists
- Feb 14-20: Finish elements vs. attributes and Empty Elements
- Feb 21-27: extension and MODNAMVER and Top Level Element Naming
- Feb 28-Mar 6: Qualified vs unqualified and Name/Type Sharing
- Mar 7-9: Final NDR document/position paper edits
5. Action item review (till x:20)
ACTION: Mark to update tag structure position paper.
ACTION: Sue and Maryann to do some use case brainstorming offline.
ACTION: Bill and Mavis to champion the URI/URN issue and determine an
approach.
ACTION: Everyone to critique modnamver UML diagram.
ACTION: Arofan, Tim, Gunter, and Lisa to develop example and code
with LCSC group.
ACTION: Namespace issues need to be raised to library committee for
joint resolution. (Needs owner.)
ACTION: Gunther will finish some modifications to the elements vs.
attributes position paper and will post it by January 31.
ACTION: Arofan to liaise with the CMSC on the issue of code list
extensibility and subsetting.
ACTION: Ask Eduardo to create a proposal for using attributes at the
leaf level.
6. Code lists (till y:15)
Issues:
Identifiers for a whole code list:
==================================
- Requirements:
. Refers unambiguously to one list
. UBL can assign (for internal code lists)
. Others can assign (for external code lists)
. Extension designers can assign without clashing
- Options:
1. URI reference as a "code list namespace name"
2. Ad hoc (e.g., ISO number, UBL descriptive keyword, etc.)
2. Other
Versioning a whole code list:
=============================
- Requirements:
. Need to keep the identifier the same when version changes?
- Options:
1. Put version in identifier
2. Keep identifier the same over time but provide separate
version info in markup
Maintenance of external code lists:
===================================
- Requirements:
. UBL will need "machine-readable" form of these
. Can UBL afford to maintain?
. Are there legal issues around this?
- Options:
1. UBL maintains
2. External groups maintain, through arrangement if necessary
3. No machine-readable form of these
4. Other
Provision of a code in markup:
==============================
- Requirements:
. Ideally can be checked to be a valid code
. Can fully but succinctly document the code's meaning
. Do users ever need the "zz" escape hatch capability?
. Possible codes should be subsettable based on context
. Do codes need to be extensible based on context?
. Possible codes should be extensible by extension designers
. Performance requirements in validation?
. Performance requirements in processing?
- Options:
1. Enumerated list of string values
a. With "zz" option
b. Without "zz" option
2. Unrestricted string
3. String with pattern-matching restrictions
4. One unique UBL element per code
5. String from code list validated at run time
6. Other
Style of code naming:
=====================
- Requirements:
. Ideally should match the prevailing industry code list usage?
. Needs to be compact and concise?
. Needs to help instance readability?
. Needs to provide semantic clarity?
Options:
1. Alphanumeric
2. Numeric
3. Full spelling
4. Combination
5. Ad hoc
6. Other
7. Tag structure (till y:50)
Position paper:
http://www.oasis-open.org/committees/ubl/ndrsc/pos/draft-Crawford-tagstructure-01.doc
- Getting the tag structure decisions documented and bought into
Other issues:
- Oxford English
- Delimiters between portions of a name
- Acronyms, abbreviations, and truncations
- Non-letter characters
- Singular and plural
- Articles, prepositions, etc.
- Recommendation for maintenance of RT list
8. Next steps (till y:59)
9. Adjourn (z:00)
--
Eve Maler +1 781 442 3190
Sun Microsystems XML Technology Center eve.maler @ sun.com