OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: xml










"Murray, Bryan P." <bryan.murray@hp.com>  wrote on Mon, 21 Jun 2004
10:07:15 -0700

>

[snip]

> ... I am confused as to how an application could interact
> with a property it does not understand beyond simply displaying or
copying
> its value. If an application does understand a property that falls into
> the xsd:any portion of the resource property document schema, it does not
> need the schema - it already knows the type of this property.

A very good point, but let me check something.

IANAXEB (I am not an xml expert but..) I think even parsing the xsd:any
part of a document into sub-elements with string values makes
assumptions, namely that each child is independent.This is not always
the case for a general xml document; there could, for example, be
key/keyref constraints on the newly added elements so that they are
related to each other (for example, they must exist in pairs.)

Is this allowed in a Resource Properties (RP)document?  If RP is
constrained to be a list of independent children then an application
may, as your use case suggests, copy/display them independently.


Later, Byran Murray wrote:

> Tim,

> I was not asking about a use-case for dynamic properties, but for a
> use-case that requires a schema to be retrieved at runtime from a
> WS-Resource for dynamic properties.

> Bryan


Yes, sorry for the confusion.


Regards, Tim Banks
IBM TP Architecture & Technology. Hursley, UK.
Phone: External +44 1962 815639, Internal 245639



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]