Skip to content

foaf:gender and foaf:phone with normalized tel: URIs#2

Merged
namedgraph merged 1 commit into
masterfrom
foaf-phone-gender
Jul 16, 2026
Merged

foaf:gender and foaf:phone with normalized tel: URIs#2
namedgraph merged 1 commit into
masterfrom
foaf-phone-gender

Conversation

@namedgraph

Copy link
Copy Markdown
Member

Follow-up to #1, per the vocabulary cascade (W3C → domain vocabs → schema.org → custom):

  • schema:gender schema:Male/Femalefoaf:gender "male"/"female" (FOAF covers it, and sits above schema.org in the cascade)
  • schema:telephone literal → foaf:phone <tel:+370…>: the mapping BIND normalizes source values to E.164 — bare 7-digit numbers are Vilnius landlines (area code 5), national format drops the leading 8, 370…/+370… pass through, unrecognized formats yield no tel: URI. Same URI-construction pattern as LinkedDataHub-Apps ETL mappings (e.g. demo/copenhagen/libraries.rq).

All 140 phone values in the current Seimas feed normalize cleanly (tel:+37052096…); persons.trig rebuilt and validated (148 graphs). The BIND pattern is documented in etl/ONTOLOGY-NOTES.md for reuse in future mappings with phone numbers.

🤖 Generated with Claude Code

FOAF sits above schema.org in the vocabulary cascade and covers both
properties: gender as the spec-recommended "male"/"female" literals,
phone as a tel: URI. Phone numbers are normalized to E.164 (+370) in
the mapping BIND — bare 7-digit source values are Vilnius landlines
(area code 5), national-format numbers drop the leading 8, unknown
formats yield no tel: URI. Same URI-construction pattern as
LinkedDataHub-Apps ETL mappings (e.g. demo/copenhagen).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant