Is this legal?
Chad Berkley
berkley at nceas.ucsb.edu
Thu Jul 17 14:04:51 PDT 2003
would this be a choice between 1..n controlPoints, 1..4 cornerPoints or
1 bilinear fit? So, it should validate if you do something like:
<georeferenceInfo>
<controlPoint/>
<controlPoint/>
<controlPoint/>
<controlPoint/>
<controlPoint/>
<controlPoint/>
</georeferenceInfo>
or if you do
<georeferenceInfo>
<cornerPoint/>
<cornerPoint/>
</georeferenceInfo>
or
<georeferenceInfo>
<bilinearFit/>
</georeferenceInfo>
but not if you do this:
<georeferenceInfo>
<cornerPoint/>
<cornerPoint/>
<cornerPoint/>
<cornerPoint/>
<cornerPoint/>
</georeferenceInfo>
or
<georeferenceInfo>
<controlPoint/>
<controlPoint/>
<cornerPoint/>
<cornerPoint/>
<cornerPoint/>
</georeferenceInfo>
or
<georeferenceInfo>
<bilinearFit/>
<bilinearFit/>
</georeferenceInfo>
it's kind of weird, but now that I look at it, it seems ok...at least
from looking at the picture. I don't know what the schema looks like.
chad
Dan Higgins wrote:
> Hi All,
>
> In the spatialRaster module of eml2, we have the contruction shown
> below where georeferenceInfo is followed by a choice of one of 3
> elements (cornerPoint, controlPoint, or bilinearFit. But cornerPoint and
> controlPoint are defined with caridinalitiies greater than 1! Is this
> legal? (or meanngful?) Since the Choice element has a cardinality of 1,
> doesn't this mean that only ONE child is allowed? If so, one cannot have
> multiple cornerPoint or controlPoint elements (unless they are placed
> within a Sequence)?
>
>
> geoReference
>
> Dan
>
> --
> *******************************************************************
> Dan Higgins higgins at nceas.ucsb.edu
> http://www.nceas.ucsb.edu/ Ph: 805-892-2531
> National Center for Ecological Analysis and Synthesis (NCEAS)
> 735 State Street - Room 205
> Santa Barbara, CA 93195
> *******************************************************************
>
--
-----------------------
Chad Berkley
National Center for
Ecological Analysis
and Synthesis (NCEAS)
berkley at nceas.ucsb.edu
-----------------------
More information about the Eml-dev
mailing list