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


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-architecture message

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

Subject: RE: TA 0.9 Comments

Hi All,

Very Nice!  In my review, I find the document to be easily understood, and
emotionally neutral.  I approve the document, though I do offer the
following comments:

1) Line 355, editorial - delete "the Semantics of"

2) line 738, Use of "attributes" may be confused with XML use of
"ATTRIBUTE".  Perhaps 
   "properties" might be a better word to use in this document.

3) Lines 154-162, and lines 201-291

This may be just an observation, but - 

What sounds so easy (and automatic) in 154-162 looks and sounds so much more
difficult in 201-294.  

I don't think ebXML will significantly bring the SME's on board in a direct
way.  But then I never thought it would, any more than I ever thought EDI
would.  The key to eventual success is in hiding the complexity from the
SME's.  I believe the ebXML architecture, through the standardized building
blocks of that architecture, will facilitate the integration and hiding of
these complexities within higher level application packages.  We did at one
time think that EDI would facilitate this, but we were shortsighted.  I
don't know whether we are beign shortsighted again, but I feel there is
cause for optimism on this happening with ebXML.

In 201-294, the "Company A" 'does this, does that' verbage reads to me as
"some individual(s) in Company A must understand and execute a rather
complicated set of manual (and perhaps semi-automated) steps to reach the
point where automation takes over.  And of course, until higher level
off-the-shelf application packages do this job, these initialization steps
will require 'hands on' knowledge, and so will not penetrate much further
than traditional EDI.  

In 151-152, the need to hide this stuff in off-the-shelf software is
expressed.  Maybe a few words at the end of 201-294 to affirm that this
stuff can be automated and so be largely hidden from the end SME user would
be helpful and reassuring.


-----Original Message-----
From: duane [mailto:duane@xmlglobal.com]
Sent: Sunday, October 29, 2000 1:32 AM
To: agrangard@nycall.com
Cc: ebxml-architecture@lists.ebxml.org; 'ebXML Coordination'
Subject: Re: TA agenda Tokyo

Anders, Murray, Nagwa, Brian et al:

I would like to propose that on Tuesday we hold a special session with a
split group from TA and QRT.   We should split the TA team into two
groups - one to work with QRT on addressing their specific comments on
the TA spec and the second team to start categorizing the general
comments we receive from the other teams.

Murray Maloney from QRT has already agreed to sit with us for a while
and I would also hope that Tim, Nagwa and Jon also attend or have at
least one other QRT member attend with a list of currently outstanding

I think that by working together in Tokyo for one full day,  we can
fully address the issues facing the TA spec.


Duane Nickull

"agrangard@nycall.com" wrote:
> Below you will find my proposed TechArch agenda for the Tokyo meeting. As
> you will see I have tried to keep it as clean as possible to allow core
> to be done. If you want to add or change anything, please do so before
> Thursday next week.
> Have a good trip and see you in Tokyo.
> Anders
> Draft Agenda
> ebXML Technical Architecture Project Team
> Tokyo, 6 - 10 November 2000
> Monday, 6 November
> 09:00 - 10:00 ebXML Technical Orientation
> 10:00 - 11:00 Open Plenary
> 11:00 - 12:00 Opening of the TA meeting, practical details, new sub-group:
> Security
> 12:00 - 13:00 Lunch
> 13:00 - 17:30 Review received comments
> Tuesday, 7 November
> 08:00 - 08:15 Report from yesterdays Steering Committee
> 08:15 - 12:00 Review received comments (subgroups)
> 12:00 - 13:00 Lunch & Learn (Presentation on Conformance)
> 13:00 - 16:00 Review received comments (subgroups)
> 16:00 - 17:30 Review received comments
> 17:30 - 18:00 Wrap-up, input to steering committee
> Wednesday, 8 November
> 08:00 - 08:15 Report from yesterdays Steering Committee
> 08:15- 12:00 Review received comments (subgroups), Joint sessions with
> PTs, as appropriate
> 12:00 - 13:00 Lunch & Learn
> 16:00 - 17:30 Review received comments
> 17:30 - 18:00 Wrap-up, input to steering committee
> Thursday, 9 November
> 08:00 - 08:15 Report from yesterdays Steering Committee
> 08:15 - 12:00 Finalise Tech Arch 1.0 (subgroups), review of Hong Kong
> presentation (Krishna Sankar)
> 12:00 - 13:00 Lunch & Learn
> 13:00 - 16:30 Finalise Tech Arch 1.0
> 16:30 - 17:00 Wrap-up, input to steering committee
> Friday, 10 November
> 08:00 - 12:00 Prepare closing plenary presentation and future work
> 12:00 - 13:00 Lunch
> 13:00 - 15:00 ebXML Closing Plenary

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC