OASIS Vocabulary for XML Standards and Technologies TC

 

Minutes of Meeting 14 March 2002
Updated: 15 March 2002, H. Holger Rath


>>> Participants >>> Agenda >>> Approval of Minutes of Last Meeting >>> Review of Actions Items
>>> Content >>> Decisions >>> Action Items >>> Future Dates

1. Participants

Anthony B. Coates (called in)
Patrick Durusau
Eric Freese
Lars Marius Garshol
James D. Mason
Motomu Naito
Mary Y. Nishikawa (guest)
Peter Pappamikail (called in)
Steve Pepper
H. Holger Rath
Michelle Raymond (guest)
Suellen Stringer-Hye (guest)
Scott Tsao
Bernard Vatant


2. Agenda

  1. Welcome by chair
  2. Roll call of participants. Who wants to apply for TC membership?
  3. Approval of agenda
  4. Review of OASIS TC process, IPR policy
  5. Review of TC charter
  6. Vote on any standing rules for the TC
    1. Whether to allow OASIS members who are not TC members to subscribe to the TC mail list (default is no, but the TC should have a reason for not allowing other OASIS members to subscribe).
    2. Whether to allow voting by email. The default is that voting may only take place in a TC meeting, either face to face or via telcon.
    3. Whether to restrict all email communication to the public mailing list.
  7. Selection/volunteers for the following; most of these are the chair's responsibilities but can be delegated.
    1. Vice-chair
    2. Editor
    3. Secretary
    4. Webmaster
    5. Liaisons with other applicable standards groups or OASIS TCs
  8. Discussion of deliverables
    1. Requirements document stating the scope of the vocabulary (new)
      1. What is the purpose/ use of the vocabulary?
      2. Only schema PSs (classes)? Or both schema PSs and instance PSs? XML as PS?
      3. First proposal: standard creator (organization, std body, std editor), standard, std implementor, std application, std user
      4. Should we cover time issues, evolution of stds/ specs (versions, editions, stages)?
      5. Should we use Dublin Core for document (std/ spec) metadata?
    2. Draft vocabulary
    3. Core vocabulary
    4. Example topic map in XTM
    5. Recommendations for the definition of further Published Subjects
  9. Discussion of requirements
  10. Set meeting schedule, ask for volunteers for hosting meeting

3. Approval of Minutes of Last Meeting

Not applicable


4. Review of Actions Items

Not applicable


5. Content

  1. Welcome by chair

    Chair welcomed all attendees.

  2. Roll call of participants. Who wants to apply for TC membership?

    Mary Nishikawa will apply for membership.

  3. Approval of agenda

    Agenda was approved.

  4. Review of OASIS TC process, IPR policy

    Chair pointed attendees to the OASIS web site to check TC and IPR policy.

  5. Review of TC charter

    Charter was extended in a way that also PS for topics (instances of classes) will be defined and some topic examples were added. A requirements specification was added to the list of deliverables.

  6. Vote on any standing rules for the TC
    1. Whether to allow OASIS members who are not TC members to subscribe to the TC mail list (default is no, but the TC should have a reason for not allowing other OASIS members to subscribe).

      Private TC mailing list will not be opened up for OASIS members.

    2. Whether to allow voting by email. The default is that voting may only take place in a TC meeting, either face to face or via telcon.

      Voting will be done during meetings and via email.

    3. Whether to restrict all email communication to the public mailing list.

      All technical discussion will be performed in public TC mailing list. Only voting, phone numbers for concalls etc. will be performed on private TC mailing list.

  7. Selection/volunteers for the following; most of these are the chair's responsibilities but can be delegated.
    1. Vice-chair, editor, webmaster

      Webmaster will be done by chair. Vice-chair will be appointed when necessary. Editors for deliverables will be appointed later.

    2. Secretary

      PatrickDurusauvolunteeredtoactasTCsecretary.Thechairandthe members appreciate this.

    3. Liaisons with other applicable standards groups or OASIS TCs

      TC will establish liaisons with:

      • OASIS Standards Registry committee (resp.: Bernard Vatant)
      • W3C Unified Glossary & Dictionary project (resp.: provisionary Scott Tsao)
      • OASIS PubSubj TC (resp.: Steve Pepper)
      • Liaisons to ISO JTC1 SC1 and NewsML were considered by rejected.
  8. Discussion of deliverables

    Requirements specification and use cases will have large impact on list of PSs. We will use the XML Cover Pages as a playground.

  9. Discussion (brainstorming) of requirements

    Several issues for the requirements specification were identified during a brainstorming session. Summarized these were: identifiy use cases and derive detailed requirements from them, list domains to be covered, show applicability of vocabulary for other notations besides XTM, identify USPs for vocabulary (e.g., merging examples, use case to be marketed), follow a practical approach by using the XML Cover Pages as playground/ testbed, vocabulary should be somehow organized and not only a flat list.

XMLvoc TC expresses its appreciation to the Boeing company for hosting the meeting.


6. Decisions

  1. All technical communication in public TC mailing list.
  2. Voting in meetings and by email.
  3. Using XML Cover Pages as playground.
  4. Domain name for PSIs: http://psi.xml.org/. Domain for testing: http://psi.xml.org/test/%CLASS%/%INSTANCE% (= URI template).

7. Action Items

No. Action Who Deadline State
1 Scan XMLCover Pages or other XML info sites to harvest PSIs all 15 Apr 2002 o
2 Write outline of requirements spec. H. Holger Rath 15 Apr 2002 o
3 Contact OASIS to establish and get access to psi.xml.org H. Holger Rath 15 Apr 2002 o
 
Legend for state of action items:
o - still open
c - closed
x - not necessary any more

8. Future Dates

  • Tue. 16 Apr 2002, 1500-1700 UTC, conference call
  • Fri. 24 May 2002, f2f meeting, Barcelona in conjunction with XML Europe conference, exact time and location to be announced (will start around noon local time)