Comments (10)
Ok, will do. I'll submit a new PR for that.
from vc-data-model.
I vote separate document.
from vc-data-model.
+1 on separate document.
But related question: I don't see that WebIDL has the representational horsepower to construct a graph. So how does a LinkedDataSignature2015 get generated for it?
from vc-data-model.
Why should it be in a separate document? I thought we wanted to show that WebIDL was a valid syntax.
from vc-data-model.
@burnburn Reasons that it might make more sense to have it in a separate document:
- WebIDL is for the browsers, primarily, therefore the WebIDL should be in a "Browser API" spec (this is 1-2 years down the road, btw).
- There may be many other supported syntaxes, for example, we've successfully converted the data model to YAML and XML, and we probably wouldn't put those in the data model spec.
- We may want to focus on the most likely serialization and then point to other serialization specs if it makes sense to do so.
- WebIDL isn't really a syntax, right? It's more like a way of expressing a programming data model.
from vc-data-model.
@msporny Reason 1 makes sense, since we are particularly interested in making clear that no browser support or modifications are required for this first effort.
Reason 2 is circular, since you are assuming that those would not go into the data model spec without discussion to make that decision. Personally I don't believe they need go in, but others might disagree.
Reason 3 I agree with. However, whether or not WebIDL belongs depends on whether it will be "one of the most likely" syntaxes. Based on reason 1, probably not.
Reason 4 I disagree with. WebIDL is a fairly concrete syntax with defined implementation behavior. If your statement were true, then would could just agree to define our data model in WebIDL and be done.
I am not arguing for WebIDL to remain. I merely want the reasons for removing it to be clear so we can begin developing our criteria for why certain syntaxes will go into the document and others won't.
from vc-data-model.
I support having one syntax in all the examples in the spec document (JSON-LD would be my preference) but being very clear in the language that multiple syntaxes are possible and providing examples in other syntaxes as an appendix or other related resource.
from vc-data-model.
@burnburn the WebIDL has been commented out in the spec (but not removed). Should we close this issue and move the WebIDL to its own spec? Granted, most of the WebIDL is now out of date (as the data model has shifted slightly and will probably continue to shift over time). I don't think anyone is asking for WebIDL at this point, and if they do, we can express it in a separate spec.
from vc-data-model.
from vc-data-model.
The spec no longer includes WebIDL and there are no plans to include it for 1.0. Closing this issue as the group seems to have reached consensus on this. We can always add WebIDL back in to the spec (or create a separate spec w/ WebIDL definitions).
from vc-data-model.
Related Issues (20)
- Specify that it is important to validate the `issuer` value HOT 8
- Specify what kind of processing is safe on a returned document HOT 21
- Ensure `credentialStatus` `id` field is optional HOT 5
- Verifying a VC should return the same credential regardless of the verification method HOT 3
- Clarify embedded proof extension point HOT 3
- phrasing and/or punctuation for input "inputBytes or inputDocument and inputMediaType" needs work HOT 4
- reconsider `@id` for `mediaType` term HOT 17
- Does the specification need a normative "Credential Type Specifications" section? HOT 5
- (editorial) "bitstring" vs "bit string" HOT 1
- `Type-Specific Credential Processing` is better phrasing than `Credential Type-Specific Processing` HOT 2
- Backtick characters in Internationalization / Language examples HOT 2
- typo in Terms of Use HOT 2
- Support of SHACL Schema in Version 2.0 HOT 4
- "โฆ" as a term name in the context file? HOT 2
- Unnecessary direction attribute? HOT 12
- EnvelopedVerifiablePresentation missing in data model HOT 5
- first example contains an http url identifying a credential HOT 5
- Remove at risk issue markers for property extension points. HOT 1
- What does the hash values in ยงB.2 mean? HOT 4
- Proposal: remove ambiguity and asymmetry as it relates to subject identifiers HOT 7
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 vc-data-model.