@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix foaf: <http://xmlns.com/foaf/0.1/> .
@prefix mcr: <https://registry.apicrafter.io/vocab#> .
@prefix dt: <https://registry.apicrafter.io/datatype/> .
@prefix cat: <https://registry.apicrafter.io/category/> .
@prefix country: <https://registry.apicrafter.io/country/> .
@prefix tool: <https://registry.apicrafter.io/tool/> .

dt:android_permission a skos:Concept ;
    skos:inScheme <https://registry.apicrafter.io/> ;
    skos:topConceptOf <https://registry.apicrafter.io/> ;
    skos:notation "android_permission" ;
    skos:prefLabel "Android platform permission name"@en ;
    skos:definition "Name of a permission defined by the Android platform, as an app requests it in a uses-permission element of AndroidManifest.xml and as the constants of android.Manifest.permission hold it. Almost all start with android.permission. followed by an uppercase name (android.permission.CAMERA); a few older ones use a com.android.<component>.permission. prefix (com.android.voicemail.permission.ADD_VOICEMAIL). APK analysis tools and VirusTotal list them to show what an app can access. Apps can also define their own permissions with any package-style name; the regexp covers only the platform form."@en ;
    skos:example "android.permission.ACCESS_COARSE_LOCATION" ;
    skos:example "android.permission.POST_NOTIFICATIONS" ;
    skos:example "com.android.voicemail.permission.ADD_VOICEMAIL" ;
    mcr:status "draft" ;
    mcr:isPII false ;
    mcr:classification "categorical" ;
    mcr:regexp "^(?:android|com\\.android\\.[a-z]+)\\.permission\\.[A-Z][A-Z0-9_]*$" ;
    rdfs:seeAlso <https://developer.android.com/reference/android/Manifest.permission> ;
    rdfs:seeAlso <https://virustotal.readme.io/reference/file-object-androguard> .