<commit_before><commit_msg>Create ServiceTypes.md<commit_after>There is an [OGC URN policy document](http://www.opengeospatial.org/ogcUrnPolicy) which recommends that
the "serviceType" have the following node designations:
```
    "urn:ogc:serviceType" ":" name ":" version ":" [binding] [":" profile]
```
In the Geoportal Server metadata editor, the following are used:
```
urn:x-esri:specification:ServiceType:ArcIMS
urn:x-esri:specification:ServiceType:ArcGIS
urn:ogc:dataFormat:GML:2.0
urn:ogc:dataFormat:GML:2.1.1
urn:ogc:dataFormat:GML:2.1.2
urn:ogc:dataFormat:GML:3.0
urn:ogc:dataFormat:GML:3.1.1
urn:ogc:serviceType:CatalogueService:2.0.1:CORBA
urn:ogc:serviceType:CatalogueService:2.0.1:HTTP
urn:ogc:serviceType:CatalogueService:2.0.1:HTTP:ebRIM
urn:ogc:serviceType:CatalogueService:2.0.1:HTTP:EO
urn:ogc:serviceType:CatalogueService:2.0.1:HTTP:FGDC-CSDGM
urn:ogc:serviceType:CatalogueService:2.0.1:HTTP:ISO19115/19119
urn:ogc:serviceType:CatalogueService:2.0.1:Z39.50
urn:ogc:serviceType:CatalogueService:2.0.1:Z39.50:GEOProfile
urn:ogc:serviceType:CatalogueService:2.0.1:Z39.50:SRU
urn:ogc:serviceType:CatalogueService:2.0.2:CORBA
urn:ogc:serviceType:CatalogueService:2.0.2:HTTP
urn:ogc:serviceType:CatalogueService:2.0.2:HTTP:ebRIM
urn:ogc:serviceType:CatalogueService:2.0.2:HTTP:EO
urn:ogc:serviceType:CatalogueService:2.0.2:HTTP:FGDC-CSDGM
urn:ogc:serviceType:CatalogueService:2.0.2:HTTP:ISO19115/19119
urn:ogc:serviceType:CatalogueService:2.0.2:Z39.50
urn:ogc:serviceType:CoordinateTransformationService:1.0
urn:ogc:serviceType:CoordinateTransformationService:1.0:COM
urn:ogc:serviceType:CoordinateTransformationService:1.0:CORBA
urn:ogc:serviceType:CoordinateTransformationService:1.0:Java
urn:ogc:serviceType:GridCoverage:1.0:COM
urn:ogc:serviceType:GridCoverage:1.0:CORBA
urn:ogc:serviceType:OpenLSCoreServices:1.0
urn:ogc:serviceType:OpenLSCoreServices:1.0:SOAP
urn:ogc:serviceType:OpenLSCoreServices:1.1
urn:ogc:serviceType:KML:2.2
urn:ogc:serviceType:SimpleFeatureAccess:1.0:CORBA
urn:ogc:serviceType:SimpleFeatureAccess:1.1:OLE/COM
urn:ogc:serviceType:SimpleFeatureAccess:1.1:SQL
urn:ogc:serviceType:SimpleFeatureAccess:1.2:SQL
urn:ogc:serviceType:SensorObservationService:1.0
urn:ogc:serviceType:WebCoverageService:1.0
urn:ogc:serviceType:WebCoverageService:1.1.0
urn:ogc:serviceType:WebFeatureService:1.0
urn:ogc:serviceType:WebFeatureService:1.1
urn:ogc:serviceType:WebMapService:1.0
urn:ogc:serviceType:WebMapService:1.1
urn:ogc:serviceType:WebMapService:1.1.1
urn:ogc:serviceType:WebMapService:1.3.0
urn:ogc:serviceType:WebMapService:Post:0.0.3
urn:ogc:serviceType:WebProcessingService:0.4
```
I like this structure, and would like to propse a few more that would be managed by Unidata:
```
url:unidata:serviceType:OPeNDAP:2.0.0
url:unidata:serviceType:NetcdfSubsetService:1.0.0
url:unidata:serviceType:CdmRemote:0.1.0
```

Perhaps there is a better way to build this list, but just wanted to get this down here...
{'fraction_non_alphanumeric': 0.13362801768106086, 'fraction_numerical': 0.05440326419585175, 'mean_word_length': 11.791304347826086, 'pattern_counts': {'":': 4, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 1, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7508000', 'n_tokens_mistral': 1214, 'n_tokens_neox': 1174, 'n_words': 120}