[ogsa-naming-wg] Re: [gfs-wg] RNS critique (new revision available)

[Manuel Pereira]

Hello Takuya and all,

> * About QNames, do namespace in XML (and Prefix) for QNames have not
>   to be defined strictly in this RNS document?

This is a very good question.  Since RNS has not yet been established as a 
standard, an official XML namespace has not been defined.  This is 
orthogonal to the specification of the service however.  Once the 
specification becomes a standard, then the appropriate XML namespace and 
WSDL references will be defined.
 
>   Accoding to some examples in this document, namespace in XML for
>   Required Entry Properties (in section 1.2.2.2.1) and Entry itself is
>   "http://rns.ggf.org".
>
>   And accoding to RNS WSDL 1.1, namespace in XML (for Inputs,
>   Responses , Faults and ResourceProperties) is
>   "http://rns.ws.ibm.com".

Actually, all of the examples that use any XML namespace use ?rns.ggf.org? 
since this particular specification draft is being submitted to GGF for 
standardization.  The ?rns.ws.ibm.com? is only found in the WSDL, which is 
an actual working WSDL used to build the reference implementation, which 
is undergoing final development within IBM.  The reality is that both of 
these may change.  The official XML namespace may change once RNS becomes 
a standard, and the WSDL of the reference implementation will eventually 
match the defined standard.
 
> * What is a XML datatype of Entry?
> 
>   According to EPRs and LogicalResolvers and Target (these are string)
>   and some examples of <Entry>, I see that the XML datatype of Entry
>   is string. (or any?)

This is another good question.  As outlined by the WSDL, <Entry> is not 
defined as a ComplexType.  This simply means that Entry is an implicit 
type defined only in the semantic of the service.  The <Entry> element 
(reflecting the Entry QName) is used to demarcate related property 
elements in a return message, but since the service is based on document 
style messaging, it does not define a specific ComplexType for Entry.

When the property values associated with a particular entry are returned 
in a QueryResponse message, the property values are enclosed in an <Entry> 
envelope within the array of xsd:any elements.
 
>   And, do the XML schema of Basic Namespace Components (in section
>   1.1) and Required Entry Properties (in section 1.2.2.2.1) have not
>   to be provided in this RNS document? (as appendix?)

Only the QNames must be defined.  Section 1.1 presents the ?Type? values 
possible for any namespace entry.  These ?Type? values are literally 
identified by the QName defined.  They are not objects but rather a 
property value or attribute of an object.  For this reason, they are 
stored as strings and presented by the service in the form of a QName for 
consistent value comparison.

Section 1.2.2.2.1 lists all entry property names.  These ?names? are used 
in the composition of a query to denote which properties the requestor is 
interested in.   Furthermore, they are used to envelope the property 
values returned in response messages.  So these QNames are represented 
within the WSDL as entry properties only for the purpose of declaring the 
data types descriptively within the WSDL.

I hope that I properly understood your questions, please let me know if I 
misunderstood you.

Best regards,
Manuel Pereira
------------------------------------------------------
IBM Almaden Research Center
1-408-927-1935                 [Tieline: 457]
mpereira at us.ibm.com
------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/ogsa-naming-wg/attachments/20050805/98065db9/attachment.htm