Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespace proliferation #13

Open
dbooth-boston opened this issue Dec 7, 2018 · 0 comments
Open

Namespace proliferation #13

dbooth-boston opened this issue Dec 7, 2018 · 0 comments
Labels
Category: usage For issues around RDF usage in practice

Comments

@dbooth-boston
Copy link
Collaborator

It's hard to manage all the
namespaces involved in using RDF: FOAF, SKOS, DC and all the
hundreds of specialized namespaces that are encountered when
using external RDF. Namespaces can help organize IRIs into
categories (typically based on the IRI's origin), but this
fact is nowhere recognized in official RDF specs. Indeed,
the official mantra is that IRIs are opaque, and there are
very important design reasons for opacity.[16] But there is
a cost: RDF is stuck in a flat, global naming space analogous
to global variables of 1960's programming languages. Somehow,
modern programming languages deal with namespaces much more
conveniently than RDF does. Perhaps we can learn from them,
without undermining the Web's design principles.

@dbooth-boston dbooth-boston added the Category: usage For issues around RDF usage in practice label Dec 8, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: usage For issues around RDF usage in practice
Projects
None yet
Development

No branches or pull requests

1 participant