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

Clarify namespaces #55

Closed
MartijnR opened this issue Dec 22, 2016 · 2 comments
Closed

Clarify namespaces #55

MartijnR opened this issue Dec 22, 2016 · 2 comments

Comments

@MartijnR
Copy link
Contributor

MartijnR commented Dec 22, 2016

@lognaturel writes:

I know the document pre-supposes a good working understanding of XML but I'm wondering whether it might be worth linking to a quick resource about namespaces along with introducing this (good) change? It might also be good to explain things like the value of having separate OpenRosa XForms and OpenRosa javarosa namespaces as defined in this example.

@lognaturel
Copy link
Member

lognaturel commented Dec 23, 2016

I got a little more background from @MartijnR and will take a stab at writing up what I've learned.

The key thing is that namespaces were introduced to identify additions not in the XForms 1.0 spec but were not used consistently. jr: was the originally chosen namespace but it unfortunately is tied to JavaRosa which is a specific implementation. orx: is an implementation-agnostic replacement.

@MartijnR
Copy link
Contributor Author

MartijnR commented Dec 23, 2016

Yes, the way I see it, the key is for them to be namespaced with anything. The actual namespace value is less important, as long as we can limit the amount of different namespaces somewhat. The JavaRosa namespace could identify the origin of a particular extension which seems fair enough. Though ideally, in the future, we agree on extensions before they are implemented and then use the openrosa.org/xforms namespace.

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

No branches or pull requests

2 participants