@prefix this: . @prefix sub: . @prefix np: . @prefix dct: . @prefix npx: . @prefix xsd: . @prefix orcid: . @prefix rdfs: . @prefix fip: . @prefix prov: . sub:Head { this: a np:Nanopublication; np:hasAssertion sub:assertion; np:hasProvenance sub:provenance; np:hasPublicationInfo sub:pubinfo . } sub:assertion { sub:MIF-MID a fip:Available-FAIR-Supporting-Resource, fip:FAIR-Enabling-Resource, fip:FAIR-Specification, fip:Knowledge-representation-language; rdfs:comment """The “MapInfo Interchange Format” .mif, usually associated with the .mid file, is the export format of the MapInfo software, designed for GIS interoperability. It is a clear, well documented, well supported and stable ASCII text file. It can be expected from GIS applications that they can correctly import MIF/MID data and that map layers in the application’s own format can be exported to MIF/MID. MIF/MID is a preferred format for file type GIS. """; rdfs:label "MIF/MID (Mapinfo Interchange Format)" . } sub:provenance { sub:assertion dct:creator orcid:0000-0001-6899-760X . } sub:pubinfo { this: dct:created "2025-12-04T16:58:54Z"^^xsd:dateTime; dct:creator ; dct:license ; npx:introduces sub:MIF-MID; prov:wasDerivedFrom . sub:sig npx:hasAlgorithm "RSA"; npx:hasPublicKey "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCoKFb7LKlXyBB7BUvjFF9bDJNk0WxH3Xerr4H3v/VCiRVshEDl3BZVekbMMmdRe+TOPyc8AOLd9IAL2VfVVD/T0rmCHk7Pw7DQjI96mwyeXhE7f4g0WG5UT5Pxxm0Rzy7IrYnEaaVDs7dkZUt952M6qWlHfTwCQDcXJhZfLiXoMwIDAQAB"; npx:hasSignature "BVQTNTX5Bj+aEqy4GiJ8r5x1bWnHld7qKPOz6BGxNW0YvnfmrJvaWq5ffdzMrxl7ZYoXho8pljj96uC2+DH5y3GaTnC691pEo11LC/NC6HhEaVcu9cRSzfMjKqloOMsDZGzsPAEaEqox+hjVevDEGVXn9E2E3+/YY4NKmATEH0Q="; npx:hasSignatureTarget this: . }