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

 


Help: OASIS Mailing Lists Help | MarkMail Help

cgmo-webcgm message

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


Subject: [no subject]


ISSUE:  should WebCGM 2.0 have more detail about search?



3.2.1.3
The viewer behaviour described here refers to query/search. WebCGM 2.0 =
still does not have a syntax for this, neither has the DOM. Access to =
individual text elements is impossible.
So how is search being performed?


3.2.1.3 defines a search/match priority, but then says:  "Further =
details of behavior of viewers with respect to identifying matches or =
communicating the identity of matches is not specified in WebCGM."  It =
was explicitly undefined in 1.0, and is currently the same in the 2.0 =
text.

"Search" is not mentioned in the 2.0 Requirements:
http://www.cgmopen.org/technical/WebCGM_20_Requirements.html

RECOMMENDATION:  no change -- leave the "how" of search undefined and =
implementation dependent, in 2.0 as in 1.0.  (Consider starting a 2.1 =
Requirements document now.)

Regards,
-Lofton.







------_=_NextPart_001_01C57057.837BACA8
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.50.4522.1800" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN =
class=3D140233220-13062005>I'm=20
comfortable with leaving wording at it is.&nbsp; The fact that the =
content=20
attribute is an enabler is enough for me.&nbsp; In fact in our case the =
content=20
of paras is extracted and indexed as part of the compound document=20
preparation.&nbsp; The search is then done a level up from the CGM =
viewer with=20
the search results (cgm containing the string) potentially firing off =
the viewer=20
to display the particular cgm file.</SPAN></FONT></DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D140233220-13062005></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2><SPAN=20
class=3D140233220-13062005>thx...Dave</SPAN></FONT></DIV>
<BLOCKQUOTE>
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Lofton Henderson=20
  [mailto:lofton@rockynet.com]<BR><B>Sent:</B> Monday, June 13, 2005 =
5:43=20
  AM<BR><B>To:</B> cgmo-webcgm@lists.oasis-open.org<BR><B>Subject:</B>=20
  [cgmo-webcgm] ISSUE: should WebCGM 2.0 have more detail about=20
  search?<BR><BR></FONT></DIV>From Dieter's comments:<BR><FONT=20
  color=3D#0000ff><U><A=20
  =
href=3D"http://lists.oasis-open.org/archives/cgmo-webcgm/200506/msg00021.=
html"=20
  =
eudora=3D"autourl">http://lists.oasis-open.org/archives/cgmo-webcgm/20050=
6/msg00021.html</A><BR><BR></U></FONT>ISSUE:&nbsp;=20
  should WebCGM 2.0 have more detail about search?<BR><BR>
  <BLOCKQUOTE class=3Dcite cite type=3D"cite">3.2.1.3<BR>The viewer =
behaviour=20
    described here refers to query/search. WebCGM 2.0 still does not =
have a=20
    syntax for this, neither has the DOM. Access to individual text =
elements is=20
    impossible.<BR>So how is search being =
performed?</BLOCKQUOTE><BR>3.2.1.3=20
  defines a search/match priority, but then says:&nbsp; "Further details =
of=20
  behavior of viewers with respect to identifying matches or =
communicating the=20
  identity of matches is not specified in WebCGM."&nbsp; It was =
explicitly=20
  undefined in 1.0, and is currently the same in the 2.0 =
text.<BR><BR>"Search"=20
  is not mentioned in the 2.0 Requirements:<BR><A=20
  href=3D"http://www.cgmopen.org/technical/WebCGM_20_Requirements.html"=20
  =
eudora=3D"autourl">http://www.cgmopen.org/technical/WebCGM_20_Requirement=
s.html</A><BR><BR>RECOMMENDATION:&nbsp;=20
  no change -- leave the "how" of search undefined and implementation =
dependent,=20
  in 2.0 as in 1.0.&nbsp; (Consider starting a 2.1 Requirements document =

  =
now.)<BR><BR>Regards,<BR>-Lofton.<BR><BR><BR><BR><BR></BLOCKQUOTE></BODY>=
</HTML>

------_=_NextPart_001_01C57057.837BACA8--


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