JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for FISH Archives


FISH Archives

FISH Archives


FISH@JISCMAIL.AC.UK


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

FISH Home

FISH Home

FISH  2001

FISH 2001

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Peer Review Opening Message Protection Grad e/Status

From:

"Siddall, Jason" <[log in to unmask]>

Reply-To:

The Forum for Information Standards in Heritage (FISH)

Date:

Fri, 14 Dec 2001 16:47:24 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (170 lines)

Hi

having listened to all that has been said on this matter there seems to be a
few items of note

thanks to you all ... keep the discussion going

GIS does have some potential
It however has some limitations
        1) Even with mapping we will never get away from having to have
common terms and their             meanings. Even if they are on a map or in
a text database, we must know what we mean by
           Listed Building or how we refer to it i.e is it LB, Listed
Building, LIBU etc (as Martin              just noted see an article I have
just written concerning this very issue it will be in      the next SMR news
and is based on research conducted by The National Trust research
Assistant).
        2) Searching within records with or without Mapping will still
require us to tag our              records with the designation - i.e show
me on this map all the listed buidlings etc
        3) Mapping is still a luxury it is not something everyone can use
(however much we would             like to). In a cash strapped
council/organisation it may not be possible to buy lots of         software,
input, ammend data etc
        4) Although we can use maps on the internet (ADS website is a good
example) we seem to be     along way away from being able to use it as we
would a GIS on our systems.
        5) GIS is a great way to define areas but a poor way to maintain
common terminology                 standards.

In fact much of the lists and terminology you are seeing are base line
standards the idea of compliance comes in here and the guidance for
compliance (i am just writing a short article to explain my thoughts on this
matter - this will be available on tuesday 18/12/2001). The terms indeed are
equally applicable to text databases as to a GIS layer. So we will always
need base line terminology standards even if we are using GIS solely (which
i think may happen but is many years away for SMR's).

as for there being no point in developing complex text based terminology and
opting for a GIS standard ... I wonder if that is not putting the cart
before the horse ...

We need FUNDAMENTAL BASE LINE TERMINOLOGY for our lists these can be applied
to a whole host of applications not just a text lookup (although thats what
most people use them for).

without which you will have a case of one person in one county calls a
Scheduled Monument a SAM another may well call it SM its pure chaos. It will
confuse the general public, fellow non archaeologist collueges - who
increasingly want and need to look at our information. We need a base line
accepted terminology so we all know what we mean when we say LB or Scheduled
Monument without having to provide 60+ different mapping scopes to numerous
terms. It is no longer enough that we in our little world of archaeology
understand things ..as statutory status looms we must ensure we are being
very clear about what we mean in our standards.

this is why we need terminology standards.

thats my penny's worth
cheers
Jason

-----Original Message-----
From: Newman, Martin [mailto:[log in to unmask]]
Sent: Friday, December 14, 2001 4:05 PM
To: [log in to unmask]
Subject: Re: Peer Review Opening Message Protection Grad e/Status


I agree that GIS is the best way to define areas of protection status,
however, an agreed list of terms for describing these  is essential,
especially for data exchange. This point is admirably demonstrated in
forthcoming article by Jason which will appear in the next issue of SMR
News.

Martin


-----Original Message-----
From: Wardle, Chris (DSD) [mailto:[log in to unmask]]
Sent: 14 December 2001 15:47
To: [log in to unmask]
Subject: Re: Peer Review Opening Message Protection Grad e/Status


I state the case as I see it as an SMRO. Those SMRs that don't have GIS will
need to get it sooner or later. The amenity societies should also consider
it.
-My considered view is that text based systems alone are not adequate for
identifying Grade/Status.


> -----Original Message-----
> From: Carlisle, Philip [SMTP:[log in to unmask]]
> Sent: 14 December 2001 15:35
> To:   [log in to unmask]
> Subject:      Re: Peer Review Opening Message Protection Grad e/Status
>
> What about those SMR's or amenity societies who haven't got GIS
> capability?
>
> Phil
>
>  -----Original Message-----
> From:   Wardle, Chris (DSD) [mailto:[log in to unmask]]
> Sent:   14 December 2001 15:34
> To:     [log in to unmask]
> Subject:        Re: Peer Review Opening Message Protection Grad e/Status
>
> > -----Original Message-----
> > From: Leonard Will [SMTP:[log in to unmask]]
> > Sent: 14 December 2001 15:07
> > To:   [log in to unmask]
> > Subject:      Re: Peer Review Opening Message Protection Grad e/Status
> >
> > In message
> > <[log in to unmask]>
> > on Fri, 14 Dec 2001, "Wardle, Chris (DSD)"
> > <[log in to unmask]> wrote
> >
> > >I would wish to make the
> > >comment that I don't believe that text based data is any longer the
> best
> > way
> > >of dealing with the  Grade/Status of Monuments.
> >
> > . . .
> >
> > >So take an historic settlement recorded on an SMR: Some of it might be
> a
> > >Conservation Area, other bits (possibly overlapping) might be an
> Register
> > >Park, an SSSI and the bits round the church might be in ecclesiastical
> > use.
> > >There might be 3 separate scheduled monuments. There might be 50 listed
> > >buildings, 1 of which might be Grade I, perhaps 4 might be Grade II*
> and
> > the
> > >rest Grade II. There is no point in trying to sum up all this in a text
> > >database. It is much better to show this complexity as separate layers
> on
> > a
> > >GIS. And it is this that we should be creating standards for.
> >
> > Is it not the case, though, that for each bit or layer, however you
> > decide to divide them up, you have to have some way of specifying its
> > properties? A GIS may well be the best way of separating out the various
> > components, and you can apply indexing terms at various levels of
> > granularity - either to the site as a whole, to sub-divisions, or to
> > individual elements. These terms can be expressed in textual form or as
> > symbols on a graphical representation - though you still need a textual
> > legend to explain what the symbols mean.
>         [Wardle, Chris (DSD)]   Firstly; we need boundaries not symbols.
> Secondly no text based approach, matches what you get from a
> mapped/graphical one.
> > Nothing in what you say seems to reduce the need for a controlled and
> > standardised list of indexing terms.
> >  [Wardle, Chris (DSD)]  So, yes standards are needed; but there's little
> > point in developing complex text based ones when we should be thinking
> of
> > what's needed for GIS.
> >
> > Leonard Will
> > --
> > Willpower Information       (Partners: Dr Leonard D Will, Sheena E Will)
> > Information Management Consultants              Tel: +44 (0)20 8372 0092
> > 27 Calshot Way, Enfield, Middlesex EN2 7BQ, UK. Fax: +44 (0)20 8372 0094
> > [log in to unmask]               [log in to unmask]
> > ---------------- <URL:http://www.willpowerinfo.co.uk/> -----------------

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
February 2024
December 2023
September 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
November 2022
October 2022
August 2022
May 2022
April 2022
March 2022
February 2022
January 2022
November 2021
October 2021
September 2021
May 2021
April 2021
March 2021
February 2021
October 2020
September 2020
May 2020
April 2020
March 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
December 2018
October 2018
May 2018
March 2018
February 2018
January 2018
December 2017
October 2017
August 2017
July 2017
June 2017
April 2017
March 2017
January 2017
December 2016
November 2016
September 2016
July 2016
June 2016
February 2016
January 2016
October 2015
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
November 2014
October 2014
September 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
October 2012
July 2012
June 2012
May 2012
February 2012
January 2012
November 2011
October 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager