RE: [emergency] <resourceDesc> (aka Issue #32)

["R. Allen Wyke" <emtc@nc.rr.com>]

I think you are on to something here - we need to either change or
clarify the word "type". Art just sent a great explanation, that helped
me better understand what was intended. Since the word "kind" doesn't
plug right in, how about:

"The human readable text describing the type, such as 'map' or 'photo',
and content of the resource file"

Allen

On Thu, 2003-12-04 at 20:26, Rex Brooks wrote:
> Hey, lets just change the word "typ"e to "kind" and maybe we'll lose 
> this whole question, eh? We should bear in mind how overloaded the 
> term "type" is. It depends on what standard or API you are working in 
> programmatically, and whether you are working to XML or RDF, too.
> 
> Just a thought,
> Rex
> 
> At 4:46 PM -0500 12/4/03, Poindexter, Gary W (BearingPoint) wrote:
> >Eliot wrote:
> >
> >==>Example: <resourceDesc>photo of kidnapping victim</resourceDesc>
> >
> >In the example, the term "photo" conveys the "type" of the resource
> >file (other examples could be of type "voice", "map", "seismometer
> >trace" etc)<==
> >
> >Content "type" should not be defined by the content of the element, it
> >should only be defined by a "type" element or type attribute such as
> >'<resourceDesc type="photo">...' and there should be an enumeration of the
> >allowable types (like photo, sound, map, seismometer trace, etc.)
> >
> >gary
> >
> >-----Original Message-----
> >From: Eliot Christian [mailto:echristi@usgs.gov]
> >Sent: Thursday, December 04, 2003 2:45 PM
> >To: emergency@lists.oasis-open.org
> >Subject: Re: [emergency] <resourceDesc> (aka Issue #32)
> >
> >
> >At 01:57 PM 12/4/2003 -0500, Allen Wyke wrote:
> >>[...]
> >>1. Eliot's
> >>(http://lists.oasis-open.org/archives/emergency/200312/msg00013.html):
> >>
> >>"The text describing the resource file."
> >
> >I withdraw that suggestion after discussion on the call that clarified
> >what Art had intended in his response to Allen.
> >
> >>2. And the one from the minutes of the call
> >>(http://lists.oasis-open.org/archives/emergency/200312/msg00016.html),
> >>although it put back in the very issue I had - using the word "type",
> >>which is redundant with <mimeType>.
> >>
> >>"The human readable text describing the type and content of the resource
> >>file"
> >
> >Example: <resourceDesc>photo of kidnapping victim</resourceDesc>
> >
> >In the example, the term "photo" conveys the "type" of the resource
> >file (other examples could be of type "voice", "map", "seismometer
> >trace" etc)
> >
> >
> >To unsubscribe from this mailing list (and be removed from the roster of the
> >OASIS TC), go to
> >http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgro
> >up.php.
> >
> >
> >******************************************************************************
> >The information in this email is confidential and may be legally
> >privileged.  Access to this email by anyone other than the
> >intended addressee is unauthorized.  If you are not the intended
> >recipient of this message, any review, disclosure, copying,
> >distribution, retention, or any action taken or omitted to be taken
> >in reliance on it is prohibited and may be unlawful.  If you are not
> >the intended recipient, please reply to or forward a copy of this
> >message to the sender and delete the message, any attachments,
> >and any copies thereof from your system.
> >******************************************************************************
> >
> >
> >To unsubscribe from this mailing list (and be removed from the 
> >roster of the OASIS TC), go to 
> >http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php.
-- 
R. Allen Wyke
Chair, OASIS Emergency Management Technical Committee
http://www.oasis-open.org/committees/emergency