Reserved elements for AI#344
Conversation
Incorporation of AI metrics into section 11.4, and of syndication namespacing into section 11.1
berndoberknapp
left a comment
berndoberknapp
left a comment
There was a problem hiding this comment.
Syndication and AI are separate topics, please create separate pull requests and issues.
Putting the information about syndicated usage in the "Platform as a Namespace" section seems wrong to me, since it is not related to this topic. Additionally this is not an extensions, which would have to be requested explicitly, instead report providers that report syndicated usage include it in the COUNTER Reports by default.
If you just want to include the rule that syndicated usage must be reported with the namespace, I would suggest to include that in the definition of the Platform element in Table 3.h. If you would like to provide more information, especially that both the syndication platform and publisher platform must be audited for COUNTER compliance, I would suggest to add a subsection to Section 10.
They are and they aren't: a lot of the work for phase two of AI ties back to syndication. Hence bundling them in this PR. However, if you want me to split them out, does that mean I should revert this PR and re-do the changes in two separate ones? |
|
While syndication might be used for AI usage, it is a more general concept, and as I mentioned it is not related to "platform as a namespace". I would suggest to create separate issues for the AI extension and for syndication. You could either close this PR and create two new ones, or create a new PR with the syndication paragraph added to the Platform definition in Table 3.h (unless you want to explain this concept in more detail), and remove that part from this PR and rename this PR. |
removed reference to syndication
|
I just noticed that the reserved values probably should be a separate section - we have 11.2 for creating custom report, 11.3 for creating custom eelements, 11.4 for creating custom values, and 11.5 for the reserved custom elements. The reserved custom value therefore probably should be in Section 11.6 (which would move the existing 11.6 to 11.7, and the new section about the API extensions to 11.8)? The alternative would be to move 11.5 into a subsection of 11.3, but I would prefer a separate section. |
Split information about reserved values from custom values. Necessitated relabelling reserved elements as such, and renumbering 11.7
|
|
||
| * - Metric_Type | ||
| - Total_AI_Investigations | ||
| - Total number of times within a user session that a chunk from an Item or information related to an Item was included by an AI system in generating a response to a user prompt. |
There was a problem hiding this comment.
I still find the "with a user session" for the Total metrics and the Search metric confusing, since the session is only relevant for Unique metrics. The double click filtering does apply, but that information is missing.
There was a problem hiding this comment.
Changing this will require going back to the AI working group. Since they are working on phase two of the project now, my recommendation is to hold this PR for a subsequent R5.1.2.
|
|
||
| * - Metric_Type | ||
| - Total_AI_Requests | ||
| - Total number of times within a user session that a chunk from an Item was requested (i.e. the full text or content was accessible to the AI system) in generating a response to a user prompt, during a user session. |
There was a problem hiding this comment.
"accessible to" or "accessed by"? Same question for Unique_AI_Requests.
There was a problem hiding this comment.
Changing this will require going back to the AI working group. Since they are working on phase two of the project now, my recommendation is to hold this PR for a subsequent R5.1.2.
Addressed requirement for Reports column Clarifications in first para
2 participants
Incorporation of AI metrics into section 11.4, and of syndication namespacing into section 11.1