[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Font mapping/default style - partly done
Hi all, I spent some time going through the whole spec and discovered that this task had impact on several chapters. I'm circulating what I've done up to now. All that's left to do is the creation of Chapter 9 and I'm planning on doing that before COB today (Friday). Over the weekend, I'll be incorporating all of this into the working draft for final posting on Monday in preparation of the vote to move to CD on Wednesday. Thx...dave <<config_edits.html>> Technical Fellow - Graphics/Digital Data Interchange Boeing Commercial Airplane 206.544.3560, fax 206.662.3734 david.w.cruikshank@boeing.comTitle: No title
There are some CGM Version 3 attribute and control elements for which it is desirable to override the default value in CGM:1999, when an explicit definition of the value is not present in the CGM file. This would also allow defintion of the rendering behavior of CGM Version 1 and Version 2 files, where those attribute and control elements are not allowed.
This is accomplished in WebCGM using a standard XML DTD to encode the allowable elements and their values in an XML instance. Examples and more details can be fouund in the WebCGM application configurable items chapter.
In order to facilitate font interchange, WebCGM defines a method to specify mapping font names during the import process.
This mapping is accomplished in WebCGM using standard XML DTD. Examples and more details can be found in the WebCGM application configurable items chapter.
In the 4th para, add a new bullet to the end of the unordered list
in the defintion of webcgmfragment replace "xcfterm" with "resrcterm"
replace the definition of xcfterm with
resrcterm ::= "xcf(" resrcurl ")" | "xcf(" resrcurl ");aci(" resrcurl ")" |
"aci(" resrcurl ")" | "aci(" resrcurl ");xcf(" resrcurl ")"
replace the defintion of xcfurl, with
resrcurl ::= (char)+
replace 2 occurences of "xcfurl" with "resrcurl"
3.1.1.5 Resolving relative IRIs for resource files
The above
fragment EBNF defines an resrcterm production whose
'resrcurl' parameter identifies an XML Companion File and/or
a Application Configurable Items file associated the WebCGM identified by the
IRI. WebCGM
viewers that support XCF must
interpret the fragment, locate and load the XCF. WebCGM viewers that support ACI
files must interpret the fragement and load the ACI file only on the initial
load of a WebCGM file. The 'resrcurl' parameter is itself a
IRI, and it
can be absolute or relative. WebCGM viewers shall resolve a relative
'resrcurl' IRI relative to the
IRI of the
WebCGM instance with which the resource file is a companion — i.e.
relative to the WebCGM file referenced by the base part of the IRI containing the
fragment — rather than relative to the file containing the IRI reference (e.g.,
an HTML file).
EXAMPLE. Suppose an HTML document contains a hyperlink
(href attribute on <a> element) to a WebCGM
illustration, and that hyperlink IRI contains a
fragment specifying to load and apply an XML Companion File:
http://www.example.org/parts-list.htmlhttp://www.example.org/illustrations/some-part.cgm#xcf(some-part.xml)Then the relative IRI
"some-part.xml" is resolved according to the location of the
associated CGM, not according to the location of the HTML:
http://www.example.org/illustrations/some-part.xmlSimilarly, if the fragment were
#xcf(companions/some-part.xml), then that IRI resolves to:
http://www.example.org/illustrations/companions/some-part.xml
3.1.2.7 ACI File
The fragment syntax can only be used to load an Application Configurable Items file (ACI) along with the WebCGM file. An interpreter that supports WebCGM DOM shall load and apply the ACI file then load WebCGM file.
Interpreters that do not support the WebCGM DOM may ignore this fragment type.
At the end of para 1, change "three" to "four"
add scenario 4
Scenario 4: A companion file could also be used to associate a WebCGM default configuration file (See Chapter 9 for more information) with the initiation of a WebCGM viewer application via the processing instruction mechanism:
Example 4.4: A companion file processing instruction is used to tell the viewer application to apply configuration defaults for font mapping and style properties with the referenced file.
<?webcgmconfig href="myconfig.xml" ?> |
<webcgm version="2.0" id="root-cgm"
filename="sample_2.cgm"<bindByName apstargetname="bolt_100"
screentip="Replacement part:bolt-100B"/><bindByName apstargetname="wingnut_9"
screentip="Replacement part:wingnut-T9A"/></webcgm> |
replace "none" after "Other" with
A method for the user specification of font substitution is described in the Application Configurable Item chapter.
Add a Note at the bottom
Note: The semantic latitude for many of these cases is addressed in the Application Configurable Items chapter, allowing explicit defintion of rendering behavior for V1/V2 files and for those V3 and later files that have not specified values.
in para 1 add a new item to the bulleted list
add at end
Configuration files (ACI)
The ACI file is not extensible. There shall be no content in conforming ACI file instances beyond what is defined and allowed by the Appliction Configuration Items of Chapter 9.
add at end
Configuration files (ACI)
The ACI file is not extensible. There shall be no content in conforming ACI file instances beyond what is defined and allowed by the Appliction Configuration Items of Chapter 9.
9. Application configurable items
9.1 Overview
The WebCGM Configuration File (WCF) allows the user to improve font interchange by specifying desired font mapping between CGM files and WebCGM applications. The WCF also provides a mechanism
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]