oasis-library-review — archive

[Robin Cover]

Sorry, I should have documented the statement > the Naming Guidelines place > no constraints upon TC members as to the use or non-use of the substring > 'spec' in a filename, whether that file(name) is associated with a designated > "spec-track" document or not. Here's the principal section: note, e.g., the absence of any directive about (non-) use of the substring 'spec' (or 'specs') in any filename http://docs.oasis-open.org/specGuidelines/namingGuidelines/resourceNamingV07.html#nameConstruction and (e.g.,) "Componentized filenames (e.g., IETF-style filenames, using hyphen-separated metadata factoids) are allowed but not required" That null rule is related to an explicit conclusion from the membership (two reviews) per: http://docs.oasis-open.org/specGuidelines/namingGuidelines/resourceNamingCommentaryV07.html#nameConstruction "A significant conclusion emerged from the two public reviews of AIR (July 2005) and ASIS (February 2006): the OASIS membership does not welcome a policy mandating the use of structured filenames which use hyphen-delimited metadata components, IETF-style. In some cases it may be natural and desirable to use some "metadata" information in filenames and URIs, but we heard strong negative reaction against the early proposal to make a componentized schema required. " See also the spec URI examples provided in this section: http://docs.oasis-open.org/specGuidelines/namingGuidelines/metadata03.html#specURIs examples like: http://docs.oasis-open.org/health/virus-ml/virusML-1.html http://docs.oasis-open.org/exampleTC/nutMarkup/4.0/pr3.5/nut.html http://docs.oasis-open.org/exampleTC/fruitMarkup/v2/fruit.pdf -rcc Robin Cover OASIS, Chief Information Architect Editor, Cover Pages and XML Daily Newslink http://xml.coverpages.org/ On Mon, 31 Mar 2008, Robin Cover wrote: > Neil, thanks for updates. A couple minor followups inline below. > > On Mon, 31 Mar 2008, Neil Schelly wrote: > >> Robin has been browsing around the KT library and commented on changed >> permissions with some of his earlier test files. The entire permissions >> system has been replaced to tie into the Kavi authentication system. > > I managed to figure that out after some experimentation > >> >> The initial installation of KT had basically unlimited permissions for >> everyone so you could browse the system and see it at full functionality. >> Now, you should be logging in with your Kavi credentials and the fwsi and >> dev-testing TC folders are setup with appropriate permissions given to TC >> members and TC administrators. Please do your testing in there. >> >> Also, most of Robin's tests seem to be testing naming guidelines. The >> naming >> guidelines aren't implemented. They can't be implemented as written >> because >> they are too vague in some spots and that's a discussion for another day. >> When we get it to concrete rules, we can code it. Currently, the naming >> guidelines are setup only as a light check. You can't publish a non-spec >> document that has the word spec in the name. You can upload it, but you >> cannot publish it until you rename it. > > We'll need to have that discussion. For example, the Naming Guidelines place > no constraints upon TC members as to the use or non-use of the substring > 'spec' in a filename, whether that file(name) is associated with a designated > "spec-track" document or not. Thanks for clarification about the current > non-implementation of the NG. Any of my tests are likely to be based > upon minimum assumptions -- as in "this is possibly how the system would > behave out-of-the-box-without-without-major-obvious-changes". It's > helpful to be able to see how KT behaves, even if the test install is > in limbo/transition. > >> >> Anyway, we need a presentation to go over the recent changes and the >> current >> status of the prototype. I just wanted to send this quickly, because of >> Robin's requests for help with permissions changes last Friday. > > Thanks. > >> >> -- >> Regards, >> Neil Schelly >> >> W: 978-667-5115 x213 >> M: 508-410-4776 >> >> Senior Systems Administrator >> OASIS http://www.oasis-open.org >> "Advancing open standards for the information society." >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. You may a link to this group and all your TCs in >> OASIS >> at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >