[ogsa-naming-wg] RNS 1.1 spec
Michael Behrens
michael.behrens at r2ad.com
Tue Dec 29 21:04:23 CST 2009
Looks good!
Two nit-noids that the editor will probably fix in the v.9 spec:
wellknown should be two words or hyphenated on page 4 and in the
following paragraph, " indiacting" should be "indicating". Also, be sure
to update the table of contents to get the page numbers updated, etc.
Osamu Tatebe wrote:
> Hi all,
>
> Attached are modified documents of RNS spec 1.1 and OGSA
> rendering document. I double checked the inconsistency
> between two documents. I hope there is no major error
> in these documents.
>
> I will submit them to the editor tomorrow. If you find
> any typo or even small errors, please let us know now or
> during the public comment period.
>
> Mark, would you submit ws-iterator document to the editor?
>
> Thanks,
> Osamu
>
> On Tue, 29 Dec 2009 02:50:41 +0900
> Osamu Tatebe <tatebe at cs.tsukuba.ac.jp> wrote:
>
>
>> Hi,
>>
>> Thanks for pointing out the inconsistency. I fixed about
>> response messages in RNS 1.1. Lookup operation now returns
>> a list of response-entries not a list of entries. Mark,
>> would you check this?
>>
>> Also, I updated Faults and Failures section and fixed several
>> typos (not included in change history, sorry). I hope these
>> include all required modifications we discuss recently.
>>
>> Regarding the inconsistency between the spec and the rendering
>> document, I will check later.
>>
>> Thanks,
>> Osamu
>>
>> On Mon, 28 Dec 2009 14:05:15 +0900
>> Hideo Matsuda <matsuda at ist.osaka-u.ac.jp> wrote:
>>
>>
>>> Dear Tatebe-san and Mark,
>>>
>>> Thank you very much for your editing the final version of
>>> RNS 1.1 document.
>>>
>>> I would appreciate it if you could check the consistency
>>> between RNS 1.1 spec and rendering documents.
>>>
>>> For example, RNS 1.1 spec has "response-entry" element
>>> in the addResponse message in p.8. But RNS 1.1 rendering
>>> seems not to have "response-entry" element.
>>>
>>> Another minor comment is that add message has "rns:entryNameType"
>>> in p.7 in RNS 1.1 spec. But it seems to be "rns:EntryNameType".
>>>
>>> Best regards,
>>>
>>> Hideo Matsuda
>>>
>>>
>>>> Hi all,
>>>>
>>>> Attached is a final version of RNS 1.1 document I will submit to
>>>> the editor on 30 December, 2009. If there is still something to
>>>> edit, please let me know.
>>>>
>>>> Also, this RNS 1.1 spec depends on WS-Iterator specs. Mark,
>>>> would you submit them to the editor?
>>>>
>>>> Thanks,
>>>> Osamu
>>>>
>>>> On Mon, 9 Nov 2009 08:40:21 -0500
>>>> Mark Morgan <mmm2a at virginia.edu> wrote:
>>>>
>>>>
>>>>> Please find attached the revised versions of the documents as
>>>>> discussed on the telecon last week. I fixed the errors that Hideo
>>>>> pointed out and fixed a couple of typos that came up while trying to
>>>>> run the xsd and wsdl through out tooling.
>>>>>
>>>>> Osamu, you never sent me the list of authors/acknowledgements to add
>>>>> so I'll leave it to you to add those to the document.
>>>>>
>>>>> -Mark
>>>>>
>>>>> On Nov 8, 2009, at 1:51 AM, Osamu Tatebe wrote:
>>>>>
>>>>>
>>>>>> Thanks for pointing out errors. We have a teleconference
>>>>>> as scheduled, and discussed about the document. After some
>>>>>> errors in text and in schema are corrected, Mark will post
>>>>>> it to the ML soon.
>>>>>>
>>>>>> Thanks,
>>>>>> Osamu
>>>>>>
>>>>>> On Wed, 04 Nov 2009 22:24:56 +0900
>>>>>> Hideo Matsuda <matsuda at ist.osaka-u.ac.jp> wrote:
>>>>>>
>>>>>>
>>>>>>> I am very sorry for my late response.
>>>>>>>
>>>>>>> The spec is almost very fine for me.
>>>>>>> But a minor comment is that it is not appropriate that
>>>>>>> in page 17 in "RNS-rendering-v4.doc", the element has
>>>>>>> the name "xxxx Type" such as
>>>>>>> <wsdl:message name="AddRequest">
>>>>>>> <wsdl:part name="AddRequest"
>>>>>>> element="rns:AddRequestType"/>
>>>>>>> </wsdl:message>
>>>>>>> because add request message could be sent as "AddRequestType"
>>>>>>> (not "AddRequest"). If you want to replace it with "AddRequest",
>>>>>>> please remove "Type" from "element=" in page 17.
>>>>>>>
>>>>>>> And also change the definition of the complex port type in page 12:
>>>>>>> <!-- Messages -->
>>>>>>> <xsd:complexType name=”AddRequestType”>
>>>>>>> <xsd:sequence>
>>>>>>> <xsd:element name=”entry” type=”rns:RNSEntryType”
>>>>>>> minOccurs=”1” maxOccurs=”unbounded” nillable=”false”/>
>>>>>>> </xsd:sequence>
>>>>>>> </xsd:complexType>
>>>>>>> <xsd:element name=”AddRequestType” type=”rns:AddRequestType”/>
>>>>>>> ^^^^^^^^^^^^^^^^
>>>>>>> in which 'element name="AddRequestType"' is to be replaced with
>>>>>>> 'element name="AddRequest"' so that the message does not include
>>>>>>> "xxx Type"
>>>>>>> in its element. Again, it is only a minor comment. The document
>>>>>>> itself
>>>>>>> is very fine.
>>>>>>>
>>>>>>> Best regards,
>>>>>>>
>>>>>>> Hideo Matsuda
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> I appreciate your effort to write it up.
>>>>>>>>
>>>>>>>> As discussed in the WG session during the OGF27, we would
>>>>>>>> like to have a conference call in the first week of November
>>>>>>>> to discuss and finalize the RNS document for submission to
>>>>>>>> the editor.
>>>>>>>>
>>>>>>>> I suggest to have a Skype conference call at 10pm in JST
>>>>>>>> (8am in EST, I suppose the daylight saving time ends) on
>>>>>>>> Wednesday, November 4. Everyone who is interested fine? If
>>>>>>>> not, please let us know the convenient time slot. (please
>>>>>>>> consider the Japan timezone JST+0900).
>>>>>>>>
>>>>>>>> I will invite everyone who is interested in the discussion.
>>>>>>>> Let me know your Skype ID.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Osamu
>>>>>>>>
>>>>>>>> From: Mark Morgan <mmm2a at virginia.edu>
>>>>>>>> Subject: [GFS-WG] RNS 1.1 v4
>>>>>>>> Date: Wed, 21 Oct 2009 13:27:56 -0400
>>>>>>>>
>>>>>>>>
>>>>>>>>> As agreed last week, please find attached the updated RNS 1.1
>>>>>>>>> specification document and the RNS 1.1 OGSA WSRF BP Rendering
>>>>>>>>> document. Hopefully this adequately represents the changes that we
>>>>>>>>> discussed.
>>>>>>>>>
>>>>>>>>> -Mark
>>>>>>>>>
>>>>>>>> --
>>>>>>>> gfs-wg mailing list
>>>>>>>> gfs-wg at ogf.org
>>>>>>>> http://www.ogf.org/mailman/listinfo/gfs-wg
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> ogsa-naming-wg mailing list
>>>>>>>> ogsa-naming-wg at ogf.org
>>>>>>>> http://www.ogf.org/mailman/listinfo/ogsa-naming-wg
--
Michael Behrens
R2AD, LLC
(571) 594-3008 (cell)
(703) 714-0442 (land)
More information about the ogsa-naming-wg
mailing list