Agree with what you have stated. Features is a word that is familiar in the context of mobile, We actually map this into actuators(things that we can operate) in a device context. so we can map features into operation however in the current context feature definition does not give any meaning about the parameters and definition of the api it could be - This is something we need to rethink about. A sample reference would be to think like what eclipse vorto have done with the way they map the actuators to operations[1]. Another possible approach is Feature contains another property called "MetaDataEntries" (along with code, name, description) we could provide addition properties through this.
In addition about your comments related to provide version strategy to features, A doubt I have is for given version of android we have specific features it support with a clear definition. However across different version this could change but my question is do we have to support version strategy in feature level or do we have to support version strategy in a device type level(android,windows,ios, raspberry pi..etc)? [1] http://vorto.eclipse.org/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
