Comments (5)
Thanks for letting me know! There's a bit more of these unfinished sentences in the project... Sorry, it's the chaotic way I tend to write things down.
Anyways, to answer the question:
Two separate RDF developers (who did not know each other) gave me the exact same reason for using Named Graphs: They wanted to extend the schema.org
ontology by adding properties to these items in a local graph.
I don't think even this usecase is appropriate for named graphs. They were actually using an external resource that did not provide them with the things they needed. The things that they would add (the translations) are not re-usable, so in the end they will just keep spreading a URL that doesn't provide people with the things that they will come to expect. The schema.org URL still won't provide the translations that they wrote!
I believe a better solution is to copy the resource (in this case a part of the schema.org ontology), and extend it, and host it somewhere else, and use that URL. I'd like to see a more organic usage of URLs that actually provide meaningful and valuable machine readable properties, including translations and icons.
from atomic-data-docs.
Do I understand you correctly that your recommendation for the schema.org example is to formally create a subclass of the ontology?
...because making a fork with different content (added triples to cover a new language strings) without formally renaming the project sounds bad to me.
from atomic-data-docs.
There's a bit more of these unfinished sentences in the project...
Right. Just spotted another one at the end of https://docs.atomicdata.dev/schema/intro.html#atomic-schema
Sorry, it's the chaotic way I tend to write things down.
I can suggest to add the word FIXME
whenever you are leaving something incomplete.
That way it is possible to grep for incomplete stuff, and you might even add such grep check as part of a git push hook or an mdbook publish hook (if such exist - I have not yet embraced that tool myself).
from atomic-data-docs.
Fixed the dangling sentences!
I can suggest to add the word FIXME whenever you are leaving something incomplete.
Good idea!
Right. Just spotted another one at the end of https://docs.atomicdata.dev/schema/intro.html#atomic-schema
Thanks, fixed it!
Do I understand you correctly that your recommendation for the schema.org example is to formally create a subclass of the ontology? ...because making a fork with different content (added triples to cover a new language strings) without formally renaming the project sounds bad to me.
Well, to be honest, I think forking it with a new subject is preferable to re-using it and add properties to it, but is still not the optimal scenario. Ideally, you'd create a PR and add properties / translations to the source, like what is happening here in this repo (see #21). But in any case - you want the world to be able to use your improvements!
from atomic-data-docs.
Well, to be honest, I think forking it with a new subject is preferable to re-using it and add properties to it, but is still not the optimal scenario. Ideally, you'd create a PR and add properties / translations to the source, like what is happening here in this repo (see #21). But in any case - you want the world to be able to use your improvements!
Obviously the optimal scenario is a different collaborative one than the scenario you presented: I assume those choosing to work elsewhere has first considered and given up on the collaborative approach for whatever reason.
from atomic-data-docs.
Related Issues (20)
- Add usecase for knowledge base software
- Tracking issue: renaming things and changing URLs
- WebAuthn + Atomic Authentication
- On trailing slashes for URLs / subjects HOT 4
- Multiple Keys per Agent - Sessions
- Use expiration time in x-atomic HTTP authorization
- Dealing with local subjects / identifiers / local-id / @id / blank nodes
- CI failing, can't build mdbook-open-gh HOT 2
- Compositional Classes - multi-class resources
- Agent scopes - new Agents for the same user with limited access
- Currency datatype / property
- CI fails to build mdbook-open-on-gh HOT 1
- Article / tutorial for data modelling
- Status for potential use cases
- Templates - Generate pre-filled groups of resources
- Limiting creation of too much data for invitees
- Combining / trimming commits.
- Docs sourcing data from Atomic Server instead of git repo
- Renaming repos HOT 1
- Consider alternative to mdbook
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from atomic-data-docs.