Comments (9)
I think the only mention of ids in the context of blank nodes in the explainer document is here:
without depending on the particular set of blank node identifiers used in the original serialization of the input RDF Dataset
While blank nodes do not have identifiers nor labels nor any syntactic form in the abstract RDF data model, I guess they can have "identifiers" in a serialization of an RDF dataset (such as N-Quads).
The Turtle Recommendation systematically uses the term "blank node label". So does the N-triple Recommendation. The JSON-LD specification uses the term "blank node identifier" and so does RDF/XML. Finally, and somewhat more surprisingly, the RDF Semantics specs also uses the term blank node identifier.
All this today is that there is no consistency even among the formal RDF related specifications. And although I do agree that, when it comes to the formal standard to be defined by the WG, an airtight terminology is necessary, let us not forget that this is an explainer text, whose goal is to explain the underlying concepts to non-RDF experts, primarily AC reps, to help them cast their votes. We may make things more difficult, albeit more precise, to understand the problem area if we are not careful. In this context, it does not seem to be so problematic to use the term "identifier", or perhaps "label".
from rch-wg-charter.
IIRC, David Booth raised a similar issue a while back, and we made some changes.
I think the only mention of ids in the context of blank nodes in the explainer document is here:
without depending on the particular set of blank node identifiers used in the original serialization of the input RDF Dataset
While blank nodes do not have identifiers nor labels nor any syntactic form in the abstract RDF data model, I guess they can have "identifiers" in a serialization of an RDF dataset (such as N-Quads). Arguably we're okay since we say that we don't depend on them, but maybe there's cleaner language possible; something like:
without depending on how blank nodes are serialized in the original syntax of the input RDF Dataset
Another option is just to drop the whole "without ..." part, leaving:
Such a canonicalization function can be implemented, in practice, as a procedure that deterministically labels all blank nodes of an RDF Dataset in a one-to-one manner.
In case that the issue is more about the language of "labelling" a blank node, we could go one further and write about producing a labelling of blank nodes; something like:
Such a canonicalization function can be implemented, in practice, as a procedure that outputs a deterministic one-to-one labelling of all blank nodes of an RDF Dataset.
Though I would see that as somehow equivalent and maybe a bit more verbose?
from rch-wg-charter.
I would just yank the sentence.
from rch-wg-charter.
As well, suppose that the function depended on the order of triples in the input document. Is that allowable?
from rch-wg-charter.
As well, suppose that the function depended on the order of triples in the input document. Is that allowable?
Since the function is defined on an RDF Dataset (abstract syntax), for which the order is not significant, I think it should be clear that it would not be allowed. Granted, it would be even clearer if we spelled it out. Do you think we need to?
from rch-wg-charter.
If there is an explicit exclusion for blank node labels in input documents then I think there needs to be exclusions for other aspects of input documents. The, probably better, alternative would be to require that the only information the algorithm has access to is an RDF dataset. (But that should have been the case all along - bringing in the possibility of utilizing other information is at best misleading.)
from rch-wg-charter.
the algorithm has access to is an RDF dataset. (But that should have been the case all along
That was the intention.
- bringing in the possibility of utilizing other information is at best misleading.
agreed; therefore I propose to either
- yank the end of the sentence ("without depending on..."), or
- make it more generic, something like "without depending on any feature of the input serialization (blank node labels, order of the triples, etc...)."
from rch-wg-charter.
agreed; therefore I propose to either
- yank the end of the sentence ("without depending on..."), or
- make it more generic, something like "without depending on any feature of the input serialization (blank node labels, order of the triples, etc...)."
I am (mildly) in favor of the second alternative
from rch-wg-charter.
@pfps, with PR #103 merged, can we close this issue?
from rch-wg-charter.
Related Issues (20)
- status of [arnold-longley-2020] HOT 19
- how the canonicalization algorithm is chosen HOT 3
- fix HTML title
- AUEB/MMlab supports the W3C LDS WG HOT 3
- Jolocom supports the W3C RCH WG HOT 5
- Create a registry of hash functions HOT 3
- Semmtech supports the W3C RCH WG HOT 4
- Rename "Linked Data Hash" as "RDF Dataset Hash" HOT 1
- A is B considered harmful HOT 6
- Need a glossary for the acronyms the lds-wg-charter HOT 1
- ED of explainer points to charter doc. HOT 1
- W3C Web of Things (WoT) WG supports the W3C LDS WG HOT 8
- Vague mentions of json-ld context work item needs clarification HOT 25
- 3 Round Stones supports the W3C RCH WG HOT 5
- Vrije Universiteit Amsterdam supports the W3C RCH WG HOT 5
- Coordinate with WebAppSec HOT 6
- Consider defining a canonical serialization to bytes, rather than a hash HOT 5
- Stale expressions of support HOT 1
- quantifier scoping HOT 3
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 rch-wg-charter.