add "compoundliteral" as example in "blank-node-use-cases"

w3c / N3

W3C's Notation 3 (N3) Community Group

47 stars 18 forks source link

add "compoundliteral" as example in "blank-node-use-cases" #136

Closed VladimirAlexiev closed 1 year ago

VladimirAlexiev commented 1 year ago

https://w3c.github.io/N3/spec/#x3-6-3-blank-node-use-cases

Composite information: when describing composite pieces of information, such as street addresses, telephone numbers and dates

Add:

... Representing Compound literals is another typical use of this pattern.

domel commented 1 year ago

In principle, I agree. But we should remember about discussing about i18n in RDF 1.2. @VladimirAlexiev can you provide a PR?

VladimirAlexiev commented 1 year ago

@domel

this spec somewhat boldly talks about the new "text direction" work/ideas without giving any reference. I didn't post an issue, but maybe this needs to be fixed? It is highly nontrivial how ^^i18n:ar-EG_rtl is magically "transformed" to дататъпе ^^rdf:langString
yes, I'll make some PRs

gkellogg commented 1 year ago

Probably best to suspend anything more on this until the RDF-star WG takes a direction; it may make sense to take a different direction, but I think N3 should take it's lead from discussions/decisions there.

There are arguments against i18n and Compound Literals, but they have less impact on the ecosystem. The "right" way to do this may be at the model level, with a fourth element added for language-tagged literals, but that has it's own major consequences.

Track https://github.com/w3c/rdf-concepts/issues/9 an https://github.com/w3c/rdf-star-wg/blob/main/docs/text-direction.md.

VladimirAlexiev commented 1 year ago

@gkellogg can you review #148?

it adds a Note and link to https://github.com/w3c/rdf-star-wg/blob/main/docs/text-direction.md
but maybe I should also add a link to https://github.com/w3c/rdf-concepts/issues/9 ?