[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [wsrp-wsia] Minutes for 28 January 2003 Face-to-Face
Attached are the minutes for the WSRP face-to-face meeting in Palo Alto, CA for 28 January 2003. Steven Smith Director of Information Services and Technology Capitol College 11301 Springfield Road Laurel, MD 20708 voice: (301) 369-2800 x2548 fax: (301) 953-1180 email: ssmith@capitol-college.edu web: http://www.capitol-college.edu
Minutes 28 January 2003 Meeting started 9:18am Pacific Time No attendance taken. Quorum determined by headcount of attendees in meeting room and Charles Wiecha on the phone (24 of 30). **************************************** No objections Change Requests #5 - Edit to remove security aspect & move to Appendix B #7 - Alternative: Editorial change to improve wording #8 #10 #11 #13 - Alternative: Left justify #35 #37 - Rich's new text accepted #49 - Keep Security.AccessDenied #50 - Clarify text #64 - Add portlet URL parameters #65 #66 - Remove first two sentences & re-word third sentence (new first sentence). #69 - Clarify recommendation about cookies and secure vs non-secure. Include reference to RFC #82 #83 #84 - Note that changing a property's value could impact the value of Portlet's properties. #85 - Alternate: Make a required field, both wsrp-url and wsrp-rewriteResource when urltype="Resource" & dropping second sentence. Clarify first sentence. #86 - (see #37) #98 #101 - Leave "system entity" #102 - Check to see if really needed in spec #103 #105 - Alternative: change style to table and make it part of Chapter 4. Just lists the data types (alphabetically) with hyperlinks to the correct sections. State that Chapter 4 is non- normative. #106 - Change systematically throughout the specification - customize => end-user (logically) sourced settings - personalize => system sourced settings #107 - Change throughout spec #108 #109 #110 - Text as amended #111 #112 #116 - Alternative: Remove term from glossary. Add hyperlinks to spec for this and XML. Change "a collection of names to "a name". Make verbs singular. #124 - Recommend first 127 characters of Unicode characterset and warn about not following recommendation could lead to data loss #125 #126 #127 - Add: Add fields in RuntimeContext for namespace prefix and templates (from MarkupParams). **************************************** Keep As Is Issues #119 Change Requests #3 #4 - Change from Other (27 January 2003 minutes) #70 #81 - Drop Security.AccessDenied fault #97 (see Other) #113 - Term deleted in #101 #114 - Term deleted in #101 #115 #104 **************************************** Revisit for Version 2 Change Requests **************************************** Other Change Requests #97 - Mike will contact JSR168 to request they synchronize case with WSRP **************************************** **************************************** Producer Demo by Gil Tayar Discussion about WSDL group meeting on CDATA - No CDATA type in WSDL spec - Use ANY type for CDATA? - XML parser understands CDATA (2.7 - <element><![CDATA[some_data]]></element>) - Have to do custom serializers and deserializers Discussion about WSRP and JSR168 (Change Request #71) - Blocking and Non-Blocking actions - getMarkup, navigationalState, performInteraction, action-urls - JSR168 face-to-face meeting next week Agenda change - move some Thursday items to tomorrow No Objections to making editorial changes to values to match camel case. IBM is in the process to provide IPR (intellectual property rights) statement dealing with WSRP on a reciprocal royalty free licence. WebCollage will write a statement on relevant IPR when they receive IBM's statement. OASIS Specification Process (Summary) <http://www.oasis-open.org/committees/process.shtml#standards_process> 1. Vote in committee on completed specification (2/3 yes and less than 1/4 no) 2. Goes to 30-day public comment 3. Collect comments and meet to decide on changes and vote on modified specification 4. Another 30-day public comments (if committee makes what it thinks are major changes) 5. Have at least 3 separate, independent implementations 6. Submit to OASIS for review and approval for making a standard 7. TC required to review if there are any negative votes from OASIS Bill will send to email references to time limits for the specification process. Next milestones: - Consensus that technical content is what we want (is it ready for public review) - IPR clarified - Successful vote on the spec Committee Schedule Corrected spec will be ready by Wednesday of next week. (Feb 5) Review period for 3 weeks - make change requests (until Feb 26) Meet by phone after review period (Feb 27) Update the spec (March 3) Final review period - 3 weeks (until March 24) Final spec (March 27) Vote on spec (as soon as possible after final spec) Bill Cox moved that we accept the proposed schedule. Seconded by Sasha Aickin. Passes without dissent. Discussion on next face-to-face meeting - 3rd week of May - In Europe (UK or Germany) - Will discuss later Meeting ended 5:20pm (Pacific)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC