Rabi I
Enable an agent to recognise Rabi I as a named Islamic calendar month, resolve dated occurrences under an explicit calendar convention, and contextualise associated observances.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
recalled by Codex without web access - no source was read
Researched by: Codex
Purpose and description
Enable an agent to recognise Rabi I as a named Islamic calendar month, resolve dated occurrences under an explicit calendar convention, and contextualise associated observances.
Rabi I, commonly called Rabi al-Awwal, is the third month of the Islamic lunar calendar.
It can be Normalise supported Rabi I name variants to the registered concept.; Distinguish the recurring month from a year-specific occurrence.; Resolve a Rabi I date using a declared calendar convention and locality.; Compare conflicting boundary announcements without discarding their provenance.; Attach attributed observance links to relevant days.; Flag conversions or scheduling decisions that lack sufficient calendar context..
Distinguishing features
The intended referent is a recurring calendar month, rather than a discipline despite the batch context.
Rabi I denotes Rabi al-Awwal; the numeral distinguishes it from Rabi II rather than identifying a year.
Its ordinal position is third: after Safar and before Rabi al-Thani, as listed by [Muslim Aid](https://www.muslimaid.org/islamic-calendar/rabi-al-awwal/).
A named month is distinguishable from an occurrence such as Rabi I in a specified Hijri year.
An observance associated with Rabi I does not define the entire month or establish universal participation.
Scope
+ Names and transliterations identifying Rabi I
+ Third-month position and relationships to adjacent Islamic months
+ Year-specific occurrences qualified by calendar convention and locality
+ Evidence and uncertainty governing month boundaries
+ Links to community-specific commemorations within the month
- Islamic studies as a discipline and its institutional classifications
- The complete Islamic calendar and its general algorithms
- Rabi II as a separate named month
- Biographies of people associated with the month
- Mawlid rituals, theology and event administration
- Civil public-holiday legislation and employment entitlements
Characteristics
- Resolved calendar sense
- Rabi al-Awwal; unresolved registry referent Prevents the inherited knowledge-domain classification from becoming a mistaken field-of-study model.
- Month ordinal
- 3; dimensionless calendar position Distinguishes Rabi I from Rabi II and anchors calendar sequencing.
- Name equivalence
- Label linked to language, script, transliteration convention and evidence Supports recognition without treating an ambiguous bare Rabi as a confirmed match.
- Occurrence year
- Hijri year number with era and calendar convention Identifies which recurrence is being dated.
- Boundary determination
- Observation-based; calculated; tabular; authority announcement; unspecified Makes the basis for assigning an occurrence's dates inspectable.
- Boundary status
- Predicted; announced; retrospectively documented; disputed; superseded Separates provisional dates from dates established under a named authority.
- Occurrence extent
- Start and end boundaries; elapsed days under the selected convention Allows interval membership and date conversion to be checked.
- Observance attribution
- Observance linked to community, day designation and supporting source Keeps community practice distinct from the identity of the calendar month.
Where this came from
wikidata · CC0 1.0
Drafted structure
Bundle to layer to finding to question, as the second pass will find it: 6 bundles · 11 layers · 16 findings · 32 questions.
Rabi I identity Establish the calendar-month sense and distinguish similarly named referents.
The registry has no definition, and the batch's discipline framing does not fit the apparent referent.
Registry sense
Connect the registry entry to the intended named month.
Calendar month resolution
Treat the Islamic month interpretation as the working sense while preserving the need to verify the originating registry record.
- Does the originating registry identifier resolve specifically to Rabi al-Awwal? provenance
- Should the INF.KNW placement be retained as a calendar concept or corrected under registry classification rules? boundary
Rabi name disambiguation
Recognise supported variants while protecting the distinction between the two Rabi months.
First Rabi labels
Record label equivalence with linguistic evidence; do not silently equate an unqualified Rabi label with Rabi I.
- Which Arabic forms and transliterations are explicitly attested for this month? provenance
- What contextual evidence distinguishes Rabi I from Rabi II when a source abbreviates the name? definition
Rabi I calendar position Represent the month's recurring place within the Islamic year.
Recognition depends on calendar relationships rather than a fixed civil date or season.
Month sequence
Anchor the month through its ordinal and neighbours.
Third-month adjacency
Use the third-month identity to check links to Safar and Rabi II.
- Does the selected calendar identify this occurrence as month three? definition
- Do its boundaries connect consistently to the preceding Safar and following Rabi II occurrences? measurement
Recurring month and occurrence
Separate the named calendar unit from its dated instances.
Hijri year binding
Require a year and calendar convention before treating Rabi I as a specific temporal interval.
- Does the reference denote Rabi I generally or an occurrence in a specified Hijri year? boundary
- Which era and calendar convention qualify the recorded year number? definition
Rabi I boundary evidence Make the determination and revision of occurrence boundaries explicit.
An agent needs to know whose dates it is using before converting or scheduling a Rabi I occurrence.
Start determination
Record the basis and applicability of the transition from Safar into Rabi I.
Safar to Rabi I boundary
Qualify the proposed or announced start with its method, authority and geographic applicability.
- What observation, calculation or announcement establishes the start of this Rabi I? provenance
- For which locality or community is that determination applicable? boundary
- Is the start predicted, announced or retrospectively documented? measurement
End and revisions
Track the transition into Rabi II and reconcile competing boundary records.
Rabi I interval integrity
Check the occurrence's duration against its recorded boundaries and retain evidence when dates change.
- What evidence establishes the end of Rabi I and the beginning of Rabi II? provenance
- How many days lie within the occurrence under the selected calendar convention? measurement
- Which dependent dates must be recalculated if an applicable boundary is revised? action
Rabi I date use Support qualified conversion and interpretation of dates within the month.
The month name alone cannot establish a unique civil date or timestamp.
Civil date correspondence
Record reproducible mappings from a Rabi I day to another calendar.
Qualified date conversion
Bind conversions to the Hijri year, day number, calendar method and target calendar.
- Which Rabi I day and Hijri year are being converted, under which calendar method? measurement
- Which target calendar and conversion source produce the reported civil date? provenance
- Should the result be presented as provisional because the occurrence boundaries remain unsettled? action
Day boundary interpretation
Distinguish a calendar-day label from an exact local interval.
Rabi I local day extent
Require explicit day-boundary and timezone conventions when a Rabi I date is used for timestamp-level decisions.
- Does the source use an evening-start religious day, a midnight-start civil display or another stated convention? definition
- Which locality and timezone are required to determine the intended interval? measurement
- Can the requested scheduling action proceed with a date label, or does it require exact boundaries? action
Rabi I observance context Associate commemorations and historical claims with the month using explicit attribution.
Cultural associations help interpret references but must not become universal calendar properties.
Mawlid association
Link the month to attributed commemorations of Muhammad's birth.
Community-specific commemoration
Rabi al-Awwal is associated with commemorating Muhammad's birth; record the practice and day designation for the relevant community. See [Islamic Relief UK](https://www.islamic-relief.org.uk/resources/islamic-calendar/rabi-al-awwal/).
- Which community or institution associates an observance with a specified day of Rabi I? provenance
- Does the source describe a commemorative convention, a historical birth-date claim or both? boundary
- What evidence supports displaying this observance for the user's selected community? action
Historical and administrative links
Keep historical dating and civil recognition separate from month identity.
Attributed Rabi I associations
Represent historical-event dates and holiday designations as sourced links owned by neighbouring models.
- Which source supports each historical event's assignment to Rabi I, and how precise is that assignment? provenance
- Does an asserted holiday apply to a specific jurisdiction and year rather than to every Rabi I occurrence? boundary
- Which event or jurisdiction model owns the details needed before acting on this association? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
A model that cannot be lined up against existing standards, identifiers and practice cannot be adopted by anyone who already uses them.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- The intended sense is inferred from the established calendar name; no sense was supplied.
- The supplied field-of-knowledge context does not fit this calendar-month interpretation and should be checked against the registry record.
- This description is based on recall, without source consultation.
- Which of these check these first hold for the sense of Rabi I this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Dating events and documents in the Islamic calendar.
- Determining the timing of Mawlid observances in Muslim communities that celebrate the Prophet Muhammad's birth.
- Which of these real-world use hold for the sense of Rabi I this model covers, and on what evidence? provenance
Typical measurements
Recalled without web access and unsourced; every item is a lead to verify.
- Month length - 29-30 - days
- Position in the Islamic calendar - 3 - ordinal month
- Which of these typical measurements hold for the sense of Rabi I this model covers, and on what evidence? provenance
Failure modes and hazards
Recalled without web access and unsourced; every item is a lead to verify.
- Confusion with Rabi II, the following month.
- Assigning a Gregorian date without specifying the year and calendar convention.
- Assuming all communities begin the month or observe Mawlid on the same date.
- Which of these failure modes and hazards hold for the sense of Rabi I this model covers, and on what evidence? provenance
Regional variation
Recalled without web access and unsourced; every item is a lead to verify.
- The start of the month can differ between communities using local crescent sightings, sightings accepted from elsewhere, or calculated calendars.
- Mawlid observance and its date vary by religious tradition and locality; some Muslim communities do not celebrate it.
- Which of these regional variation hold for the sense of Rabi I this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Rabi II - Rabi II, also called Rabi al-Thani or Rabi al-Akhir, is the fourth Islamic month; Rabi I is the third.
- Safar - Safar is the second Islamic month and immediately precedes Rabi I.
- Mawlid - Mawlid is a commemoration of the Prophet Muhammad's birth, whereas Rabi I is the calendar month in which many communities observe it.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of Rabi I this model covers, and on what evidence? provenance
What the second pass must settle
- Does the original registry source confirm the Rabi al-Awwal sense, and is INF.KNW an intentional placement?
- Does an existing Vercy calendar or world model already own this concept, requiring a link rather than a separate publication?
- Which Arabic spellings, transliterations and abbreviations should be accepted as evidenced name variants?
- Which calendar authorities, geographic scopes and conversion conventions must the initial model support?
- Which community-specific observance dates and historical associations have sufficient evidence to include, and which remain disputed?