Skip to content

Commit 41f38bd

Browse files
Joseph ShookJoseph Shook
authored andcommitted
Update README.md
1 parent 5a4309e commit 41f38bd

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This is a Microsoft .NET Core reference implementation library for Expressing Co
1111

1212
### Design of Context
1313

14-
The Context library uses the excellent [MimeKit](https://github.com/jstedfast/MimeKit) library as the base for creating and parsing mime messages. The Direct Project libraries are primarily parsers and not builders. The current implementation is targeted for [Direct Context]((https://wiki.directproject.org/Implementation_Guide_for_Expressing_Context_in_Direct_Messaging)) version 1.1 compliance and recent ADT Notification requirements. If you find any issues, please create and issue and/or email me directly. I created this project in 2017 when I was very intimate with the details. Recently I revisited this project to bring it from 1.0 to 1.1 with respect to the [Direct Context Guide]((https://wiki.directproject.org/Implementation_Guide_for_Expressing_Context_in_Direct_Messaging)), in addition making it compatible with [ADT Notifications](https://directtrust.org/standards/event-notifications-via-direct).
14+
The Context library uses the excellent [MimeKit](https://github.com/jstedfast/MimeKit) library as the base for creating and parsing mime messages. The current implementation is targeted for [Direct Context]((https://wiki.directproject.org/Implementation_Guide_for_Expressing_Context_in_Direct_Messaging)) version 1.1 compliance and recent ADT Notification requirements. If you find any issues, please create and issue and/or email me directly. I created this project in 2017 when I was very intimate with the details. Recently I revisited this project to bring it from 1.0 to 1.1 with respect to the [Direct Context Guide]((https://wiki.directproject.org/Implementation_Guide_for_Expressing_Context_in_Direct_Messaging)), in addition making it compatible with [ADT Notifications](https://directtrust.org/standards/event-notifications-via-direct).
1515

1616
Originally [Direct Context](https://wiki.directproject.org/Implementation_Guide_for_Expressing_Context_in_Direct_Messaging) was intended to evolve as various versions bound to a specification version. For example, an application hosting multiple versions of the parser would decide which parser to load based on the version header value in the Context part. To this point I don't believe any context other than 1.1 has ever been put into production. ADT Notifications violate the code version binding to a Direct Context specification. I imagine the spec will catch up at some point. My hope is the concept of DirectContext could make way for completely different contexts, that allow for other interesting workflows. Senders and receivers would need to understand the two contexts, but they could be anything such as carrying patient consent requests and answers. In such a workflow we would just create a new DirectContext but the version would be something completely different such as pc-1.0 which would load the appropriate context object and leading to specific workflow actions.
1717

0 commit comments

Comments
 (0)