LISTSERV mailing list manager LISTSERV 16.0

Help for TEI-GRAPHICS-SIG Archives


TEI-GRAPHICS-SIG Archives

TEI-GRAPHICS-SIG Archives


TEI-GRAPHICS-SIG@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-GRAPHICS-SIG Home

TEI-GRAPHICS-SIG Home

TEI-GRAPHICS-SIG  March 2010

TEI-GRAPHICS-SIG March 2010

Subject:

Re: Developing a proposal for polygons etc.

From:

"John A. Walsh" <[log in to unmask]>

Reply-To:

John A. Walsh

Date:

Wed, 31 Mar 2010 04:59:35 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (52 lines)

+1 for @svg:points. In spite of Sebastian's concerns about DTDs and
.xsd, I think this is the most elegant and standards-based approach.

On Wed, Mar 31, 2010 at 3:01 AM, Conal Tuohy <[log in to unmask]> wrote:
> On Wed, 10 Mar 2010 19:38:29 +0000, Sebastian Rahtz
> <[log in to unmask]> wrote:
>
>>On 10 Mar 2010, at 19:09, Martin Holmes wrote:
>>
>>>
>>> The simple answer is that all we need is @svg:points, added to
>>> att.coordinated.
>>>
>>
>>
>>ah, that's a nice idea. So we arrange it so that you get an extra
>>attribute if some sort of SVG module is loaded.
>
> I like this idea too. It's the simplest suggestion we've had so far which
> deals minimally with Martin's users' requirements. As Martin suggested, this
> isn't about adding an SVG drawing to the zone (which can be done in TEI
> already), with a coloured border, etc; it's actually more like a "clipping
> path" in the sense that it's a path which outlines an area of interest.
>
> The @path should be constrained (in the prose of the guidelines, at least -
> possibly also in schematron) to fall entirely within the bounding box. It
> should be defined to have the "SVG Points" data type:
> http://www.w3.org/TR/SVG/shapes.html#PointsBNF and including the semantics
> that it's a closed shape.
>
> If a need ever arose for zones with smooth curves, or for "compound" shapes
> (i.e. shapes with "holes" in them), we could add yet another attribute
> (@path, I'd suggest) with SVG's "path data" data-type:
> http://www.w3.org/TR/SVG/paths.html#PathData
>
> Finally, I think the rectangular bounding box co-ordinates should remain
> mandatory even when the optional @points (or @path) attribute is present.
> The reason is that they support base-line functionality for
> facsimile-enabled TEI processors. Of course theoretically a bounding box
> could be computed from the @points (or @path) attribute, but I tend to think
> we should require the TEI-encoding software to do this, so that we don't
> make it any harder to write software to display facsimile TEI.
>



-- 
| John A. Walsh
| Assistant Professor, School of Library and Information Science
| Indiana University, 1320 East Tenth Street, Bloomington, IN 47405
| www: <http://www.slis.indiana.edu/faculty/jawalsh/>
| Voice:812-856-0707 Fax:812-856-2062 <mailto:[log in to unmask]>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2011
November 2011
March 2011
October 2010
April 2010
March 2010
August 2009
November 2008
October 2008
September 2008
June 2008

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager