emergency-msg message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: GML and Resource
- From: "Ham, Gary A" <hamg@BATTELLE.ORG>
- To: emergency-msg@lists.oasis-open.org
- Date: Tue, 06 Feb 2007 16:26:30 -0500
Folks,
I am trying to write the Data Dictionary reference for
our implementation of GML using geo-oasis.
In our structure we
have a "Location Type" consisting of three elements:
1.
LocationDescription: xsd:string
2. Address:
ciq:xal
3. TargetArea:
geo-oasis:where
My discussion
will concern only number 3 on this list.
The schema shows the
TargetArea element to be of TargetAreaType from the types
schema.
TargetAreaType should then be of type
geo-oasis:WhereType.
This is consistent
with our other Types so I plan to make the Data dictionary entries consistent
with the schema.
So far, no
problem.
Question: How broad
do we want our location to be?
An
geo-oasis:whereType gives a choice of
gml:Point
gml:LineString
gml:CircleByCenterPoint
gml:Polygon
gml:Envelope
Did we mean to have
Location have the option of all of these elements?
Or should I make
TargetAreaType a restriction on WhereType that limits the choices to one or more
of the options.
I originally thought
that Point would be simple and appropriate for resource messages (the larger
scope is certainly needed for future updates to DE and CAP). But the name as
TargetArea makes me think the larger scope was intended by the committee for
resource messaging as well.
Personal opinion:
For resource, I would rather use Point. Too many options already are making
resource messages harder to deal with.
I need a consensus.
R/s
Gary A. Ham
Senior Research
Scientist
Battelle Memorial
Institute
540-288-5611 (office)
703-869-6241
(cell)
"You would be surprised what
you can accomplish when you do not care who gets the credit." - Harry S.
Truman
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]