RE: [plcs] Draft PLCS Advisory for DEX Development Outside the PLCS TC

["Mason, Howard (UK)" <howard.mason@baesystems.com>]

A few suggested editorial changes attached.  The wording as originally proposed seems to focus on DEX acceptance, but also mentions capabilities and reference data.

 

Some fundamental issues:

1)  I don't think we are planning to ballot on individual capabilities - these will be maintained and configuration managed in DEXlib.  So what is the acceptance process for externally-developed capabilities?

2)  The same question arrises for reference data.  We are still finalising the guidance on reference data - what is the acceptance process for reference data developed externally?

 

Howard Mason

---

From: Chris Kreiler [mailto:kreilerc@mantech-wva.com]
Sent: 30 December 2005 20:41
To: plcs@lists.oasis-open.org
Subject: [plcs] Draft PLCS Advisory for DEX Development Outside the PLCS TC

*** WARNING ***

This mail has originated outside your organization,
either from an external partner or the Global Internet.
Keep this in mind if you answer this message.

All,

 

One of the Secretariat’s action items from the last PLCS teleconference was to draft an advisory for the OASIS PLCS TC Public side of the website regarding contacting a PLCS TC expert before undertaking development of a data exchange specification.  Attached is my first cut.  I have “volunteered” some technical experts.  Please confirm your desire to be included or removed from the list. 

 

Please make any editorial comments by close of business 9 Jan 06.  I will incorporate the comments and post on OASIS website.

 

Thanks.

 

v/r

 

Chris Kreiler

PLCS Secretariat

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

PLCS Website Advisory.doc