Closed westurner closed 4 years ago
What is missing or could be added?
From http://lists.w3.org/Archives/Public/public-vocabs/2014Feb/0130.html :
Properties:
- derivedFrom/previousIncantation property could also be helpful.
- prerequisite/buildsUpon/suggestedPrerequisite properties would be great.
Types for these properties would need to be <Course
... This would then form a graph of Course s and/or OnlineCourse s.
Also from http://lists.w3.org/Archives/Public/public-vocabs/2014Feb/0130.html :
Classes:
- CourseSection
Possible properties for a CourseSection:
Now in the example, EducationEvent that already exist in schema.org (which has many properties like startDate, endDate)is being used for describing CourseSection.
It will be more clear by using new Type like CourseSection, but then we need to think more general type like Section.
I am trying to pull together the various threads and have put together a modified proposal that:
Please take a look at https://docs.google.com/document/d/12YWjLzZC8FiTiOwSAETRIEozeqZdn6O8a4fgqK4t5Ss/edit?usp=sharing
Thanks:)
Building on Vicki's work I suggested changes to the Google doc (1) based on what seems to be areas of consensus on the discussion threads and comments within the doc.
I'm afraid that there are different threads/communities with definitions that may work fine within a narrow purpose, but have conceptual errors when trying to apply the vocabulary more universally. The approach discussed in the group seems to be headed in the right direction. How can we bring the different communities together on this?
For example, moocontology (2) has "instructor" and "event" as properties of Course rather than defining a CourseSection. This can create ambiguity when multiple Course Sections are offered at the same or different times. e.g. This month EdX started a Section of "Introduction to Computational Thinking and Data Science" (course number 6.00.2x). This is not the first time the course was offered. The course content/description is the same for each instance, but the start and end dates change, and the instructors may change over time. There could be Sections going on concurrently with different instructors, but the same course number, learning objectives, description.
I know there are discussions about Course as an extension to schema.org, rather than core; even so, I think we should try to get the different communities together so Course isn't defined as different things by different communities.
-jim
(1) https://docs.google.com/document/d/12YWjLzZC8FiTiOwSAETRIEozeqZdn6O8a4fgqK4t5Ss/edit?usp=sharing (2) https://sites.google.com/site/moocontology/
Is it CourseSession or CourseSection?
(It was CourseSession, but was changed without discussion to CourseSection).
+1 to "CourseSession", Coursera and Stanford MOOC use "session".
Coursera API: https://tech.coursera.org/app-platform/catalog/ Stanford Online: http://online.stanford.edu/courses/all
On Fri, Mar 6, 2015 at 12:00 AM, Wes Turner notifications@github.com wrote:
Is it CourseSession or CourseSection?
(It was CourseSession, but was changed without discussion to CourseSection).
- I vote for "CourseSession". To me, Section implies a physical partitioning; which does not fit.
— Reply to this email directly or view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-77479627.
To be Sharer^^
A man is not old as long as he is seeking something. A man is not old until regrets take the place of dreams.
CourseSession and CourseSection are totally different beasts. A Course may have many CourseSections and CourseSections may have many CourseSessions. For example, at the Univ. of Washington (Seattle) there is a course in the University inventory (catalog) called "Metadata Design Studio". This spring quarter, there are two CourseSections of this Course (SLN 15343 and SLN 15344). This week, (the section I teach) SLN 15344 is in the second CourseSession of the spring quarter. I am less concerned about what Coursera and the Stanfod MOOC call things than with the pattern that holds in the nomenclature of thousands of colleges and universities--at least in the U.S.
hello. I have been thinking about the scope and use cases for this proposal. The discussion above starts with a bullet point referring to "online courses" but I think we have gone beyond that. Also I can see lots of potential implementers above, but nothing about use cases that relate to what a user might want to do. My initial ideas are at http://goo.gl/DnTTsb I would welcome comments/corrections. Apologies if they are sketchy, I wanted to share early rather than make unwarranted assumptions.
hello. I have fleshed out the ideas I mentioned before for more specific scope and use cases, still in google doc at http://goo.gl/DnTTsb . Any comments? I think it would be useful to compare the proposals to these use cases and some examples, but it'ls also be good to have some agreement that the use cases are valid and nothing major is missing before doing that.
Is a google doc the best place to do this, would you rather have it on github somewhere?
@philbarker I've updated the ticket description w/ the link to your google doc containing use cases for these vocabulary extensions.
I think it would be great to build the tests for these use cases (in JSON-LD, RDFa, or just RDF TTL/N3). (the JSON-LD test suite http://json-ld.org/test-suite/reports/ uses earl
for similar reports: http://www.w3.org/TR/EARL10-Schema/ )
Thanks @westurner . I do intend to cross check the use cases against some of the example courses listed above and in the scoping part of the google doc and against the current proposal. I'm not sure that my technical skills extend to building tests along the lines you point to, or what data there is to test (none yet, or maybe I am misunderstanding?)
Thanks! Really just JSON-LD and RDFa examples that demonstrably (and recordedly) evaluate to valid RDFa.
To be clear, I opened this ticket but by no means should this be construed to indicate leadership on this issue. (It may be helpful to start reaching out for more input from e.g. a registrar's office: I believe we're currently missing a way to represent prerequisite edges) On Jun 1, 2015 4:09 AM, "Phil Barker" notifications@github.com wrote:
Thanks @westurner https://github.com/westurner . I do intend to cross check the use cases against some of the example courses listed above and in the scoping part of the google doc and against the current proposal. I'm not sure that my technical skills extend to building tests along the lines you point to, or what data there is to test (none yet, or maybe I am misunderstanding?)
— Reply to this email directly or view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-107376617 .
@westurner - Phil and I had a quick chat about prerequisites last week. He pointed out that we should try to have a mechanism for this which is compatible with our approach to representing learning outcomes. Doing so will make it easier to chain together learning opportunities from a larger pool...
BTW please note that we now have a new W3C Community Group devoted to Course description: https://www.w3.org/community/schema-course-extend/
From schema.org's point of view this issue #195 is probably the best interface between schema.org in general and Course-specific issues, so let's try to keep this issue up to date with any major progress or discussion points, even if more activity moves into the new and more specific Community Group.
From schema.org's point of view this issue #195 is probably the best interface between schema.org in general and Course-specific issues, so let's try to keep this issue up to date with any major progress or discussion points, even if more activity moves into the new and more specific Community Group
- | Project: https://www.w3.org/community/schema-course-extend/
- | MailingList: https://lists.w3.org/Archives/Public/public-schema-course-extend/ "by thread"
I've posted a snapshot of the current community group design in the pending extension, http://webschemas.org/docs/releases.html#g195 ... at this stage without examples. The source was https://github.com/philbarker/schemaorg-1/tree/feature/ext-course/data/ext/course
For more about "pending" (a new development) see http://webschemas.org/docs/howwework.html#pending
I've updated the version in pending so that grantsCredential does not reference a non-existent "Credential" type (and we have updated our unit tests to run against the extension schemas so bugs like that won't slip past in future). However I would encourage use of other terms here, as talk of granting credentials may sound like a crypto protocol to non-educationalists.
Why not add Intangible > Credential CreativeWork > Credential Credential > Certificate > Diploma ?
There is a need for a base Credential type in schemed, as well: https://github.com/twamarc/ScheMed/issues/34#issuecomment-213594529
At a later time, it may make perfectly good sense to add as subclasses of Credential:
On Friday, May 20, 2016, Dan Brickley <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:
I've updated the version in pending so that grantsCredential does not reference a non-existent "Credential" type (and we have updated our unit tests to run against the extension schemas so bugs like that won't slip past in future). However I would encourage use of other terms here, as talk of granting credentials may sound like a crypto protocol to non-educationalists.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-220588244
To focus more on modeling Offers for Services and a Product, IDK how to do:
On Friday, May 20, 2016, Wes Turner wes.turner@gmail.com wrote:
Why not add Intangible > Credential CreativeWork > Credential Credential > Certificate > Diploma ?
There is a need for a base Credential type in schemed, as well: https://github.com/twamarc/ScheMed/issues/34#issuecomment-213594529
At a later time, it may make perfectly good sense to add as subclasses of Credential:
- ...
- SSLCertificate
- GPGKey
- SSHKey
- WebID
- ...
On Friday, May 20, 2016, Dan Brickley notifications@github.com wrote:
I've updated the version in pending so that grantsCredential does not reference a non-existent "Credential" type (and we have updated our unit tests to run against the extension schemas so bugs like that won't slip past in future). However I would encourage use of other terms here, as talk of granting credentials may sound like a crypto protocol to non-educationalists.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-220588244
I don't see SSLCertificate, GPGKey etc and Degree, Diploma having a lot in common. I have a degree from the University of Bristol, and numerous SSLCertificates from various sources, but they do not have much in common. Let's please not mix anything crypto-related casually into other topics. I don't often express strong opinions on schema design here but on this issue I'm pretty sure we would quickly come to regret such an entangling of issues.
+1
However the raising of this highlights the need to choose term names with care to avoid future confusion and wrong assumptions.
~Richard
On 21 May 2016, at 08:15, Dan Brickley notifications@github.com wrote:
I don't see SSLCertificate, GPGKey etc and Degree, Diploma having a lot in common. I have a degree from the University of Bristol, and numerous SSLCertificates from various sources, but they do not have much in common. Let's please not mix anything crypto-related casually into other topics. I don't often express strong opinions on schema design here but on this issue I'm pretty sure we would quickly come to regret such an entangling of issues.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub
Yes, please, I am with Dan in regards to not doing this kind of mixing/polluting. There is a huge, loosely related set of global verticals made up of for-profit and non-profit credentialing organizations with products as well as millions of people who have earned credentials publicly denoting success in some endeavor.
There is work well underway on development RDF-based, rich description of credentials of these more formal sorts [1]-[2] as well as W3C work on credentials and verifiable claims regarding them [3]-[4]. Let's do keep these more formal (and widely) used notion of credential distinct from "anything crypto-related". There are hopes within CTI that a light-weight version of the work at [1]-[2] will form the basis for a Credential type within schema.org.
Stuart
[1] http://www.credentialtransparencyinitiative.org/ [2] http://www.credreg.net/ [3] https://www.w3.org/community/credentials/ [4] https://www.w3.org/Payments/IG/wiki/Main_Page/ProposalsQ42015/VerifiableClaimsTaskForce
On Sat, May 21, 2016 at 12:15 AM, Dan Brickley notifications@github.com wrote:
I don't see SSLCertificate, GPGKey etc and Degree, Diploma having a lot in common. I have a degree from the University of Bristol, and numerous SSLCertificates from various sources, but they do not have much in common. Let's please not mix anything crypto-related casually into other topics. I don't often express strong opinions on schema design here but on this issue I'm pretty sure we would quickly come to regret such an entangling of issues.
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-220763288
@danbri
I don't see SSLCertificate, GPGKey etc and Degree, Diploma having a lot in common.
These are all types of credentials.
At this time, we have no Creative-Commons schema.org way to define Credential > {Certificate, Degree}.
Use Cases ( @philbarker ) :
...
(Out of scope, but still logically deriving from a base Credential class):
I believe a preliminarily defined Credential > Degree is in scope for this effort in order to define a rdfs:range
of grantsCredential
.
Blocking objectives for Schema.org Course Extension
...
@stuartasutton
Credential [...] Questions for researching potential/ideal implementations of schema.org/Credential and e.g. schema.org/Degree:
- Are you open to Creative Commons as a license [hard schema.org requirement]?
- Are you open / friendly to other application implementations?
- Is the/your application open source? (link to source: ____; early and often)
- Do you [already] solve for DegreeProgram?
(DegreeProgram will/would require conditionals)
On Sat, May 21, 2016 at 5:54 AM, Wes Turner notifications@github.com wrote:
I believe a preliminarily defined Credential > Degree is in scope for this effort in order to define a rdfs:range of grantsCredential.
I believe the rdfs:range (schema:rangeIncludes) of grantsCredential should remain Credential. Degree is one subclass of Credential that could be applicable in the context of an instance of Course; but, not the only one. See https://github.com/CredentialTransparencyInitiative/vocabularies/blob/master/credentialType.ttl. A number of these subclasses could be applicable to Course.
@stuartasutton https://github.com/stuartasutton
If you mean by "you" the CTI initiative (which is not me), the following responses hold:
Credential [...] Questions for researching potential/ideal implementations of schema.org/Credential and e.g. schema.org/Degree:
- Are you open to Creative Commons as a license [hard schema.org requirement]?
Creative Commons licensing is not a "hard requirement". The CTI specifications under development will all have open licenses (e.g., https://creativecommons.org/licenses/by/4.0/).
- Are you open / friendly to other application implementations?
Absolutely. There are a number of 3rd party implementers advising the CTI work because they know that that work is open from the start and is intended to spur a marketplace of applications. While CTI, under its grant funding, is developing a Credential Registry (also to be openly licensed) and a set of applications for interacting with it (also open), there are no illusions that it will be the only credential registry or the only set of applications developed that will act on data based on the Credential Transparency Description Language (CTDL). So, it is very open to the developer community as part of its strategy for long-term sustainability.
- Is the/your application open source? (link to source: ____; early and often)
Not yet. But it will be (on GitHub) when there is something to put in front of people. The applications and the Credential Registry are in early stages of development. It's too early to know whether CTI will maintain an actual open source community (not easy to do); but, it is not too early to know that the code base for the apps CTI is developing under its grant funding will be openly available through GitHub.
- Do you [already] solve for DegreeProgram?
(DegreeProgram will/would require conditionals)
If you mean that an instance of Credential (or one of its subclasses) stems from a degree program (obviously, not all do), then the conditions for granting the degree are within scope.
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-220776363
IIUC, CC-By-SA [3.0,] is a hard (viral) requirement for schema.org and contributions From https://schema.org/docs/terms.html :
Scope of Terms of Services; License These Terms of Service govern your use of the Website, which contains a schema specifying a vocabulary you can use. The Sponsors' copyrights in the schema are licensed to website publishers and other third parties under the Creative Commons Attribution-ShareAlike License (version 3.0). To view a copy of this license, please visit http://creativecommons.org/licenses/by-sa/3.0/. The Sponsors have applied the W3C Patent Policy to the schemas published by Schema.org as follows: each Sponsor, by itself and on behalf of its affiliates, agrees to make available under W3C RF licensing requirements its Essential Claims (if any) in the schemas published by Schema.org as if the schemas were W3C Recommendations. In some cases, this website may indicate that some but not all of the Sponsors have recognized a particular extension to the Schema; in those cases, as to that extension, the above rights are granted by only those recognizing Sponsors.
From https://wiki.creativecommons.org/wiki/4.0_upgrade_guidelines :
Existing content:
- Who owns the rights?
- If the publisher, then can relicense under 4.0 as specified above.
- If the contributors, then need permission to relicense. Without permission (via terms of use or otherwise), then that content remains under prior version. [If this is the case, see the section below about dealing with mixed-version content.]
- A couple of options for obtaining permission to relicense:
- upon upload by contributors, have a prompt box to obtain agreement to relicense previous uploads;
- general outreach to contributors seeking agreement to upgrade. [Note that this is easier to do with discrete artifacts (an article, a photo) as opposed to other contributions such as comments on wikis and similar, where one person's contribution is intermixed with others.]
I believe the rdfs:range (schema:rangeIncludes) of grantsCredential should remain Credential. Degree is one subclass of Credential that could be applicable in the context of an instance of Course; but, not the only one.
@danbri
Is this the file I should be appending to now? (IDK how to maintain the revision log when git mv
'ing files around in a git repository):
https://github.com/schemaorg/schemaorg/blob/sdo-deimos/data/ext/pending/issue-195.rdfa#L120
(was: https://github.com/schemaorg/schemaorg/pull/972/commits )
I've updated the version in pending so that grantsCredential does not reference a non-existent "Credential" type
Where is this change?
<!-- TODO: define Credential > [Certificate, ] -->
part
except actually it's now {Intangible || CreativeWork?} > Credential > {Certificate, Degree}(IDK how to maintain the revision log when git mv'ing files around in a git repository)
If you include either a complete URL to a revision when copy-pasting OR just a shortrev, GitHub will include the link in the commit message (in order to maintain traceability between PR branches, commits, etc)
Two ways to print the shortrev (to keep commit messages usable and minimal):
git log --abbrev-commit
git rev-parse --short HEAD
https://github.com/schemaorg/schemaorg/commit/62086c8d6658e7e7ebed8993930ad1ba8ea2b4df
62086c8
(first 7 characters) So GitHub would linkify a commit message like:
Added a first snapshot of the ongoing courses work. (from 62086c8 )
Edit:
... Because now IDK which of these PR commits need to be merged over
Personally I am quite happy with the term name Credential. It doesn't immediately suggest anything crypto to me (I think the wikipedia article gets the coverage about right[1])
I also think that any meaningful alternative I can think of has similar problems. The best I can think of is grantsAward -- is anyone happier with that?
I also don't think that the course extension work is a good place to try to pin down a controlled vocabulary of all the possible Awards.
Minimally, should this initial Credential RDFS class be derivative of Intangible or of CreativeWork?:
Are there any base properties which are specific to Credential? I would think that there would then, eventually, from a different schema.org extension group, be a CryptographicCredential (where x.509 attributes may cover for most other formats: https://en.wikipedia.org/wiki/X.509#Structure_of_a_certificate (though, again, this is not yet in scope for academic credentialing, pending the recommendations of the CTI and credreg))
Brainstorming eventual Credential types:
Excited to see some work on this. Came over from https://github.com/openbadges/openbadges-specification/issues/9 as I was doing a little pruning.
Would be worth paying attention to the VCTF discussion of denoting their class proposal as "WebCredential" or "DigitalCredential" to make it more specific and differentiate from more general approaches to "Credential", like schema.org is likely to take.
I'd probably lean toward grouping Credential under CreativeWork.
@stuartasutton may know more on proposed types for credentials. The CTI meeting from a week ago previewed the first snippet of a list of proposed types, but I wasn't able to find the list on GitHub as was hinted.
@ottonomy, my sense of this is that schema.org/Credential is correct since it aligns with the CTI definition as the CreativeWork that describes the thing created by a credentialing entity (of any sort) with the intention that it be awarded. The VCTF context uses the (class name still under consideration) "TBD Credential" as a verifiable set of claims. A somewhat subtle but very significant difference.
CTI has a (unstable) set of subclasses for Credential as well as an (equally unstable) enumeration of credential types of concern to CTI at https://github.com/CredentialTransparencyInitiative/vocabularies/blob/master/credentialType.ttl
+1 for Credential as CreativeWork.
https://github.com/CredentialTransparencyInitiative/vocabularies/blob/master/credentialType.ttl
Thanks! Looking forward to learning more here. It would be great if we could get this together for Universities to catalog and implement (probably with spreadsheets) by this fall.
Thing > CreativeWork > Credential > Degree > BachelorDegree
.
Does there need to be another layer here between Credential [... > ...] Degree ?
Because:
Aside, http://blockchain.open.ac.uk/ is worth keeping an eye on.
Aside, http://blockchain.open.ac.uk/ is worth keeping an eye on.
- https://Keybase.io/ stores signatures in at least one blockchain; as well as centrally.
- https://keybase.io/docs/server_security/merkle_root_in_bitcoin_blockchain
From https://en.wikipedia.org/wiki/Merkle_tree (oldid=720708959) :
Suggestions have been made to use hash trees in trusted computing systems.[4] Hash trees are used in the IPFS and ZFS file systems,[5] BitTorrent protocol, Apache Wave protocol,[6] Git distributed revision control system, the Tahoe-LAFS backup system, the Bitcoin peer-to-peer network, the Ethereum peer-to-peer network,[7] the Certificate Transparency framework, and a number of NoSQL systems like Apache Cassandra and Riak
@westurner "Are there other systems of academic credentials?"
Yes, there are.See https://en.wikipedia.org/wiki/National_Qualifications_Framework#England.2C_Wales_and_Northern_Ireland for a list of Baccs, Certs, BTECs, Diplomas, Awards, PGCerts etc. in England, Wales and Northern Ireland (Scotland is different)
There is also the whole world of industry awards, e.g. CISCO/Microsoft Certifications but not limited to IT.
Phil
yes, it would be unfortunate if we could only express academic but not vocational qualifications. Also driving licences (for trucking etc.), acting and other fields this can be seen in terms of organisational membership (eg http://www.equity.org.uk/about-us/join-us/how-can-i-join/ http://fia-actors.com/no_cache/about-fia/fia-members/ ). see also https://pending.schema.org/WorkersUnion but also other professional membership structures. On 30 May 2016 1:28 am, "Phil Barker" notifications@github.com wrote:
@westurner https://github.com/westurner "Are there other systems of academic credentials?"
Yes, there are.See https://en.wikipedia.org/wiki/National_Qualifications_Framework#England.2C_Wales_and_Northern_Ireland for a list of Baccs, Certs, BTECs, Diplomas, Awards, PGCerts etc. in England, Wales and Northern Ireland (Scotland is different)
There is also the whole world of industry awards, e.g. CISCO/Microsoft Certifications but not limited to IT.
Phil
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-222440576, or mute the thread https://github.com/notifications/unsubscribe/AAKZGRrNYI3NjxuXM8E6s_j6Iq4WkCynks5qGp-0gaJpZM4DHZMZ .
re credentials, take a look at https://www.google.com/trends/explore#q=credentials
related searches (at google):
windows credentials
user credentials
login credentials
network credentials
invalid credentials
credential
what is credentials
On Thursday, June 2, 2016, Dan Brickley notifications@github.com wrote:
re credentials, take a look at https://www.google.com/trends/explore#q=credentials
There are different results for the @en singular form ("credentials" / "credential") https://www.google.com/trends/explore#q=credential
Minimally, C: CreativeWork > Credential
C: CreativeWork > Credential > CredentialInstance
Or, P: CredentialInstance.credential R: Credential
Are there more appropriate terms than issuer/issuee?
And/Or, P: issuerCredential R: Credential D: {Credential, CredentialInstance}
On Friday, June 3, 2016, Wes Turner wes.turner@gmail.com wrote:
On Thursday, June 2, 2016, Dan Brickley <notifications@github.com javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:
re credentials, take a look at https://www.google.com/trends/explore#q=credentials
There are different results for the @en singular form ("credentials" / "credential") https://www.google.com/trends/explore#q=credential
Minimally, C: CreativeWork > Credential
- P: issuer R: Person/Organization
C: CreativeWork > Credential > CredentialInstance
- P: issuer R: Person/Organization
- P: issuee R: Person/Organization
Or, P: CredentialInstance.credential R: Credential
Are there more appropriate terms than issuer/issuee?
How about issue as a more specific "CreateAction" ?
@danbri and @philbarker, Is this discussion of defining a schema.org Credential best placed here under an issue focused on Course? There are many who have vested interests in how schema.org might ultimately handle a definition of Credential who aren't necessarily watching Course issues.
On Friday, June 3, 2016, Stuart Sutton notifications@github.com wrote:
@danbri https://github.com/danbri and @philbarker https://github.com/philbarker, Is this discussion of defining a schema.org Credential best placed here under an issue focused on Course? There are many who have vested interests in how schema.org might ultimately handle a definition of Credential who aren't necessarily watching Course issues.
Degree, Certificate, and Diploma are all blocked on a Credential base class.
Thing > CreativeWork > Credential > Degree Thing > CreativeWork > Credential > Diploma Thing > CreativeWork > Credential > CredentialInstance > Certificate > Diploma Thing > CreativeWork > Credential > Certification
There are many potential implementations of DigitalCredential / CryptoCredential / _Credential. When those rdfs:classes are defined in terms of schema.org RDFS, it should be possible to describe types of Credentials and CredentialInstances through subclassing and/or composition.
Can we agree to work with 'issuer' and 'issuee' with domains of {Credential, CredentialInstance}?
Degree [> BachelorDegree]
So that a record can be signed, eventually there must be a way to do:
Diploma (or "DegreeInstance", or {Degree, CredentialInstance})
Again, OpenBadges JWS works today and KeyBase.io proofs work today.
—
You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-223601464, or mute the thread https://github.com/notifications/unsubscribe/AADGywrjWwCSqMy96B4uUZdi9xTx4ZRRks5qIEBBgaJpZM4DHZMZ .
On Friday, June 3, 2016, Guangyuan Piao notifications@github.com wrote:
How about issue as a more specific "CreateAction" https://schema.org/CreateAction?
Maybe ConferAction?
Action > CreateAction > ConferAction
ConferAction
DegreeInstance (or {Degree, CredentialInstance}) credX
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-223567680, or mute the thread https://github.com/notifications/unsubscribe/AADGy6c5jPE2U8C-HwNLZeHH4h-COkQcks5qICA7gaJpZM4DHZMZ .
The CTI project is uses subclasses of schema.org/Action with key actions between agents (People/Organizations) and credentials and other agents--chiefly in the context of quality assurance; e.g.,
AccreditAction ApproveAction ConferAction EndorseAction RecognizeAction RenewAction RevokeAction
CTI is deliberately focused on description of Credential as a work (CreativeWork) and not on the credential awarded (or on related transactions on such awarded artifacts (verifiable claims etc.)).
On Fri, Jun 3, 2016 at 12:22 PM, Wes Turner notifications@github.com wrote:
On Friday, June 3, 2016, Guangyuan Piao notifications@github.com wrote:
How about issue as a more specific "CreateAction" https://schema.org/CreateAction?
Maybe ConferAction?
Action > CreateAction > ConferAction
ConferAction
- agent: Organization orgX (CredentialInstance orgX.credential[n]
- result: CredentialInstance credX
- participant: Person personX
- startTime: DateTime iso8601datetimeX
DegreeInstance (or {Degree, CredentialInstance}) credX
- dateCreated: DateTime iso8601datetimeX
- issuee: Person personX
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/schemaorg/schemaorg/issues/195#issuecomment-223567680>, or mute the thread < https://github.com/notifications/unsubscribe/AADGy6c5jPE2U8C-HwNLZeHH4h-COkQcks5qICA7gaJpZM4DHZMZ
.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/schemaorg/schemaorg/issues/195#issuecomment-223670047, or mute the thread https://github.com/notifications/unsubscribe/ACzYpo4cGm6GYIaCPqLONpaUK43EYY_Nks5qIH7egaJpZM4DHZMZ .
Hi everyone. This is Jeanne with the Credential Transparency Initiative (CTI). We've been following the progress with Course schema. In regards to the recent comments here on "Credential", the CTI defines this as, "A qualification or achievement of an agent." As an additional comment, for CTI, only credentials issued to people, and credentials for quality issued to organizations for related programs, courses, tasks and/or assessments are in scope. As Stuart noted, CTI metadata modeling takes into account the work of Schema.org. The editor's draft classes, properties, and enumerations and other information is available from the CTI tech planning site http://credreg.net.
CTI is deliberately focused on description of Credential as a work (CreativeWork) and not on the credential awarded (or on related transactions on such awarded artifacts (verifiable claims etc.)).
- “What we learned from designing an academic certificates system on the blockchain” @medialab https://medium.com/mit-media-lab/what-we-learned-from-designing-an-academic-certificates-system-on-the-blockchain-34ba5874f196
- “Verifiable Credentials on the Blockchain” @chrisjagers https://medium.com/learning-machine-blog/blockchain-credentials-b4cf5d02bbb7
- http://certificates.media.mit.edu
- https://github.com/digital-certificates/cert-schema "Cert-schema: Cert-schema details how to make a digital certificate. A digital certificate is essentially a JSON file with the necessary fields needed for our cert-issuer code to place it on the blockchain. We tried to keep the schema as close to the Mozilla Open Badges specifications as possible."
... In terms of set logic (preferably as one or more Venn diagrams, if possible and you have the time), how can we support multiple Credentials?
.
Goals:
Products:
data/ext/course/course.rdfa
-- Course extension RDFadata/ext/course/course-course-examples.txt
-- course extension examplesmake test
andmake build
Examples:
Discussion Mailing List Threads:
http://lists.w3.org/Archives/Public/public-vocabs/2014Oct/0052.html
"[Proposal] schema:OnlineCourse"
Use Cases / Potential Implementors (Culled from the Mailing List):
Release notes: