Ensure that service provider metadata management is forward-compatible with Share #11

Closed
michaelrhanson opened this Issue Mar 19, 2012 · 3 comments

Comments

Projects
None yet
2 participants
Member

michaelrhanson commented Mar 19, 2012

Whatever we do to manage service provider metadata should evolve naturally from our Share implementation.

Member

mixedpuppy commented Mar 19, 2012

right now there different db files for the addons, but the manifest code is essentially the same. we just need to define a manifest format, preferably compatible with the apps manifest. I should refactor the manifest code a bit so the lib file for it remains the same between the two.

Member

mixedpuppy commented Apr 5, 2012

Here's a strawman proposal for manifest syntax, which shouldn't interfere with app manifest structure:

{
'browserServices':
{
'activities': {
'share': { ... }
}
'social': {
'name': 'mysite',
'iconURL': ...
'workerURL': ...
'sidebarURL': ...
'URLPrefix': ...
}
}
}

Member

mixedpuppy commented May 15, 2012

recent changes, documented in https://github.com/mozilla/socialapi-dev/blob/develop/docs/socialAPI.md avoids conflict with share and webapps manifest data

mixedpuppy closed this May 15, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment