354964 - No placeholder for microsummaries namespace

Status: RESOLVED FIXED

(www.mozilla.org :: General, defect)

Description

[Robert Accettura [:raccettura]]

There is a page for the XUL namespace:
http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul

But no page for the microsummaries namespace:
http://www.mozilla.org/microsummaries/0.1

This should be fixed...

Comment 1

[Robert Accettura [:raccettura]]

Attachment: Patch

Comment 2

[Ryan Flint [:rflint] (ping via IRC for reviews)]

*** Bug 344054 has been marked as a duplicate of this bug. ***

Comment 3

[Robert Accettura [:raccettura]]

Note the patch meets the following requirements:
- Links to content with a friendly license.
- Valid HTML 4
- Easter egg ;-)

Comment 4

[Myk Melez [:myk] [@mykmelez]]

sheppy is working on a doc describing the grammar for this namespace.  Seems like we should link/redirect to that when it's ready.

Comment 5

[Eric Shepherd [:sheppy]]

The microsummary grammar reference is at:

http://developer.mozilla.org/en/docs/Microsummary_XML_grammar_reference

If anyone sees anything sucky about it, let me know.

Comment 6

[Ryan Flint [:rflint] (ping via IRC for reviews)]

*** Bug 359793 has been marked as a duplicate of this bug. ***

Comment 7

[Steffen Wilberg]

Can we please add the redirect now, to the page mentioned more than 2 years ago in comment 5?

Comment 8

[David Boswell]

If I understand the issue correctly, it is not ideal to have the URL of a namespace redirect somewhere else (this comment has been made in other bugs where people are talking about other namespace URLs).  If there is a redirect, people could end up using the link they get sent to for the URL of the namespace.  I think the best thing to do is set up a landing page that then links to some set of docs.  This is what the XUL namespace URL does:

http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul

Comment 9

[Gordon P. Hemsley [:GPHemsley]]

This issue should have been taken care of by the fix for bug 670316, so resolving as FIXED.

If you find that the namespace URI still does not resolve, please reopen this bug.

However, if you feel that this fix was unsatisfactory, or that the information about this particular namespace URI should be modified or updated, please file a new bug.