more about sub-string hotspots

[Lofton Henderson <lofton@rockynet.com>]

One further comment.  I have thought more about this (from minutes)...

[[[
Discussion:  [...]  This only works easily with grobjects.  Things would 
have to be carefully implemented due to model of para/subpara.
]]]

Assuming the ISO defect correction, this would be currently legal according 
to 2.0 (I think!!! I haven't yet found anything in 2.0 to prohibit it, but 
haven't looked carefully enough yet):

BegAPS 'grobject'
   RT x,y extent notfinal substring
   BegAPS 'grobject'
     ApsAttr 'linkuri'
      AT notfinal substring
   EndAPS
   AT final substring
EndAPS

And this bould be 2.0-legal:

BegAPS 'para' content="whole big string"
   RT x,y extent notfinal "whole "
   BegAPS 'subpara' content="big"
     ApsAttr 'linkuri'
      AT notfinal "big"
   EndAPS
   AT final " string"
EndAPS

And one could have a 'grobject' on the outside with a 'para' on the 
inside.  But ... you can't have a 'grobject' outside and 'subpara' 
inside.  And can't have 'content' on 'grobject'.

Regards,
-Lofton.

At 05:39 PM 6/21/2007 -0600, Lofton Henderson wrote:
>One comment and question about the minutes...
>
>[[[
>Sub-string hotspot identification
>Response from US S1000D graphics subproject indicated that the defect 
>resolution to the CGM standard is the correct approach and would solve the 
>issue.
>Discussion:  Defect to the standard clears the way to 
>implementation.   Will this require an erratum to WebCGM 2.0?
>]]]
>
>Is it our intention to retroactively recognize sub-string hotspotting in 
>2.0?  Or do we mean it to be new in 2.1?  The first might require an 
>erratum to 2.0, the second (possibly) might require broadening the 2.0 
>content rules for 2.1.
>
>It is actually more subtle than that.  The way that ISO defect corrections 
>work is that they are considered to apply as of the publication date of 
>the standard.  I.e., when the sub-string APS tagging defect correction is 
>approved, then that is considered to always have been a part of the 
>conformance landscape of CGM:1999.
>
>Therefore, if there is nothing in the current 2.0 text that prohibits 
>sub-string hotspotting, e.g., nothing in 2.0's content model that prevents 
>sub-string APS tagging, then sub-string APS tagging automatically is a 
>feature of 2.0 by virtue of the ISO defect correction.
>
>So, strictly speaking, we might need a 2.0 erratum to *prevent* APS 
>tagging within sub-strings, if we wish sub-string hotspotting to be 
>2.1-legal but not 2.0-legal.
>
>Regards,
>-Lofton.
>
>At 08:02 PM 6/21/2007 +0000, david.w.cruikshank@boeing.com wrote:
>>The document named WebCGM TC telecon minutes 20070620 
>>(20070620_WebCGM_TC_Telecon_minutes.doc) has been submitted by Mr. david 
>>cruikshank to the OASIS CGM Open WebCGM TC document repository. Document 
>>Description: Minutes of telecon View Document Details: 
>>http://www.oasis-open.org/apps/org/workgroup/cgmo-webcgm/document.php?document_id=24466 
>>Download Document: 
>>http://www.oasis-open.org/apps/org/workgroup/cgmo-webcgm/download.php/24466/20070620_WebCGM_TC_Telecon_minutes.doc 
>>PLEASE NOTE:  If the above links do not work for you, your email 
>>application may be breaking the link into two pieces.  You may be able to 
>>copy and paste the entire link address into the address field of your web 
>>browser. -OASIS Open Administration
>
>
>