March 2006 - cddlm-wg - lists.ogf.org

RE: [cddlm] Our Portal EPR is available!
by Milojicic, Dejan S (HP Labs) 20 Apr '06

20 Apr '06

Congratulations! Dejan. > -----Original Message----- > From: owner-cddlm-wg(a)ggf.org [mailto:owner-cddlm-wg@ggf.org] > On Behalf Of Flávio Roberto Santos / OurGrid Project > Sent: Tuesday, March 28, 2006 5:32 AM > To: cddlm-wg(a)ggf.org > Subject: [cddlm] Our Portal EPR is available! > > Hi people, > > Our Portal EPR is available for testing at > http://cddlm.lsd.ufcg.edu.br:8080/muse/services/Portal > > -- > > Flavio Roberto Santos > Undergraduate student at Universidade Federal de Campina > Grande OurGrid Team Member - www.ourgrid.org My webpage - > http://www.ourgrid.org/~flavio > > -- > > "As far as the laws of mathematics refer to reality, they are > not certain, and as far as they are certain, they do not > refer to reality." > -- Albert Einstein > >

4 4

CDL Tests
by Guilherme Germoglio 10 Apr '06

10 Apr '06

Hello, Our test results regarding the cdl parser can be viewed in: http://lsd.ufcg.edu.br/~guiga/cddlm/test_results/index.html >From these tests we have changed test cddlm-cdl-2005-09-0005, from import_namespace set because its resolution expected is not correct. The expected must be the following: <cdl:system xmlns:test1="http://cddlm.org/test1.cdl" xmlns:t2="http://cddlm.org/test2.cdl"> <MyServer> <hostname>www.cddlm.org</hostname> <port>80</port> </MyServer> </cdl:system> As hostname property was redefined to www.cddlm.org in MyServer, which extends test1:WebServer, this property cannot be the same of test1:WebServer (data/hostname). As you can see in the results, 2 required tests remained failing: cddlm-cdl-2005-02-0021 and cddlm-cdl-06-0001 They regard the resolution of references to lazy properties. We think the tests are not according to the specification, that says in sections 7.3.3and 7.5.2, respectively: "A value reference at *n* referring to *n'* is resolvable if and only if: (...) - The node *n'* and its descendants do not have any @cdl:ref and @cdl:lazy attribute. Otherwise, the resolution is deferred until these @cdl:ref and @cdl:lazy attributes are resolved." "A reference to an property with a @cdl:lazy attribute MUST NOT be resolved before the @cdl:lazy attribute is resolved." What does the specification mean by "be resolved"? When it states that the reference MUST NOT be resolved, does it mean that the reference must remain unchanged? If so, the tests must be changed. If not, what is the expected behavior? Also, there were three non-required tests from the suite that are not included in these results. Guilherme

4 4

Component Model test plan update
by Stuart Schaefer 31 Mar '06

31 Mar '06

Enclosed is the updated component model test plan document. It contains numerous CDL files for the tests. I am uploading all of these documents and files to SourceForge. I am only attaching the test plan document with the CDL files in the Appendix. Please review and comment. Thanks, Stuart Stuart Schaefer CTO sschaefer(a)softricity.com Softricity, Inc. 27 Melcher Street Boston, MA 02210 ph 617.695.0336 x112 fx 617.338.7769 www.softricity.com - Virtually, Anything Is Possible(tm) The Softricity Desktop(tm) enables applications to be as instantly available and easy to use as electricity "All problems in computer science can be solved by another level of indirection". -- Butler Lampson

1 0

Notes from the CDDLM meeting, Wed March 29th
by Milojicic, Dejan S (HP Labs) 29 Mar '06

29 Mar '06

Attendees: Ayla, Flavio, Guilherme, Satish (for Jun's team in NEC), Dejan, Jun, and Stuart. Notes taker Dejan Milojicic. > 1. Update on testing interoperability UFCG put up their endpoint (Congratulations Ayla, Flavio, and Guilherme!), they will try to have it up all the time, occasionally, they will take it down to put up the newer version. Others, please comments. Satish already tried to access it and he was not able establish the connection, "Connection Timeout" was the error. UFCG will check if there are any issues with firewall. Softricity: finalizing the component model test plan, testing components themselves. Updating the test doc and will check in the code for the three components. He will call out all the CDL for the exact tests to test component models as well as for three. Stuart also plans t put an EPR, the time frame is a week or a week and a half, end of the next week. Also hard to put things outside of the firewall. NEC: in the process of exposing EPR, taking a little bit of time since they already submitted a request to open up the port from NEC. Princeton guys are reviewing request and evaluating the against the NEC policy. Hopefully they will have it by the end of the next week. They should have something by the end of the next week. For the CDL testing, Steve and Jun have an agreement on some clarifying issues with the namespace and Jun will adjust the test case for that. HP: Steve is out, so no update on HP today. (wrt namespaces that Jun is changing, which option) UFCG has made an implementation according to specification. They can make changes as long as they know which option. It would be good to know when Jun will change it. Jun will fix this case on import so that it is applied only to a couple of element. Jun will do this by > 2. OGSA and CDDLM Jun provided the presentation describing CDL implementation for BLAST. Neither Jun nor Dejan will be able to attend the OGSA meeting today. Next week is F2F. Jun will attend and Dejan. > 3. Planning GGF17 in Tokyo It looks like only Jun will attend. > 4. Various A side announcement: Component model has been officially made a public document: GFD 65. Congratulations to Stuart. Other documents are in the funnel. Hopefully Actions by end of next week we may have two other endpoints by NEC and Softricity.

2 1

[ogsa-wg] Proposed agenda for March 29th call
by Hiro Kishimoto 29 Mar '06

29 Mar '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on March 29th. Wednesday from 4pm to 6pm (CST). Dial-in numbers for Wednesday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0329 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (if available) Agenda bashing 2) April F2F meeting update (10 min) Revised meeting agenda is on GridForge: https://forge.gridforum.org/projects/ogsa-wg/document/2006Apr-OGSA-F2F-agen… 3) Security Architecture discussion (30 min) Scope, goal, and process discussion. 4) Information model discussion (30 min) Ellen will send out revised container info model (CIM profile) draft for review. 5) Joint CDDLM discussion (30 min) we will review Jun's CDL example document for BLAST job. Jun: Please send out CDL example document before the call. https://forge.gridforum.org/projects/ogsa-wg/document/minutes-2006-03-15/en… 6) Wrap up AOB <NEXT CALL> April 3 (Mon): NO call April 4-7: F2F meeting in San Francisco Bay Area Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ -- Hiro Kishimoto

2 1

CDL for BLAST
by Jun Tatemura 29 Mar '06

29 Mar '06

Please find the attached slides on CDL for BLAST. I will attend our 6am PST call but will not be able to attend the CDDLM/OGSA call today. Thanks, Jun

1 0

Reminder, CDDLM meeting tomorrow
by Milojicic, Dejan S (HP Labs) 29 Mar '06

29 Mar '06

Hi, There is regular CDDLM meeting tomorrow at 6am. We will use our usual numbers: +1 866-639-4732 (toll free while in US) Code 2362906 (followed by a '#' sign) +1 574-948-0379 (toll & international) Agenda: 1. Update on testing interoperability 2. OGSA and CDDLM 3. planning GGF17 in Tokyo 4. various Thanks, Dejan.

1 0

RE: [cddlm] deploy API revisions
by Milojicic, Dejan S (HP Labs) 28 Mar '06

28 Mar '06

Thanks Steve, I will submit it as is (others, please note that PDF does not correspond to the Word document, read the Word document instead). Hiro, I hope that the changes are fine with you and that it is ok that I submit it. Thanks, Dejan. > -----Original Message----- > From: owner-cddlm-wg(a)ggf.org [mailto:owner-cddlm-wg@ggf.org] > On Behalf Of Steve Loughran > Sent: Monday, March 27, 2006 5:24 AM > Cc: cddlm-wg(a)ggf.org > Subject: Re: [cddlm] deploy API revisions > > > This is the updated document. As usual, the CVS image of this > is the normative copy of the specification; what you are > seeing here is are downstream artifacts of that gold image. > > I've made less changes than hiro suggested, not because I > dont agree with them, but because I dont think the changes > should go through except in co-ordination with the other > specifications. If we can do this, then yes, I am in favour > of the changes. > > A1, A2. Yes, there is duplication in the introductory commentary. > However, the team agreed to put a consistent preamble across > all the standards. I do not want to change mine to be > inconsistent, unless we change all simulataneously. > Accordingly, I have not applied any changes to that part of > the document. > > A2: > Looking at the engineering costs of this I'm more reluctant > to make an immediate change. I'd have to change the schema > information across all docs including test documents, and it > will be inconsistency across the different specs. We can do > it, but it will require team-wide coordination. > > An extra complexity is that GFD.58 doesnt define where other > URIs should go, for example, MUWS capabilities. I have picked > on > http://www.gridforum.org/cddlm/deployapi/2005/02/capabilities/ > portal for one of these. Similarly, Appendix B defines two > > What I have done is declared in section 4.4.3.3 that all > extra deployment options that begin with > http://ggf.org/schemas/cddlm are reserved for the cddlm wg. > > > A3. Declared which chapters are normative vs informative. > > A5:. removed "Compliant" near OGSA. > > A6: marked the XSD as copyright 2004-2006. It didnt exist until 2004. > > > Again, these are all minor changes. They make no changes to > the semantics of any part of the specification. > > Dejan, Stuart, if you are happy with these, then post them to > the site. > I am now going to be absent for eight days, skiing in the > Alps. No email, no voicemail. > > -steve > > -Steve >

2 1

Our Portal EPR is available!
by Flávio Roberto Santos / OurGrid Project 28 Mar '06

28 Mar '06

Hi people, Our Portal EPR is available for testing at http://cddlm.lsd.ufcg.edu.br:8080/muse/services/Portal -- Flavio Roberto Santos Undergraduate student at Universidade Federal de Campina Grande OurGrid Team Member - www.ourgrid.org My webpage - http://www.ourgrid.org/~flavio -- "As far as the laws of mathematics refer to reality, they are not certain, and as far as they are certain, they do not refer to reality." -- Albert Einstein

1 0

what to do about <import namespace>
by Steve Loughran 27 Mar '06

27 Mar '06

I just had the phone conf thing turned on, but nobody dialled in, so we didnt get an opportunity to talk about <import namespace>. That's OK. it has given me more time to deal with SOAP problems. For the curious, I am abandoning Axis2 because all it brings to the table is pain. They've done some fancy new classloader stuff, which, coupled with the preponderance of the code to catch and inadequately log exceptions, means you can spend forever debugging it. Instead we will be using the long-promised Alpine SOAP stack :) I'm still trying to have something ready by the end of the week, even if it is just the portal. One problem will be the AddFile() operation, because implementing attachments will be tricky. Returning to the other troublespot: what are we to do about <import namespace>? This is what I have filed in the CDL issue tracker, under https://forge.gridforum.org/tracker/?aid=1782 Need to clarify the semantics of <import namespace> =================================== The CDL specification, on the topic of <import namespace>, doesnt cover what to do if stuff is already is in a namespace, and implies that all attributes and elements in the list also get pulled in. As a consequence, when something gets imported into a namespace, everything inside it gets moved into the new namespace, so is no longer accessible to components that are trying to resolve it using the local name. To show this as an example, (from /cdl/valid/set_09_import_namespace/cddlm-cdl-2005-09-0001.xml ) At http://cddlm.org/test1.cdl there is a file with no namespace <cdl:cdl> <cdl:configuration> <WebServer> <hostname>localhost</hostname> <port>80</port> </WebServer> </cdl:configuration> </cdl:cdl> this is imported into a new namespace <cdl:cdl xmlns:test1="http://cddlm.org/test1.cdl"> <cdl:import location="http://cddlm.org/test1.cdl" namespace="http://cddlm.org/test1.cdl" /> <cdl:system> <MyServer cdl:extends="test1:WebServer"> <hostname>www.cddlm.org</hostname> </MyServer> </cdl:system> </cdl:cdl> Now, what do we end up with? Is it (1) <cdl:system xmlns:test1="http://cddlm.org/test1.cdl"> <MyServer> <hostname>www.cddlm.org</hostname> <port>80</port> </MyServer> </cdl:system> Or is it (2) <cdl:system xmlns:test1="http://cddlm.org/test1.cdl"> <MyServer> <hostname>www.cddlm.org</hostname> <test1:hostname>www.cddlm.org</test1:hostname> <test1:port>80</test1:port> </MyServer> </cdl:system> (2) is the literal interpretation of the specification, and it is wrong, because nested elements are now in the wrong namespace for their implementation classes to be able to read. Solutions -pull the whole namespace stuff out, tell people to use their own namespaces for scoping. and stick to <import> -restrict namespace scope to the qnames of the toplevel elements. Leave stuff already in namespaces alone. What have other projects done? I looked at how Ant's ability to <typedef> a task or type into a namespace. It only acts on the supplied tasks and types in the local namespace, and maps all attributes into the same xmlns. For nested elements it does something devious and allows either namespaced or local declarations in <taskdef name="myecho" uri="antlib://ex.org.package" /> this would make the following things identical, assuming xmlns:m="antlib://ex.org.package" <m:echo level="info" > <message>text here</message> </m:echo> and <m:echo m:level="info"> <m:message>text here</m:message> </m:echo> That is: stuff inside the new task is both inside the new namespace, and in the ##local namespace. Ant pulls this off because it does its O/X mapping from the outside, going from XML elements to java methods, and can do loose matching of QNames to methods. We dont have that option in CDL, so need a better solution ---------------------- As an aside, there are a currently 6 outstanding defects in the tracker: https://forge.gridforum.org/tracker/?atid=734&group_id=130&func=browse I believe this is the official way to file issues against a spec, but if it would be better for me to file pointers to the items in a different tracker as part of the public review, I can do that.

3 4