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

Create new XmlnsDefinition standard #32

Closed
brianlagunas opened this issue Apr 3, 2015 · 10 comments
Closed

Create new XmlnsDefinition standard #32

brianlagunas opened this issue Apr 3, 2015 · 10 comments

Comments

@brianlagunas
Copy link
Member

When Prism was in Microsoft's hands they used two XmlnsDefinitions:

XmlnsDefinition("http://www.codeplex.com/CompositeWPF", "namespace") -- original
XmlnsDefinition("http://www.codeplex.com/prism", "namespace") - this was meant to replace the original

Now, we should come up with a new schema that is not tied to the codeplex name.

We do have a domain "http://PrismLibrary.com", that has yet to have a site created. So should we use this now?

XmlnsDefinition("http://prismlibrary.com/", "namespace")
XmlnsDefinition("http://www.prismlibrary.com/", "namespace") -- notice the addition of "www"

Other ideas?

@Mike-E-angelo
Copy link

I like it. My vote/preference would be without the www (seems sort of old skool and not as concise). I also like the domain in general, as it leads towards a (wicked-short) suggested candidate "pl" prefix. :)

@brianlagunas
Copy link
Member Author

Well since we don't have any components in the VS toolbox, we don't have to specify a default prefix. If we did have a default prefix, say in our project and item templates I'll be creating, I would probably go with "prism".

@briannoyes
Copy link
Contributor

Why not use its actual new home at github.com/prismlibrary?

@brianlagunas
Copy link
Member Author

Well, do we want to tie the name to a source control vendor? Even if we didn't own the actual domain name, http://prismlibrary.com/ would be specific to prism and not imply a method of source control. What happens when the next great source control solution CleanSource is released?

@bartlannoeye
Copy link
Contributor

I'm up for using the domain name as the new definition.

@briannoyes
Copy link
Contributor

Fair point, since we own the domain and since it would make intellisense selection quicker, I vote for http://prismlibrary.com

@wldevries
Copy link
Contributor

Why not .net or .org, Prism is not commercial right?

@brianlagunas
Copy link
Member Author

This has been complete. I left the XmlnsDefinition("http://www.codeplex.com/prism", "namespace") definition in there for backwards compatibility.

@brianlagunas
Copy link
Member Author

Having a .com doesn't mean it's a commercial product. Lots of open source projects the use the .com domain alias (GitHub) since it is the most widely used and it's usually the first thing someone types when looking for a website.

@lock
Copy link

lock bot commented Feb 1, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants