[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [cgmo-webcgm] Issue: 5.7.3 Interface WebCGMMetafile - attribute src
Dave, sorry, you are correct of course, I was a bit too short in my answer. The para should be changed, like all places where we try to prohibit the picterm. It becomes too complicated IMO. Facts: - we have the requirement to use a full fragment in certain cases - hence this full fragment will contain a picTerm - this picTerm may or may not contain a picBehavior So in all cases like this one here, we would need a phrase like "If a URI fragment is present, and if it contains the so called picTerm portion of the fragment, it must not contain a behavior term, and the default behavior assumed for picTerms without a spelled out behavior will be ignored as well. ..." My suggestion was that now that we know that picBehavior doesn't make sense in certain places, we could simply add a phrase there like "If a URI fragment is present containing a picBehavior, the picBehavior will be ignored." Just looking for simpler words. Also, we can test, whether a viewer will successfully ignore a picBehavior in these places. We can not test whether an HTML page contains a compliant URL fragment. Dieter > -----Original Message----- > From: Cruikshank, David W [mailto:david.w.cruikshank@boeing.com] > Sent: Friday, April 14, 2006 10:25 PM > To: dieter@itedo.com; cgmo-webcgm@lists.oasis-open.org > Subject: RE: [cgmo-webcgm] Issue: 5.7.3 Interface > WebCGMMetafile - attribute src > > Dieter, > > I don't think that was the question.... > > The paragraph quoted has a sentence: > 'If a URI fragment is present, it must not contain a picture > behavior term, following the "Picture behaviors" rule for > links to CGM content from non-CGM content.' > It is not a sentence that parses very well (i.e., remove the > clause between the commas and it isn't even a sentence). Are > there too many commas or some left over words from some time > in the past. > > I think the question you are addressing is whether the > requirement (not containing a picture behaviior term) is > correct. That's a different issue. > > Thx...Dave > > > > Technical Fellow - Graphics/Digital Data Interchange Boeing > Commercial Airplane 206.544.3560, fax 206.662.3734 <-- NEW > NUMBERS david.w.cruikshank@boeing.com > > -----Original Message----- > From: Dieter Weidenbrück [mailto:dieter@itedo.com] > Sent: Friday, April 14, 2006 12:58 PM > To: Galt, Stuart A; cgmo-webcgm@lists.oasis-open.org > Subject: RE: [cgmo-webcgm] Issue: 5.7.3 Interface > WebCGMMetafile - attribute src > > In those cases where the picBehavior doesn't make sense, > shouldn't we rather simply say that this part is ignored by > the recipient? > > Example: > an <a href=...> element on an HTML page contains a > picBehavior where it shouldn't. How do we test for compliance? > The test can only be that the viewer does whatever is the > intended behavior, which is to ignore whatever is there. > This would also cover the cases where picTerm is required > because a full fragment is required. > > Thoughts? > > Dieter > > > -----Original Message----- > > From: Galt, Stuart A [mailto:stuart.a.galt@boeing.com] > > Sent: Friday, April 14, 2006 9:45 PM > > To: cgmo-webcgm@lists.oasis-open.org > > Subject: [cgmo-webcgm] Issue: 5.7.3 Interface WebCGMMetafile > > - attribute src > > > > Hello, > > > > I am having a bit of difficulty parsing the following paragraph: > > > > > > src of type WebCGMString > > The URI of the current document. On setting, the new > document pointed > > to by the URI is loaded by the user agent. > > The user agent must fully parse the fragment identifier (if > > any) in the URI and execute the indicated behavior. If a > URI fragment > > <WebCGM20-IC.html> is present, it must not contain a > picture behavior > > term, following the "Picture behaviors" > > <WebCGM20-IC.html> rule for links to CGM content from non-CGM > > content. If the CGM resource pointed to by the URI is > currently loaded > > for the object, the user agent shall not reload the CGM (similar to > > the specification of a same-CGM URI for the _replace behavior > > <WebCGM20-IC.html> on a CGM-to-CGM link.) Upon retrieval, if no > > WebCGM document is open in the viewer, an empty string <> is > > returned. > > > > Specifically: > > If a URI fragment is present, it must not contain a picture > behavior > > term, following the "Picture behaviors" rule for links to > CGM content > > from non-CGM content. > > > > I am assuming that the URI must not contain any embeded > behavior, that > > the fact that it must follow the behavior rules is leftover from a > > previous edit session? > > > > > > > > > > > > -- > > Stuart Galt > > SGML Resource Group > > stuart.a.galt@boeing.com > > (206) 544-3656 > > > > > > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]