[
https://issues.apache.org/jira/browse/SHINDIG-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561661#action_12561661
]
Kevin Brown commented on SHINDIG-31:
------------------------------------
To reiterate what John has said -- Shindig is not the appropriate forum for
discussing spec issues, because shindig does not define the spec (it implements
it). Until the spec is formally published (which should be happening in the
next few days), the only spec to go by is what igoogle is doing, since igoogle
is the only existing implementation of the gadget spec. What you see right now
is essentially a port of igoogle's processing logic (with some additional
things that are being standardized now but aren't yet implemented in any google
products).
Shindig is not a standards body, it is a reference implementation of a set of
standards (much like Tomcat and Apache web server don't define the HTTP
standard, they just implement it).
Most of us (if not all, I really don't know) who have commit access to shindig
currently also happen to be involved in the process that has been taking place
in going from "Google Gadgets" to open social, so we're aware of what direction
the spec is going in. The code you're seeing in shindig today is representative
of what will be in the spec, but it is not shindig deciding how this will
happen. Unfortunately, publishing the formal spec took a lot more work (and
lawyers and other bs that engineers shouldn't have to deal with) than writing
code did, and since we can easily change code (but specs live a very long
time), many of us started working on shindig well in advance of the publication
of the spec.
Once the specs are published, shindig will take great care to implement it. If
/ when there is some standards body to be a member of, we will ideally have
representatives from the project on it (again, in the same way that other ASF
members are also members of the W3C or IETF). Unfortunately, I don't have
details on when / where the right forum to bring up issues with the specs are
right now because we don't even have a "home" for the specs. Initially I
believe they are going to be on code.google.com in the same way that the open
social spec is, but eventually they'll move once things are stable and we have
some sort of formal process in place.
Currently, the only spec that has been published is the open social javascript
API. There are many other pieces necessary to complete the eco system, and
shindig will provide reference implementations for all of these. Off the top of
my head, these include (but are not limited to):
- <ModuleSpec> (XML schema and companion processing notes, including message
bundles)
- gadgets.* core javascript APIs (mostly ports of the existing igoogle
libraries, refactored and renamed)
- opensocial.* javascript APIs
Shindig does have a few semi-formal standards that it has defined, but at
present we are not considering them to be public specs, but rather
shindig-specific implementation details (example: feature.xml).
The obvious thing to do in the short term is to have the people who are working
on getting the specs published establish some sort of place for discussing
these issues. Since I happen to sit right next to two of the people involved,
I'll bug them to at least start a google group that's similar to the open
social mailing list.
> Find a reasonable home for discussing the Gadget Spec
> -----------------------------------------------------
>
> Key: SHINDIG-31
> URL: https://issues.apache.org/jira/browse/SHINDIG-31
> Project: Shindig
> Issue Type: Task
> Reporter: Paul Lindner
> Assignee: John Hjelmstad
> Priority: Critical
>
> This issue co-opted from Paul's request for TOS in the spec, which will be
> the first issue raised in the forum:
> [--first issue description--]
> To allow developers to specify their terms of service for their Application
> we should
> allow a way to specify terms of service inside the XML file:
> <tos xml:lang="en" type="text/html"
> url="http://www.example.com/myapp/tos.html"/>
> <tos xml:lang="es" type="text/html"
> url="http://www.example.com/myapp/tos-es.html"/>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
