How about "Deprecated" as an additional column of information?

[rsignell-usgs]

For me, one of the motivations for this list was the original "alias" column that would list known values that people are currently using for these services. This would be of tremendous help to get our work done immediately, and I think it would be very useful to others. From the discussion on #1, which shot this concept down, the fear is that people would continue to use these alternate forms. But why not simply call the column "deprecated", instead of "alias". Wouldn't that suffice?

[tomkralidis]

@rsignell-usgs +1 for deprecated.

[smrgeoinfo]

There is definitely some utility in mapping existing usages in the wild to a more restricted set of recommended terms. +1

[rsignell-usgs]

Great! @smrazgs or @tomkralidis , do we have a draft of that "alias=>deprecated" column somewhere?
My git skills are not good enough to retrieve the original -- I thought we had it in the 1st draft

[smrgeoinfo]

@rsignell-usgs I went back and looked at the old LinkPropertyLookupTable.csv table that has an 'alias' column, and the strings in the 'alias' column are all identical to the strings we now have in the 'identifier' column.

[rsignell-usgs]

I can add the ones I know about as a starting point. @tomkralidis, should I just add extra column to the existing csv on my fork and submit a PR?

[emiliom]

I'm with @rsignell-usgs; if the previous 'alias' column values looked similar to current 'identifier' values, that probably means that the main alternate (deprecated) identifiers that should be added are the esri-style urn's. They're in wide use (as the Geoportal default; eg, 'urn:x-esri:specification:ServiceType:Gmd:URL.wms') and won't go away soon, so being able to interpret them more consistently by mapping into LinkPropertyLookupTable.csv would be fantastic. There might be others, though, so this may be a 1:many mapping.

[tomkralidis]

@rsignell-usgs sounds good, yes add an extra column (at the end?) and submit PR.