Thanks Dominique, I would like just to add that the issue is also on "Config" meta-data (not only About) It is Config maintained by Core WG, isn't it?
Bye /S ________________________________________ STEFANO TOPPAN GTC (Global Technology Center) ELECTROLUX ITALIA S.p.A. Corso Lino Zanussi, 30 - 33080 Porcia (PN) - Italy Tel: +39 0434 394901 Direct: +39 0434 394956 Fax: +39 0434 394915 E-mail: [email protected] Web site: www.electrolux.com From: "Dominique Chanet (QEO LLC)" <[email protected]> To: Stefano Toppan <[email protected]>, "[email protected]" <[email protected]>, "[email protected]" <[email protected]>, Date: 16-02-16 12:44 PM Subject: Re: [Allseen-irb] Custom Metadata Fields About is maintained by the Core WG, so this question should really be directed to them. I’ve put the core mailing list in the loop. I think your assessment is correct, though: adding custom metadata fields is OK. And yes, we need a convention to avoid naming conflicts. HAE has set precedent here, and it is good precedent, so we should codify that as a general rule. So I think the main takeaway from this question is that the documentation for About should be adapted (potentially along with the certification tests) to turn the namespacing of custom About metadata fields into at least a recommended best practice and potentially a hard rule. -Dominique From: <[email protected]> on behalf of Stefano Toppan Date: Tuesday 16 February 2016 at 11:05 To: "[email protected]" Subject: [Allseen-irb] Custom Metadata Fields Dear Dominique and IRB members, when HAE project was defining its own interfaces, you suggested to exchange some devices info at discovery phase adding some "custom" meta-data fields in the About and Config. You can see in the "HAE Theory of Operation" ( https://git.allseenalliance.org/gerrit/#/c/5119/5/interfaces/org.alljoyn.SmartSpaces/theory-of-operation-v1.md at paragraph "Service Framework's Custom Metadata Fields"); they are recognizable because of the common name-space "org.alljoyn.SmartSpaces". My question is: is it allowed to add other custom meta-data for "vendor specific" application? I mean, is it possible in a specific application to add a new meta-data field to those in the About data interface? (e.g. somethink like "MyOwnField" with its own type) I looked up in AllSeen site and there is no mention about it (anyway there is not even mention about adding meta-data for standard services like HAE did); In addition I had a quick check on the certification tests of the About feature and it seems that a custom meta-data is not invalidating them. So in principle I think it is possible to add proprietary meta-data. Anyway could you please clarify the doubt? Thanks. Moreover if custom meta-data are allowed I think it is the case to add some rules to their name to avoid future overlapping; e.g. using a name-space conventions like in HAE. On the other hand (i.e. if you decide that they are not possible) I think it should be specified better in your guidelines. Thanks Stefano ________________________________________ STEFANO TOPPAN GTC (Global Technology Center) ELECTROLUX ITALIA S.p.A. Corso Lino Zanussi, 30 - 33080 Porcia (PN) - Italy Tel: +39 0434 394901 Direct: +39 0434 394956 Fax: +39 0434 394915 E-mail: [email protected] Web site: www.electrolux.com This email and any attached files is for the attention of the intended recipient. The email and any attachments may contain material that is confidential, privileged and/or attorney work product. If you are not the intended recipient: (a) contact the sender immediately and delete from your system all copies of the email including any attachments. (b) do not read, print, retain, copy or disseminate this message or any part of it. Any such unauthorized use may be unlawful. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore can not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. The Electrolux Group www.electrolux.com This email and any attached files is for the attention of the intended recipient. The email and any attachments may contain material that is confidential, privileged and/or attorney work product. If you are not the intended recipient: (a) contact the sender immediately and delete from your system all copies of the email including any attachments. (b) do not read, print, retain, copy or disseminate this message or any part of it. Any such unauthorized use may be unlawful. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore can not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. The Electrolux Group www.electrolux.com
_______________________________________________ Allseen-core mailing list [email protected] https://lists.allseenalliance.org/mailman/listinfo/allseen-core
