Update: The Output of Project Tin Can is Experience API.
Activity Definition Agreement
How do we make sure that an activity isn’t referred to twice in two different ways? How do we make sure that two different activities aren’t referred to in the same way?
These are questions that have to be asked when we talk about activities as parts of statements.
Ideally, organizations would take control of the naming schemes. Domain names could be used to signify that a statement originated from a source, and statements might have to get more complex in order to make sure that they are as accurate as possible.
URLs and URIs can be used to signify who really owns a resource and where it came from, but then whoever controls the domain used in a URL would have to make sure to take charge of not having duplicate names for different resources.
What are your thoughts on activity definition agreement? Do you have any suggestions? Leave your comments and suggestions below.
|<- Previous||Next ->|
|Security/privacy complexity||Verb variation|