TEI to SVG - Revision history

Piotr Banski: /* Mapping attributes */ + link

2007-11-28T01:19:16Z

‎Mapping attributes: + link

Piotr Banski: + category

2007-04-05T22:14:13Z

+ category

Conal: /* tei:binaryObject */

2006-07-27T01:27:42Z

‎tei:binaryObject

Conal: /* tei:binaryObject */

2006-07-27T01:25:47Z

‎tei:binaryObject

Conal: /* tei:binaryObject */

2006-07-27T01:24:59Z

‎tei:binaryObject

Dot.porter: /* TEI Elements and their SVG Equivalents (approx.) */

2006-06-08T19:05:00Z

‎TEI Elements and their SVG Equivalents (approx.)

Dot.porter: /* TEI Elements and their SVG Equivalents (approx.) */

2006-06-08T19:04:41Z

‎TEI Elements and their SVG Equivalents (approx.)

Dot.porter at 16:22, 8 June 2006

2006-06-08T16:22:59Z

Dot.porter: /* A Quick Look Through the TEI Figures Module */

2006-06-08T16:08:33Z

‎A Quick Look Through the TEI Figures Module

Dot.porter: /* A Quick Look Through the TEI Figures Module */

2006-06-08T16:07:01Z

‎A Quick Look Through the TEI Figures Module

@@ Line 204: / Line 204: @@
-METS defines @mets:coords on <area>. For TEI, it would be nice to have this attribute available to "regular" elements, not to a special element. The reasoning is that in many cases, especially when dealing with primary source texts, TEI elements refer not to a text in general but to the text as it appears in a specific physical document. It may not make sense to allow @mets:coords on &lt;p>, but it may make perfect sense to allow it on those elements described in Chapter 18 [http://www.tei-c.org/release/doc/tei-p5-doc/html/PH.html Transcription of Primary Sources] that relate to a specific physical occurrance:
+[[METS]] defines @mets:coords on <area>. For TEI, it would be nice to have this attribute available to "regular" elements, not to a special element. The reasoning is that in many cases, especially when dealing with primary source texts, TEI elements refer not to a text in general but to the text as it appears in a specific physical document. It may not make sense to allow @mets:coords on &lt;p>, but it may make perfect sense to allow it on those elements described in Chapter 18 [http://www.tei-c.org/release/doc/tei-p5-doc/html/PH.html Transcription of Primary Sources] that relate to a specific physical occurrence:
 <pre>
 <abbr>
@@ Line 262: / Line 262: @@
 We need to continue looking at SVG, whether we want to be able to import it in a module  or link to external files. Or both.
 ==tei:binaryObject==

← Older revision		Revision as of 22:14, 5 April 2007
Line 299:		Line 299:
	inside them, enabling a usefully approximate rendering of the page		inside them, enabling a usefully approximate rendering of the page
	layout incorporating the transcription.		layout incorporating the transcription.
		+
		+	[[Category:SVG]]

@@ Line 272: / Line 272: @@
       xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
    <desc>This graphic links to a picture of Larry Masinter</desc>
-   <image x="200" y="200" width="100px" height="100px"
+   <image x="200" y="200" width="48px" height="48px"
           xlink:href="data:image/gif;base64,R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAw
     AAAC8IyPqcvt3wCcDkiLc7C0qwyGHhSWpjQu5yqmCYsapyuvUUlvONmOZtfzgFz

@@ Line 271: / Line 271: @@
 <svg width="4in" height="3in" version="1.1"
       xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
-   <desc>This graphic links to an external image
+   <desc>This graphic links to a picture of Larry Masinter</desc>
    <image x="200" y="200" width="100px" height="100px"
           xlink:href="data:image/gif;base64,R0lGODdhMAAwAPAAAAAAAP///ywAAAAAMAAw
@@ Line 281: / Line 280: @@
     F81M1OIcR7lEewwcLp7tuNNkM3uNna3F2JQFo97Vriy/Xl4/f1cf5VWzXyym7PH
     hhx4dbgYKAAA7">
-     <title>My image</title>
+     <title>Larry Masinter</title>
    </image>
 </svg>

@@ Line 267: / Line 267: @@
 ==tei:binaryObject==
-I don't see an equivalent in SVG, but it may be because I don't know where to look.
+A rough equivalent for tei:binaryObject in svg. tei:binaryObject is an svg:image whose xlink:href uses the [http://tools.ietf.org/html/rfc2397 "data" URL scheme].
 =Using SVG with TEI=

← Older revision		Revision as of 19:05, 8 June 2006
Line 27:		Line 27:

	TEI Chapter 22 [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html Tables, Formulae, and Graphics]		TEI Chapter 22 [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html Tables, Formulae, and Graphics]
		+
	Scalable Vector Graphics (SVG) [http://www.w3.org/TR/SVG/ 1.1 Specification]		Scalable Vector Graphics (SVG) [http://www.w3.org/TR/SVG/ 1.1 Specification]

← Older revision		Revision as of 19:04, 8 June 2006
Line 23:		Line 23:

	=TEI Elements and their SVG Equivalents (approx.)=		=TEI Elements and their SVG Equivalents (approx.)=
		+
		+	Quick Links:
		+
		+	TEI Chapter 22 [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html Tables, Formulae, and Graphics]
		+	Scalable Vector Graphics (SVG) [http://www.w3.org/TR/SVG/ 1.1 Specification]

	==tei:graphic and svg:image==		==tei:graphic and svg:image==

@@ Line 163: / Line 163: @@
    <tei:text>text contained on the image</tei:text>
   </svg:g>
 </pre>
 ==Mapping attributes==
-@tei:coords (modelled on @mets:coords)
+Hold coordinates in individual elements using @mets:coords (instead of creating @tei:coords)
 As described in the [http://www.loc.gov/standards/mets/docs/mets.v1-5.html#area METS documentation]:
@@ Line 181: / Line 198: @@
-METS defines @mets:coords on <area>. For TEI, it would be nice to have a similar attribute available to "regular" elements, not to a special element. The reasoning is that in many cases, especially when dealing with primary source texts, TEI elements refer not to a text in general but to the text as it appears in a specific physical document. It may not make sense to allow @mets:coords on &lt;p>, but it may make perfect sense to allow it on those elements described in Chapter 18 [http://www.tei-c.org/release/doc/tei-p5-doc/html/PH.html Transcription of Primary Sources] that relate to a specific physical occurrance:
+METS defines @mets:coords on <area>. For TEI, it would be nice to have this attribute available to "regular" elements, not to a special element. The reasoning is that in many cases, especially when dealing with primary source texts, TEI elements refer not to a text in general but to the text as it appears in a specific physical document. It may not make sense to allow @mets:coords on &lt;p>, but it may make perfect sense to allow it on those elements described in Chapter 18 [http://www.tei-c.org/release/doc/tei-p5-doc/html/PH.html Transcription of Primary Sources] that relate to a specific physical occurrance:
 <pre>
 <abbr>
@@ Line 236: / Line 253: @@
 @svg:points seems to me to be very similar to @mets:coords, except that it cannot be used to form a circle (only boundaries with straight edges)
-I think that I would prefer to use @mets:coords (or something similar) in TEI, rather than trying to take advantage of the various SVG attributes, at least for the more simple cases.
+There may be instances where one would want to use @mets:coords (for simple circles and bounding boxes) and other times when it would make more sense to use svg:x/y/width/height etc. (for more complex shapes).
-In more complex instances, I think we need to continue looking at SVG, whether we want to be able to import it in a module  or link to external files. Or both.
+We need to continue looking at SVG, whether we want to be able to import it in a module  or link to external files. Or both.
@@ Line 245: / Line 262: @@
 I don't see an equivalent in SVG, but it may be because I don't know where to look.

@@ Line 8: / Line 8: @@
 #Tables<br/>Elements: table row cell<br/>I don't immediately see anything corresponding to this in SVG. It wouldn't make sense, anyway - tables are really for organizing textual material. Anything else?
-#Formulae<br/>Elements: formula<br/>Formula already allows for the inclusion of elements from outside the TEI, although the [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#id2784077 examples in the guidelines] do not use namespaces, and namespaces are not mentioned in the text. Should we recommend that <figure> require namespaces for elements pulled in from elsewhere? If so, what about (as in the first two examples) when the notation is non-XML? Is @notation really enough?<br/>How will this section generally be used? Will the most common usages be MathML or ChemML (or something similar from the sciences), or perhaps
+#Formulae<br/>Elements: formula<br/>Formula already allows for the inclusion of elements from outside the TEI, although the [http://www.tei-c.org/release/doc/tei-p5-doc/html/FT.html#id2784077 examples in the guidelines] do not use namespaces, and namespaces are not mentioned in the text. Should we recommend that <figure> require namespaces for elements pulled in from elsewhere? If so, what about (as in the first two examples) when the notation is non-XML? Is @notation really enough?
-simpler formulas expressed in available Unicode characters?</br>"By default, a <formula> is assumed to contain character data which is not validated in any way"<br/>Is this really a good idea? This means that, if you have a formula that contains non-standard characters, you would be unable to use gaiji without customization. That seems strange.
+#*How will this section generally be used? Will the most common usages be MathML or ChemML (or something similar from the sciences), or perhaps simpler formulas expressed in available Unicode characters?<br/>"By default, a <formula> is assumed to contain character data which is not validated in any way"<br/>Is this really a good idea? This means that, if you have a formula that contains non-standard characters, you would be unable to use gaiji without customization. That seems strange.
 #Graphic Images<br/>Elements: figure graphic binaryObject figDesc<br/>The <figure> element is used to contain images, captions, and textual descriptions of the pictures.<br/>The images themselves are specified using the <graphic> element, whose url attribute provides the location of an image.
 <pre>