airsalliance / airs-xml

Automatically exported from code.google.com/p/airs-xml
Creative Commons Zero v1.0 Universal
3 stars 2 forks source link

make tAgency.Key required #19

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
This came from a discussion in Rochester ... and I am not certain that I 
am accurately presenting it ... but ...

Key Original is currently an Optional requirement and =0 ...if it was 
mandatory and =1 ... then each data set would have to have the unique 
identifier (which it has to have anyway) that would allow that data to be 
recognized for future updates/downloads

This is intended to make it easier for a software to download the same - 
although updated - data from another software on multiple occasions as it 
would be able to easily read the courses of the data and then compare with 
the existing set ...

Original issue reported on code.google.com by clivemjo...@gmail.com on 31 May 2010 at 6:26

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
More prescise explanation ... From the Annotation:

<xs:element name="Key" type="xs:nonNegativeInteger" minOccurs="0">
                <xs:annotation>
                    <xs:documentation>This is an optional unique number representing a vendor's internal way of tracking an agency. This can be used as meta data to uniquely describe an Agency</xs:documentation>
                </xs:annotation>
            </xs:element> 

A way to uniquely describe an Agency (and other fields) is exactly what we’re 
looking to do.  But the schema makes this element optional as well as the <Key> 
associated with ServiceGroup, Site, and SiteService: all the things that we 
want to be able to uniquely identify import-over-import.  It would be great if 
we had some sort of Key or ID element for each piece of data that we may be 
importing.

Original comment by clivemjo...@gmail.com on 14 Jul 2010 at 8:58

GoogleCodeExporter commented 9 years ago
may also want to make the Key more flexible (ie, allow other characters and not 
just numeric)

Original comment by eric.c.j...@gmail.com on 27 Jul 2010 at 5:20

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Is this redundant with item 24? Can they be combined?

Original comment by bleeb...@gmail.com on 9 Dec 2011 at 6:59

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by e...@ejahn.net on 18 Feb 2012 at 1:58