Trustmark - Revision history

Tomjones: /* Context */

2018-11-12T02:40:42Z

Context

← Older revision		Revision as of 02:40, 12 November 2018
Line 13:		Line 13:
	#The user can stipulate their own conditions on which they are willing to interoperate with the site.		#The user can stipulate their own conditions on which they are willing to interoperate with the site.

	===The Value Proposition ~~for~~ the ~~Parties~~===		===The Value Proposition of the [[Trustmark]]===
	# Users can understand the meaning of the message about the risk to their privacy.		# Users can understand the meaning of the message about the risk to their privacy.
	# Users can understand the commitment that the web site has made to security.		# Users can understand the commitment that the web site has made to security.

Tomjones: /* Context */

2018-11-12T02:38:48Z

Context

← Older revision		Revision as of 02:38, 12 November 2018
Line 12:		Line 12:
	#The user can clearly determine the purpose of the web site, especially in regard to the intent of the site to use their personal information.		#The user can clearly determine the purpose of the web site, especially in regard to the intent of the site to use their personal information.
	#The user can stipulate their own conditions on which they are willing to interoperate with the site.		#The user can stipulate their own conditions on which they are willing to interoperate with the site.

			===The Value Proposition for the Parties===
			# Users can understand the meaning of the message about the risk to their privacy.
			# Users can understand the commitment that the web site has made to security.
			# Enterprise partners can know the depth of the commitment each has made to risk reduction.
			# The value of the federation is to provide some metric as to the depth of that commitment.

	==Problems==		==Problems==

Tomjones: /* References and Coordination */

2018-11-08T20:16:50Z

References and Coordination

← Older revision		Revision as of 20:16, 8 November 2018
Line 41:		Line 41:
	==References and Coordination==		==References and Coordination==
	*Much more detail is on the page [[Trustmark Evolving Design Pattern]], which may not be fully up-to-date.		*Much more detail is on the page [[Trustmark Evolving Design Pattern]], which may not be fully up-to-date.
	*[https://tcwiki.azurewebsites.net/index.php?title=Trust ~~This~~ wiki page] is dedicated to collecting information about Trust in a digital environment.		*[https://tcwiki.azurewebsites.net/index.php?title=Trust The Trust wiki page] is dedicated to collecting information about Trust in a digital environment.
	*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].		*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].
	*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trusted ID for docs.] This depends on the publisher's URL (which I understand the Google Chrome browser is moving away from) and an ID for a [[Web Site]].		*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trusted ID for docs.] This depends on the publisher's URL (which I understand the Google Chrome browser is moving away from) and an ID for a [[Web Site]].

Tomjones: /* Possible implementation details */

2018-11-07T18:46:43Z

Possible implementation details

← Older revision		Revision as of 18:46, 7 November 2018
Line 31:		Line 31:
	===Possible implementation details===		===Possible implementation details===
	*The [[Trustmark]] will be included in an <img> element with a tag (perhaps a new HTML property or method) that can be recognized by the browser as indicative of a [[Trustmark]].		*The [[Trustmark]] will be included in an <img> element with a tag (perhaps a new HTML property or method) that can be recognized by the browser as indicative of a [[Trustmark]].
	*At competition of page load browsers will ~~check~~ for the tag so that they can run a check on the cryptographic binding of the mark.		*At competition of page load browsers will have a method for the tag so that they can run a check on the cryptographic binding of the mark.
	*If the check fails two events will occur, the header of the browser will flag the site as unsafe, a message will be sent by the browser to any user authorized malware checker.		*If the check fails two events will occur, the header of the browser will flag the site as unsafe, a message will be sent by the browser to any user authorized malware checker.
	*A new schema is developed for trusted web site [[Identifier]]s, e.g. tid:// (if it is a URI) or just tid: (if it is a URN) similar to the did: (which is a URN).		*A new schema is developed for trusted web site [[Identifier]]s, e.g. tid:// (if it is a URI) or just tid: (if it is a URN) similar to the did: (which is a URN).

Tomjones: /* Possible implementation details */

2018-11-07T18:45:13Z

Possible implementation details

← Older revision		Revision as of 18:45, 7 November 2018
Line 30:		Line 30:

	===Possible implementation details===		===Possible implementation details===
	*The [[Trustmark]] will be included in an <img> element with a tag that can be recognized by the browser as indicative of a [[Trustmark]].		*The [[Trustmark]] will be included in an <img> element with a tag (perhaps a new HTML property or method) that can be recognized by the browser as indicative of a [[Trustmark]].
	*At competition of page load browsers will check for the tag so that they can run a check on the cryptographic binding of the mark.		*At competition of page load browsers will check for the tag so that they can run a check on the cryptographic binding of the mark.
	*If the check fails two events will occur, the header of the browser will flag the site as unsafe, a message will be sent by the browser to any user authorized malware checker.		*If the check fails two events will occur, the header of the browser will flag the site as unsafe, a message will be sent by the browser to any user authorized malware checker.

Tomjones: /* References and Coordination */

2018-11-07T17:08:43Z

References and Coordination

← Older revision		Revision as of 17:08, 7 November 2018
Line 43:		Line 43:
	*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.		*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.
	*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].		*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].
	*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a ~~trust~~ ID for docs.] This depends on the publisher's URL (which I understand the Google Chrome browser is moving away from) and an ID for a [[Web Site]].		*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trusted ID for docs.] This depends on the publisher's URL (which I understand the Google Chrome browser is moving away from) and an ID for a [[Web Site]].
	*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.		*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.
	*[https://trustmark.gtri.gatech.edu/operational-pilot/ GTRI NSTIC Trustmark Pilot] - funded by NIST		*[https://trustmark.gtri.gatech.edu/operational-pilot/ GTRI NSTIC Trustmark Pilot] - funded by NIST

Tomjones: /* References and Coordination */

2018-11-07T17:07:59Z

References and Coordination

← Older revision		Revision as of 17:07, 7 November 2018
Line 43:		Line 43:
	*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.		*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.
	*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].		*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].
	*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trust ID for docs.] This depends on the publisher's URL (which I understand Google is moving away from) and an ID for a [[Web Site]].		*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trust ID for docs.] This depends on the publisher's URL (which I understand the Google Chrome browser is moving away from) and an ID for a [[Web Site]].
	*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.		*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.
	*[https://trustmark.gtri.gatech.edu/operational-pilot/ GTRI NSTIC Trustmark Pilot] - funded by NIST		*[https://trustmark.gtri.gatech.edu/operational-pilot/ GTRI NSTIC Trustmark Pilot] - funded by NIST

Tomjones: /* References and Coordination */

2018-11-07T17:07:26Z

References and Coordination

← Older revision		Revision as of 17:07, 7 November 2018
Line 43:		Line 43:
	*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.		*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.
	*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].		*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].
	*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trust ID for docs.] This depends on the publisher's URL )which I understand Google is moving away from) and an ID for a [[Web Site]].		*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trust ID for docs.] This depends on the publisher's URL (which I understand Google is moving away from) and an ID for a [[Web Site]].
	*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.		*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.
	*[https://trustmark.gtri.gatech.edu/operational-pilot/ GTRI NSTIC Trustmark Pilot] - funded by NIST		*[https://trustmark.gtri.gatech.edu/operational-pilot/ GTRI NSTIC Trustmark Pilot] - funded by NIST

Tomjones: /* References and Coordination */

2018-11-07T17:07:09Z

References and Coordination

← Older revision		Revision as of 17:07, 7 November 2018
Line 43:		Line 43:
	*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.		*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.
	*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].		*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].
	*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trust ID for docs.] This depends on the publisher's URL which I understand Google is moving away from and an ID for a [[Web Site]].		*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trust ID for docs.] This depends on the publisher's URL )which I understand Google is moving away from) and an ID for a [[Web Site]].
	*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.		*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.
	*[https://trustmark.gtri.gatech.edu/operational-pilot/ GTRI NSTIC Trustmark Pilot] - funded by NIST		*[https://trustmark.gtri.gatech.edu/operational-pilot/ GTRI NSTIC Trustmark Pilot] - funded by NIST

Tomjones: /* References and Coordination */

2018-11-07T17:05:48Z

References and Coordination

← Older revision		Revision as of 17:05, 7 November 2018
Line 42:		Line 42:
	*Much more detail is on the page [[Trustmark Evolving Design Pattern]], which may not be fully up-to-date.		*Much more detail is on the page [[Trustmark Evolving Design Pattern]], which may not be fully up-to-date.
	*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.		*[https://tcwiki.azurewebsites.net/index.php?title=Trust This wiki page] is dedicated to collecting information about Trust in a digital environment.
	*[[Identifier]]s are considered to be unique ~~with in~~ their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].		*[[Identifier]]s are considered to be unique within their name domain and only apply to a digital [[Entity]]. Real-world names may be listed as [[Attribute]]s of a digital [[Entity]].
	*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trust ID for docs.] This depends on the publisher's URL which I understand Google is moving away from and an ID for a [[Web Site]].		*[https://developers.google.com/web/updates/2018/11/signed-exchanges Google now has a trust ID for docs.] This depends on the publisher's URL which I understand Google is moving away from and an ID for a [[Web Site]].
	*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.		*Georgia Tech published a [https://trustmarkinitiative.org/specifications/trustmark-framework/1.2/tfts-1.2.pdf Trustmark Framework Technical Specification] (2017-11-06) that is focused on XML, but the fields are still helpful.