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


Help: OASIS Mailing Lists Help | MarkMail Help

asap message

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

Subject: RE: Editorial work - Input/Corrections

Title: RE: Editorial work - Input/Corrections

Please go ahead and make the grammatical/clarity changes.

If you are not sure what to do with a particular issue, make an "Open Issues" section at the end of the document; incolude whatever you know about the issues.  We can also start action items in the forum about these issues, and I will get these on the agenda for future meetings.

Please circulate the improved document to the list.  I will make it a public document from the TC page (which is what we agreed to do in December...)


Keith D Swenson, kswenson@us.fujitsu.com
Fujitsu Software Corporation
1250 E. Arques Avenue, Sunnyvale, CA 94085
(408) 746-6276   mobile: (408) 859-1005

-----Original Message-----
From: Mayilraj Krishnan [mailto:mkrishna@cisco.com]
Sent: Tuesday, April 13, 2004 10:33 AM
To: asap@lists.oasis-open.org; KSwenson@us.fujitsu.com
Subject: Editorial work - Input/Corrections


I took an action item in last month's conference call to go thru the
working draft
and see what are the inputs received so far.

Working Draft Corrections:
(1) Working draft needs minor corrections (found 25 places to be corrected)
All of these are related to grammar, readability and schema related changes.
This includes John's comments on 09/26/2003.
Can I go ahead to edit the document and sent it to you, list..?
Please let me know..

(2) Inputs Received:
        The following comments might be considered for version 1.0 specification.
        (2.1) Do we include WSDL binding in the spec? Better to add appendix.
         Jeffery Ricker  on 11/04/2003.(WSDL Binding)
        (2.2) Instance creation multiple name, subjects, descriptions List
instances multiple priorities
        John Fuller - Implementation Details - 04 Dec 2003
        (2.3) instanceProperties is far different from the working spec (access
users, state lists, activities, modification date, etc)
        history type and events are not defined in the schema
        John Fuller - More notes - 16 Dec 2003
        (2.4)Be sure to review my handling of filter and properties. Perhaps
someday filter will be an xpath expression and properties will
        extend from a common ancestor, but for now I tried to stay close to  what
we had.
        I suppose another issue is whether or not we should add priority as
an  instance property, since we set it and request it.
        (In my easyasap implementation, it's just stored elsewhere.)
        And while we're at it, perhaps make it an element or type of its own  with
some defined range.
        John Fuller - Schema - 26 Feb 2004
        (2.5)StateType schema change
        John Fuller - Discussion on state datatype - 2 Mar 2004

I think we should have more discussions on these items and go further from
Please let me know if I miss any other input


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