[LandXML] Re: Versioning
- From: "Nathan Crews" <nathan.crews@xxxxxxxxxxx>
- To: <Peter_Kistler@xxxxxxxxxxx>, <landxml@xxxxxxxxxxxxx>
- Date: Wed, 23 Jul 2003 13:26:21 -0600
Hi Peter,
Yes, the online LandXML documentation does get updated, but LandXML-1.0 as
of July 17 2002 has not changed. Yes, we did update the schema using the
same 1.0 until we agreed to stop and publish a set version 1.0. Now that we
have a 1.0 starting point, I can assure you the next version will not be
1.0, but 1.x or 2.0.
I think the concept of major and minor version numbers is very good and you
may be pleased to know that the draft version of the next version of LandXML
is 1.1. As it indicates, there are minor changes/additions to attributes,
but does not contain any renamed elements or other items that would wreck a
programmers day.
The latest draft can be found at
www.landxml.org/schema/landxml-1.1/landxml-1.1.xsd
This draft contains proposes changes that have been requested and discussed
since last July 2002.
As it turns out version numbers, XML and XSLT are so very touchy and we do
need to be careful how versioning is treated. We must continue to change the
version number if the schema changes at all (no more of the previous
version-date method).
I think your point and experiences supporting LandXML are familiar to many
of us; who also get problem files containing elements that we do not support
at all or do not support correctly.
Thanks for the rants and persistance...
Regards,
Nathan Crews
-----Original Message-----
From: landxml-bounce@xxxxxxxxxxxxx
[mailto:landxml-bounce@xxxxxxxxxxxxx]On Behalf Of Peter Kistler
Sent: Monday, July 21, 2003 2:16 PM
To: landxml@xxxxxxxxxxxxx
Subject: [LandXML] Versioning
Hello all,
Its been a year since I last brought the issue of versioning to the =
table. Well its time again. I'm sure most people are in the same =
situation that I am. I usually on get a few weeks, if I'm lucky, out of =
the year to update the LandXML component of our software with the latest =
changes. This usually coincides with receiving a LandXML file that we =
don't fully support. So I look at the file in a text viewer to see the =
version number (always version 1.0). Step 2, go the web site to see if =
there is an update, web site still reports Version 1.0. Step 3, check =
the "Change Notes" to see what's been added, last updated June 2002. =
Step 4, do a properties on the "Online Documentation" page to see when =
it was last changed, today the file date is "July 2, 2003". Steps 5-??: =
Look at the file in XMLSpy, Step through the file in the debugger, Pray =
to Bill Gates for divine intervention, ... Once I do find the offending =
/ unsupported element, I then have to figure if there are any =
differences between the version in the file and version on the web =
site...
The ranting is over. I would like to propose that versioning following =
Major.Minor.Intermediate scheme. A major version would occur any time =
there are X number of new elements added or modified. A minor change =
would be a few new elements added or a fundamental change in an existing =
element, e.g. changing from "N E Z" to "X Y Z" coordinate definition. =
Intermediate would entail the addition of an attribute or element to an =
existing element.
I would like to thank Nathan and his group for all the time and effort =
they have put into LandXML to make it work. I know that this has been a =
major undertaking, and I cringe to think if we had to do this with a DXF =
file.
Regards,
Peter
Peter Kistler
Senior Software Engineer
Trimble Navigation Ltd
7403 Church Ranch Blvd, Suite 100
Westminster CO, 80021
Phone: 720 887 4337
Email: peter_kistler@xxxxxxxxxxx
Other related posts:
