diff --git a/inbox/xep-ai.xml b/inbox/xep-ai.xml new file mode 100644 index 00000000..7196baa8 --- /dev/null +++ b/inbox/xep-ai.xml @@ -0,0 +1,273 @@ + + + +%ents; +]> + + +
+ Communicate & Ask to AI + This document defines a protocol for asking questions to an artificial intelligence or requesting it to make predictions. + &LEGALNOTICE; + xxxx + ProtoXEP + Standards Track + Standards + Council + + XMPP Core + XEP-0001 + Etc. + + + + NOT_YET_ASSIGNED + + template + + + Abdurrahman + Eker + abdurrahman.eker@detaysoft.com + abdurrahman.eker@detaysoft.com + + + 0.0.1 + 2023-03-13 + ae +

First draft.

 + +
+ +

Using artificial intelligence can be useful for quickly finding documentation or for classification operations that would take a human a long time. This feature enables asking questions to an artificial intelligence and getting guidance from it. It allows fine-tuning the usage limits of the artificial intelligence, making detailed adjustments, and making custom settings for the user.

+ + +

When a question is asked to an artificial intelligence, it SHOULD:

+
    +
  1. Be able to be asked questions and analyze them simultaneously.
    2. +
  2. Detect parameters and work with the relevant artificial intelligence engine.
    3. +
  3. Review the limits and permissions of the requester and provide a rejection response if they are not sufficient.
    4. +
+ + +

If the client is implementing artificial intelligence messages, it MUST provide the 'urn:xmpp:ai:0' feature in the features section as specified in &xep0030; and &xep0115;.

+ + + +]]> + + +… + +… + + +]]> + + + +

To ask a question to an artificial intelligence, the message package SHOULD be used. This way, the conversation with the artificial intelligence can be recorded and viewed in the message history. The <ai> element MUST be present in the message package, MUST be qualified with the 'urn:xmpp:ai:0' domain, and the model attribute value MUST be entered.

+ + Is love a tender thing? + + +]]> + + + Yes, love can be a tender thing. Love is a complex and multi-faceted emotion that can + manifest in many different ways, but at its core, it often involves a deep feeling of + affection, care, and tenderness towards another person. + + + +]]> + + +

If an AI model needs to be supported with specific parameters, &xep0004; can be used. It should be defined within the <message> element with the 'jabber:x:data' namespace.

+ + Is love a tender thing? + + + + urn:xmpp:ai:0 + + + 10 + + + +]]> + + Yes, love can be a tender thing. + + + + urn:xmpp:ai:0 + + + 10 + + + +]]> + + +

The desired speech must be sent to the artificial intelligence to estimate the next message. To predict the next message, the past conversation MUST be sent to the AI using the <suggest> element inside the <ai> element, along with the message archive history &xep0313;.

+ + What should I say? + + + + + + Romeo! + + + + + + My dear? + + + + + + + At what o'clock to-morrow + Shall I send to thee? + + + + + + +]]> + + At the hour of nine. + + + + + + Romeo! + + + + + + My dear? + + + + + + + At what o'clock to-morrow + Shall I send to thee? + + + + + + +]]> + + + + +
    +
  • The artificial intelligence should only be used for lawful and ethical purposes, and in compliance with all applicable laws and regulations.
    • +
  • The use of the artificial intelligence should not violate the privacy rights of any individuals, and all data should be handled in accordance with privacy laws and policies.
    • +
+ + +
    +
  1. The messaging app should provide a clear indication that the suggested messages are generated by an AI service, and provide an option for the user to opt-out of the feature.
    2. +
  2. The suggested messages should be presented in a way that distinguishes them from the user's own messages, and allows the user to edit or customize them before sending.
    3. +
  3. The user interface should provide a way for the user to provide feedback on the suggested messages, such as rating them or reporting inappropriate suggestions.
    4. +
+ + + +

There is no implementation to make the AI have a default setting and return a response from that setting.

+ + +

The value returned by artificial intelligence consists entirely of text. Returned text can be accessed using voice-over technologies.

+ + +

Determining when an AI question can be executed based on permissions or rights is considered outside the scope of this document. Although such mechanisms are considered specific to the application and/or implementation of this document, future specifications may address these concerns.

+

When processing reported AI questions, the requester SHOULD consider any question node that does not match the JID of the responder to be suspicious, and ignore those AI questions nodes. Responders MUST report their own AI question nodes only, and not the AI question nodes of other entities. This can help prevent limited cases of spoofing and "social engineering".

+ + +

This document requires no interaction with the &IANA;.

+ + + +

This specification defines the following XML namespace:

+
    +
  • urn:xmpp:ai:0
    • +
+

Upon advancement of this specification from a status of Experimental to a status of Draft, the ®ISTRAR; shall add the foregoing namespace to the registry located at &NAMESPACES;, as described in Section 4 of &xep0053;.

+ + + &NSVER; + + + +

The results of artificial intelligence have not been put into any classification. In addition to the response it returns, &xep0004; can be used to specify which parameters it obtained this different result from.

+ + +

REQUIRED for protocol specifications.

+ + + + + + + The protocol documented by this schema is defined in + XEP-xxxx: http://www.xmpp.org/extensions/xep-xxxx.html + + + + + + + + + + + + + + + + + + + + +]]> + +