Wikifunctions:Type proposals
This page is to discuss and decide on proposals for new Types, and for changing existing ones.
Before proposing, you should familiarize yourself with the Function model.
Types are currently being created by Wikifunctions staff. Over time these rights will be handed over to the community.
Proposals for new types to be created
Implementation in progress
In discussion
- complex128
- SI units
- Unit of measurement
- Moment in time
- Julian calendar date
- Grapheme
- Wikifunctions object reference
- Value with error
- configuration of functions for given types
- Geometrical point
- Syntactic type
- Currency
- Named parameters list
Lightweight Wikidata enumerations
Being prepared
Stalled
Something to think about
- Symbol and expression (as in a computer algebra system) - currently no idea yet
- Alphabet
- Context
- Imperial Units
- months in calendars
- Multilingual gloss
- Position on Earth
- URL
Wikidata integration
(These are just the types we will need that are not listed somewhere else)
- Wikidata qualifier
- Wikidata Data type
- Wikidata sitelink
- Unknown value
- Entity schema
"Heavy" data
Heavy data is those that can be more than 1.5MB (where medium data are between 60KB and 1.5MB). This includes most real-world files (jpg, mp3, pdf, zip, exe) and raw forms of data containing in such files (e.g. 1024*768 RGB image has 2359296 bytes in raw form). Wikifunctions currently have limited support for medium data and little support for heavy data (and neither support file uploading for computation). See bytes § Uses for more information.
- Image (raster): basically, a 2D or 3D array of number (though we do need a type to represent both the array and image mode)
- Audio and signal: basically, one number (sampling rate) and one or more (1D) arrays of number, one per channel (though we do need a type to represent all of them)
- Video: audio plus series of image
Unclear necessity / probably unnecessary
- Multidimensional array: can be represented as list of lists, but a dedicated edit interface would be nice (and way to enforce an array not to be jagged)
- Typed tuple: can be represented as nested Z882
- Set: use list instead
- Multiset: use list instead
- Multimap: use list of Z882 instead (see also simple map Z883)
Types that have already been Implemented
- RGBA color
- Grammatical number (singular/paucal/multal)
- Grammatical definiteness
- Grammatical voice (a/p)
- Grammatical affirmation and negation
- Grammatical cases (n/g/d/a)
- Grammatical degree of comparison (p/c/s)
- Chemical element
- Wikidata based types as Wikidata item (Z6001), Wikidata property (Z6002), Wikidata statement (Z6003), Wikidata lexeme form (Z6004), Wikidata lexeme (Z6005)
- Grammatical number (singular/dual/plural) as Grammatical number (singular / dual / plural) (Z28215)
- Breton mutation as Celtic mutation (Z27971)
- Grammatical person (1/2/3) as Grammatical person (3) (Z27970)
- Grammatical gender (a/i) as grammatical animacy (animate / inanimate) (Z26935)
- Grammatical number (s/p) as Grammatical number (singular / plural) (Z26934)
- Hijri calendar month as Hijri calendar month (Z26582)
- Grammatical gender (m/f) as Grammatical gender (m/f) (Z25340)
- Grammatical gender (m/f/n) as Grammatical gender (m/f/n) (Z25501)
- Grammatical gender (c/n) as Grammatical gender (c/n) (Z25502)
- Natural number as Natural number (Z13518)
- Gregorian calendar month as Gregorian calendar month (Z16098)
- Sign as Sign (Z16659)
- Igbo calendar month as Igbo calendar month (Z16927)
- Integer as Integer (Z16683)
- Day of the week as Day of the week (Z17402)
- Gregorian era as Gregorian era (Z17813)
- Rational number as Rational number (Z19677)
- Gregorian year as Gregorian year (Z20159)
- Day of Roman year as Day of Roman year (Z20342)
- Gregorian calendar date as Gregorian calendar date (Z20420)
- float64 as float64 (Z20838)
- Kleenean as Kleenean (Z22112)
- Byte as Byte (Z80)
- Unicode codepoint as Unicode code point (Z86)
Proposals for changing existing types
Changes to existing types
- ...