RE: CaveXML work plan

New Message	Reply	About this list	Date view	Thread view	Subject view	Author view

From: Kouts, Devin S. (DEVIN.S.KOUTS_at_saic.com)
Date: Sat Jan 19 2002 - 17:45:40 CET

Next message: Michael Lake: "Re: Personnel Element?"
Previous message: Peter MATTHEWS: "Re: Personnel Element?"
Maybe in reply to: Peter MATTHEWS: "CaveXML work plan"
Next in thread: Michael Lake: "Re: CaveXML work plan"

Message-Id: <881CC7991757D51196CF00508BCFE591035708EC@mcl-its-exs03.saic.com>
From: "Kouts, Devin S." <DEVIN.S.KOUTS_at_saic.com>
To: cavexml_at_cartography.ch
Subject: RE: CaveXML work plan
Date: Sat, 19 Jan 2002 11:45:40 -0500
Content-Type: text/plain
Sender: owner-cavexml_at_karmail.ethz.ch
Precedence: bulk
Reply-To: cavexml_at_cartography.ch

Nothing overtly offensive in what you propose but just one comment. The
first objective is very broad in scope, and seems ultimately unacheivable by
this small assemblage of know-it-alls. I.e. "produce a format ... for ...
speleological data", the scope of such a format would be tremendous.

I would improve that paragraph by changing the following phrase "including
data for cave surveying and mapping" to read "beginning with data for cave
surveying and mapping".

After that standard is established many people in this forum may likely drop
out and let the hydrologists, biologists, geologists, etc. carry on with the
inclusion of additional "speleological data".

DSK

Devin S. Kouts
SAIC Program Manager &
Senior Systems Engineer
703-676-6555 - office
703-966-8448 - cell
703-821-1796 - fax
devin.s.kouts_at_saic.com

-----Original Message-----
From: owner-cavexml_at_karmail.ethz.ch
[mailto:owner-cavexml_at_karmail.ethz.ch]On Behalf Of Peter MATTHEWS
Sent: Saturday, January 19, 2002 12:53 AM
To: cavexml_at_cartography.ch
Subject: CaveXML work plan

Dear All,

Although a lot of survey and xml issues have been raised by the group over
the past year and a lot of excellent discussion on them has taken place, we
haven't really established any conclusions yet. It is time we reviewed
where we are at, and where we go from here.

Now that we have a much better feel for what's involved, I would like first
of all for us to do a quick check that we are still happy with our
Objectives and Task List, and then, with general agreement on the separate
tasks before us, systematically tackle them one by one.

If we are to end up with general agreement on a final standard, it is
important that everyone can follow and understand what is being done along
the way. A systematic step-by-step approach will be needed to achieve
this. And as software engineers know, it pays to sort out the "analysis and
design" before beginning the fun part, the programming. This is not to say
that some "programming" (here, XML design) should not be done early to
check out various feasibilities etc.

Below are the existing Objectives and Tasks as currently shown on our web
page, together with a new section which I have called "Approach", which
aims to clarify our planned general approach to the project. I have also
numbered them for easier reference during the discussion, and indented
three sub-tasks which I now notice should have been indented on the web
page.

I think the best thing will be first to ask for general comments, and after
that look at any individual points as seen necessary.

Keep in mind that although we are concentrating on cave survey data at this
point, our results (principles) should ultimately be applicable to any
speleological data.

If you do want to respond during this review but cannot do so just yet,
please email me directly saying how much time you need. And if as we go
through the review you are in agreement with a point, or do not have any
extra comment, please indicate this also, so that we have a better idea of
who is participating. I hope everyone can find the time to help.

Objectives (The broad targets we want to achieve)
=========

1. Produce a data format which is hardware and software independent for the
transfer and the archiving of speleological data, including data for cave
surveying and mapping, and utilising existing international transfer
standards such as XML and related standards if possible.

2. Co-operate with relevant other groups where necessary in arriving at the
format.

3. Provide public ongoing progress information during the work of the
group, including an annual report to UISIC.

4. Achieve international agreement for the format.

5. Promote wide knowledge of and use of the format among cavers, cave
managers and cave/karst researchers.

6. Produce explanatory and training material for use of the format.

7. List, Facilitate and organize production of software to make use of the
format.

Approach (The overall way in which we want to tackle the project)
========

1. Understand and document the data structure of a cave survey. Include in
the documentation as many variations of survey method as possible.

2. Decide how our XML standard would fit into the overall scheme of survey
and mapping procedures.

3. Prepare a pilot CaveXML draft standard to completion, one which is
limited to a commonly used simple form of cave survey.

4. Expand the CaveXML standard to cover the more complex alternatives.

Tasks (Individual tasks which will need to be done to achieve our
Objectives.
===== This is the original list, and some are already partly or
fully done.
[My comments shown in square brackets] )

1. Draw up the Scope and Objectives for the group. [Done, now for review]

2. Establish the official WG delegate for each interested country (UIS
voting is by country). [Not started]

3. Catch up with the good work which has already been done in this area:
Each existing worker to post a "summary" of what they have done, as well as
point us to their detail, e.g. via their web page. {Done]

4. Establish website and Mailinglist as a platform for discussion and
publishing roadmaps, working drafts and results. [Done]

5. Decide on the range of fields which we need to consider in a survey data
transfer:

     5.1 Draw up a survey and mapping ERD (Entity Relationship Diagram)
recognizing the
     difference between surveying and mapping data. [I am about ready to
post an
     initial draft]

5.2 Fill out the fields needed in each entity of the ERD. [Many
already discussed]

5.3 Define each of these fields.

6. Define structure of the XML file: root-element, nesting, elements and
attributes, etc.

7. Produce regular working drafts for the proposed standard.

8. Provide DTD and Schema.

9. Provide Documentation of the field definitions and data structure.

10. Publish the Working Drafts for discussion and comments.

11. Make Revisions after public comment.

12. Vote by WG delegates.

13. Ratification by UISIC.

14. Publicise the format after acceptance.

15. Produce explanatory and training material.

16. List software needed and organise it to get done.

*************************

So first of all, are there any *general* comments about the above
Objectives, Approach and Tasks, ... or whatever? Please try to reply within
a week or so, say by Mon 28 Jan, or else let me know if you need longer.
After that, we'll look at them in more detail.

Regards,

Peter

Next message: Michael Lake: "Re: Personnel Element?"
Previous message: Peter MATTHEWS: "Re: Personnel Element?"
Maybe in reply to: Peter MATTHEWS: "CaveXML work plan"
Next in thread: Michael Lake: "Re: CaveXML work plan"

New Message	Reply	About this list	Date view	Thread view	Subject view	Author view

This archive was generated by hypermail 2b30 : Thu Jan 31 2002 - 23:00:01 CET