Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OPML export should be extended to include feed tags and face url #28

Open
jvasile opened this issue Mar 28, 2013 · 3 comments
Open

OPML export should be extended to include feed tags and face url #28

jvasile opened this issue Mar 28, 2013 · 3 comments

Comments

@jvasile
Copy link
Owner

jvasile commented Mar 28, 2013

The OPML spec at http://dev.opml.org/spec2.html says:

An OPML file may contain elements and attributes not described on this page, only if 
those elements are defined in a namespace, as specified by the W3C.

OPML can also be extended by the addition of new values for the type attribute. 
When specifying such an extension, following the example of this specification, say
which attributes are required and which are optional, and explain the roles each of the 
attributes plays, how they relate to each other, and what rules they must conform to.
There is a mechanism in the OPML Editor that is based on this form of extension.

Developers should, whenever possible, use capabilities that are already in use by 
others, or included in this spec, or recommendations or guidelines.

Our feeds have tags and face (hackergotchi) urls. We should export those in the OPML file planeteria should import from such an OPML file, as per issue #4.

@jvasile
Copy link
Owner Author

jvasile commented Mar 29, 2013

Actually, we can just adjust the template and not mess with namespaces. OPML spec does not prevent us from adding attributes.

@dtiburon
Copy link
Collaborator

Since I'm making major changes to the template.py file with the redesign, let's take a look at the OPML stuff once I'm done with it.

@jvasile
Copy link
Owner Author

jvasile commented Apr 2, 2013

We'll need unit tests for this. Marking "Testing"

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

No branches or pull requests

2 participants