Attendees: Lawrence Mandel, Arthur Ryman, John Kaputin, Graham Turrell

Minutes

1. Open Action Items - Lawrence Mandel 

2006-10-07 - John will update the task list with up-to-date task 
information and links to Jiras. 
2006-11-21 
John: I did some of the work today. I'll try to get this done by our next 
call. 
2006-11-28 
John: I haven't completed this yet. I'm working to get this done today.
2006-12-12
John: I did more work after the last call but haven't quite finished yet.
2006-12-19
John: Done. I closed complete tasks and opened Jiras for others. There are 
4 left that I need to investigate but I've updated the status.
Closed.


2006-11-21 - Everyone should verify and close any Jiras they've opened 
that have been resolved but not closed. 
2006-11-28 
Arthur: I did this. I had to reopen a couple. 
John: I didn't have a chance to do this but I think mine are up to date. 
Lawrence: I didn't have a chance to do this. I'll try to check this week.
2006-12-12
John: There are 14 in the list.
Note: We went through the list on the call, closed those that could be 
closed and requested that the reporters review and close the others.
John: I'll add comments to prompt the rest of the reporters to close the 
Jiras they've reported.
2006-12-19
John: I've been through the list. There are only 6 left. We're just 
waiting on Chathura and Jeremy to close out these last 6.


2006-12-12 - John will propose Jan. 15 as the M7 release date on the 
woden-dev list. 
2006-12-19
John: Done. I sent this out today. I also updated the Woden website with 
this date with a link to the Woden Jiras.
Closed.

2006-12-12 - John will post to the dev list reviewing our status for 
graduation and informing others that we will review this on our next call.
2006-12-19
John: I didn't post to the list but we can discuss on today's call.
Lawrence: Perhaps we should speak with Dims or Paul about what we still 
need to do for graduation and discuss the list on the call.
[action] John and Lawrence will review the requirements for graduating 
from the incubator and post to the dev list.
Closed.


2. Milestone (M7) Status - John Kaputin

John: The date is not set at Jan. 15. I've made some progress today. I've 
got the next three weeks to get through my list.


3.Development Discussion - All 

Arthur: I saw that a Jira was opened today for line/column info.
John: I opened this. I think Lawrence mentioned a strategy to solve this 
issue.
Lawrence: Yes. We can create a Xerces parser that will capture this 
information. We can then expose it using a separate API if we want to keep 
the model API clean.

Lawrence: John, I saw that you posted to the mailing list about putting 
together some Woden use cases.
John: This came from the task list. I think it will be useful post M7.
Arthur: Maybe we can find out more about what Cindy, who has been posting 
to the dev list, is doing with Woden to drive some use cases.

John: I was thinking about an API change. In WSDLReader we take a URI as a 
string and return a description element. I'm thinking it might be better 
to take a java.net.URI to be consistent and to return a description 
component. This came from looking at what Axis2 is doing with Woden.
Arthur: There's a more direct relation between a URI and an element. A 
component model may be a representation of many documents. Do we have a 
concept of a root document when we call toElement?
John: Yes. You get the top level description element in the composite WSDL 
tree.
Lawrence: I don't see a problem with this. I think our goal is to minimize 
the number of toElement or toComponentModel calls.

Arthur: A description element may be nested in another XML document. This 
means the URI passed to Woden may contain a fragment. Do we currently 
handle this case?
John: No. Please open a Jira.
Arthur: We'll need to check that java.net.URI properly handles fragments 
before making the change discussed above.


4. Other Business - All

Next week's status call is cancelled. Happy holidays.


Thanks, 

Lawrence Mandel 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to