Thank Frank for suggesting to make note to get addressed in the spec.
Here's a candidate (it's rather XML generic, *not* ChangeSummary specific
during which work I happened to discover the issue):
XSD defines how XML formats.
For XSD
the XML should be
the XML should be
xmlns:global=""
Yang,
First of all, this is a pretty rare corner case. Even if the global
namespace wasn't null (for example, assume it's just "http://global";),
your example is an SDO Type with two properties named "element1". The SDO
spec says that if you have more than one property with the same name, the
Thank Frank for clarifying "element ref" mapping. I'm working on
ChangeSummary StAX writer,
there're many places Properties/elements need to be outputed as XML,
such as ChangeSummary.Setting.
Supposing we have such Properties definition:
) please?
Thanks.
--
Yang ZHONG
Hi Yang,
"Yang ZHONG" <[EMAIL PROTECTED]> wrote on 09/25/2006 11:50:18
AM:
> More question, is this
>
> mapped to open content please?
No.
> If not (my impression from the specs),
> how to tell local element from global element without NameSpace please?
I'm not sure exactly what you're ask
Thank Frank very much for helping.
More question, is this
mapped to open content please?
If not (my impression from the specs),
how to tell local element from global element without NameSpace please?
On 9/25/06, Frank Budinsky <[EMAIL PROTECTED]> wrote:
Global elements are called open con
Global elements are called open content properties in SDO. The 2.0.1. spec
says that a property is from open content if it appears in
getInstanceProperties() but not in getType.getProperties(). One way to
check this: !d.getType.getProperties().contains(p). Another more efficient
way is !p.getCo
One of my assumptions was wrong: I thought XSDHelper#getGlobalProperty could
be used to help to distinguish local element from global element without
NameSpace.
I don't think so now since a no-NameSpace global element existence does
*not* prove my Property is an element ref to that.
I can't find
Local XML element doesn't have a NameSpace,
neither does global XML element without NameSpace.
It'll be nice for XSDHelper#getNamespaceURI to return "" for local XML
element (since "" is an *invalid* NameSpace)
and to return null for global element without NameSpace (since null is also
used to que
