Just reporting on some observations. Not sure if all is according to design or if some defects exist. Hopefully, this is somewhat useful info.
I'm moving along nicely now with the beta capability, and have configured the Open Data site. I shared an ArcGIS Online hosted feature service to my Open Data group, and it showed up in the Recent Data section, right on queue. When I began interacting with my data, I realized that Open Data presentation of my service:
in MAP view does not respect field aliases or coded value domains in popup
in Full Details view, converts item "Access and Use Constraints" to "License Info" and does not respect formatting
in DETAILS view respects field aliases but not the coded value domains
in DETAILS view converts item "Description" to "DETAILS" and does not respect formatting
in TABLE view does not respect field aliases or coded value domains
in DOWNLOAD > Shapefile, does not provide the metadata (but of course, that's lopped off during service publishing)
in Full Details view, converts item "Access and Use Constraints" to "License Info" and does not respect formatting
...working with this again, it dawns on me that "License Info" suggests licensing, which does not seem to align with Open Government Data principle #8 http://opengovdata.org/.
Thanks for reporting the issue with alias's, we'll take a look!
As for the licensing question, I saw that you reference this: 8. License-freeData is not subject to any copyright, patent, trademark or trade secret regulation. Reasonable privacy, security and privilege restrictions may be allowed. You can see that the Data Driven Detroit site handles this quite well by referencing a Creative Commons license. They simply would like to be referenced if the data is reused.
