On Mon, 26 Mar 2001 15:15:02 -0500, Ralph Hartley wrote:
>Richard Knapp wrote:
>> This makes is difficult to enter data in an XML editor - no overall structure.
>
>How so? I would think it would make it EASIER. The data items can be
>entered in the same order they were originally recorded. I want to allow
>the structure of the original data (book or other format) to be directly
>reflected in the CaveXML file, even if parts of the survey were entered
>useing different programs.
That can also be done while restricting the number of children but it seems to come down to a matter or personal
preference. I like the way the DOM validation can help ensure a valid XML document structure (parent to child and in my
case a valid shot). Without some sort of guide, I could enter an invalid shot. It is valid as far as the DTD is concerned and
the error will only be caught when the data is processed.
>In fact it is my intention that at lest for the CMAP/CaveXML prototype,
>the output of the converter will be both a valid CaveXML file and a
>valid CMAP file, with the relationship between them directly represented
I haven't use CMAP so I cannot comment on this. However, I am interested in the results of this.
One thing I am a little unclear on: is this a CaveXML format or a middle format that can be transformed into CaveXML or
CMAP? The example in Semantics seems to indicate the format (with <Default element="(element)">) will be transformed
into another XMLdocument.
>> - I don't think you can use ID as an attribute and as a type (however, neither DTDExplorer or Xeena complained).
>
>My view is generally that if the spec doesn't say I can't, then I can.
>The name of an attribute matches the production "Name". I think the
>confusion is because of the fact that if an attribute's name is "ID"
>that does not IMPLY that it is of type ID, but if you can find someplace
>where it says it is FORBIDEN, let me know. A real objection to using ID
>as an attribute name is that it might confuse people.
I think there is a difference between what the spec does and does not allow and what is good XML technique. There was a
_long_ discussion on xml-dev on best Schema practices. There are things not prohibited in the Schema Rec that are still
not good ideas. In this case, the main item - at least for me - is the confusion between the attribute name and the attribute
value.
>> - You have places where there are multiple enumerations using (true|false). This is
>> not compatible with the SGML spec. I encountered this issue on my Exclusion element,
>> too. Mainly a design decision.
>Are we writing XML or SGML? The XML spec says XML is a subset of SGML,
>but maybe it lies (or did I miss something? Won't be the first time.).
XML is derived from SGML. It is not illegal to use the same enumeration in XML but it will not be compatible as SGML.
>> Semantics.html
>> - If a shot has more than one azimuth, it says the values will be averaged. Will this be limited to azimuths of the same
>> reversed and inverted values or all azimuths?
>
>I don't quite understand the question. Certianly if a shot includes both
>for and back sights, they would both be used (with the back sights
>converted).
I think I misread the statement. I missed that the averaging was only applicable to the CrossSection.
If that is not true and this is a method of processing the data, I think it is out of the realm of the document's spec.
>> Overall, I think the lack of structure to the DTD makes it difficult to follow. A full example of the resulting XML might help.
>
>A bunch of examples will be needed. In its current state, I don't think
>the dtd is the way to understand it, at least not yet. The semantics are
>the primary, get that wrong and no amount of syntax will save you.
>> I also highly recommend getting a validating XML editor to see how the data works. Using
>> one resulted in changes in the version I was working.
>With ANY everywhere, it wouldn't help me much. But when I tighen those a
>bit...
>
>Do you know whre I could find good one? It needs to be free and run on
>linux.
All the tools I use are Java 1.1.6 (or better) since I'm using JDK 1.1.8 under OS/2.
For that, Xeena is available from IBM's AlphaWorks site (http://www.alphaWorks.ibm.com/tech/xeena). I got their tar
version as the only other option was a Win Exe.
There is also some hope with XMLEditor but it throws exceptions at certain points (like setting prefereneces).
I also have DTDEditor (free from www.xml4cobol.de). Pretty nice but has trouble finding the root element (so does DTD
Explorer)
- Richard Knapp
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b30 : Mon Apr 02 2001 - 18:00:01 CEST