[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: filemames
[Ray said] > So the document URIs would look like > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overview/searchRetrieve-v1.0-csd01-part0-Overview.html Yes, exactly right! The pattern emerges by rule from the Naming Directives once we have settled on an identifier for each prose part (partIdentifier) and once we have settled on the ordering of the subcomponents [version-id] ; [stage-abbrev][revisionNumber] ; [partIdentifier] -- and we have done that in off-list conversations, reflected in your summary messages to the TC list. The resolution emerges from the rules for specifications that are not multi-part. Full display of example URIs below. * Full URI for principal document identifier (document URI) ND: http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#paths Rule: http://docs.oasis-open.org/[tc-shortname]/[WP-abbrev]/[version-id]/[stage-abbrev][revisionNumber]/[doc-id].[ext] * Filename: ND: http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#nameConstruction ND: http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html#filenameSyntax Rule: [WP-abbrev]-[version-id]-[stage-abbrev][revisionNumber].[ext] Agreement to date: ================================================ I. base filenames for the principal document URIs at level csd01 ================================================ searchRetrieve-v1.0-csd01-part0-Overview.html searchRetrieve-v1.0-csd01-part1-APD.html searchRetrieve-v1.0-csd01-part2-SRU1.2.html searchRetrieve-v1.0-csd01-part3-SRU2.0.html searchRetrieve-v1.0-csd01-part4-OpenSearch.html searchRetrieve-v1.0-csd01-part5-CQL.html searchRetrieve-v1.0-csd01-part6-Scan.html searchRetrieve-v1.0-csd01-part7-Explain.html ================================================ II. Initial directories (when WD package is balloted as CSD01): ================================================ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overview/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part1-APD/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part2-SRU1.2/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part3-SRU2.0/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part4-OpenSearch/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part5-CQL/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part6-Scan/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part7-Explain/ ================================================ III. URIs for each of the prose part documents, for csd01 (HTML format) ================================================ Here's the example for csd01 that includes directories and filenames for the (primary) document URIs that are used on a spec cover page [Specification URIs], in the Citation format block, etc -- unless I have messed up ;-) http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overview/searchRetrieve-v1.0-csd01-part0-Overview.html http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part1-APD/searchRetrieve-v1.0-csd01-part1-APD.html http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part2-SRU1.2/searchRetrieve-v1.0-csd01-part2-SRU1.2.html http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part3-SRU2.0/searchRetrieve-v1.0-csd01-part3-SRU2.0.html http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part4-OpenSearch/searchRetrieve-v1.0-csd01-part4-OpenSearch.html http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part5-CQL/searchRetrieve-v1.0-csd01-part5-CQL.html http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part6-Scan/searchRetrieve-v1.0-csd01-part6-Scan.html http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part7-Explain/searchRetrieve-v1.0-csd01-part7-Explain.html ================================================ IV. The directory names per stage will be incremented for each stage/release, e.g., ================================================ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd02/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csprd01/ http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd03/ (with the subordinate 8x directories storing partIdentifier in each case. pre example in "II" above) ****** All this subject to verification by others as sanity check Thanks! Another message to follow shortly about "consolidation" of the required information discussing XML namespace names, URI listings for the XML schema resources, citations in Normative and Non-Normative sections [in 1. Introduction ] - basic replay is "yes, OK to consolidate all three into the Overview document. Details to follow. - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Wed, Jul 6, 2011 at 12:35 PM, Ray Denenberg, Library of Congress <rden@loc.gov> wrote: > Ok, I think I missed the directory/filename distinction. Let me be sure I > understand. > > You are saying that: > > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w/ > > is a directory, while I was assuming that it was shorthand for three > document URIs > > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w.html > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w.doc > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w.pdf > > But instead, you're saying the three document URIs look like > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w/xxx.html > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w/xxx.doc > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w/xxx.pdf > > > But then, in the example > http://docs.oasis-open.org/emix/emix/v1.0/csprd02/emix-v1.0-csprd02.doc > http://docs.oasis-open.org/emix/emix/v1.0/csprd02/emix-v1.0-csprd02.html > http://docs.oasis-open.org/emix/emix/v1.0/csprd02/emix-v1.0-csprd02.pdf > > there is a single directory, csprd02, while in our case there are eight. > That's because ours is multipart and the example is single part? > > > So the document URIs would look like > > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w/searchRetrieve-v1.0-csd01-part0-Overview.html > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w/searchRetrieve-v1.0-csd01-part0-Overview.html > http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0-Overvie > w/searchRetrieve-v1.0-csd01-part0-Overview.html > > ?? > > Sorry, to be so dense, I hope I have it right now. > > --Ray > > >> -----Original Message----- >> From: Robin Cover [mailto:robin@oasis-open.org] >> Sent: Wednesday, July 06, 2011 10:07 AM >> To: Denenberg, Ray >> Cc: Robin Cover >> Subject: Re: filemames >> >> On Wed, Jul 6, 2011 at 8:36 AM, Ray Denenberg, Library of Congress >> <rden@loc.gov> wrote: >> >> [Ray] >> >> > Robin - I don't understand the significance of filenames. Where are >> > these visible? Aren't the URIs sufficient? >> >> [Robin replies] >> >> The URIs you designed (and I reviewed) are URIs matching the >> directories for the eight documents. They are valid URIs for >> identification and location. But the OASIS tradition, like that of >> some other SSOs/SDOs, is to publish the URIs for the individual prose >> documents on each (prose) document cover page. The "document" URI >> incorporates the filename into the identifier string, which of course >> also uses the directory structure. >> See below for more >> >> Your directory URIs are: >> >> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part0- >> Overview/ >> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part1- >> APD/ >> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part2- >> SRU1.2/ >> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part3- >> SRU2.0/ >> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part4- >> OpenSearch/ >> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part5- >> CQL/ >> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part6- >> Scan/ >> http://docs.oasis-open.org/search-ws/searchRetrieve/v1.0/csd01/part7- >> Explain/ >> >> For examples of specification cover pages (including prose document >> "Parts" in a multi-part work), see these examples, cover page and the >> set of (typically 9x) URIs in the block "Specification URIs:" >> >> 1. http://docs.oasis-open.org/office/v1.2/cos01/OpenDocument-v1.2- >> cos01-part1.html >> 2. http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep- >> core-rs-v4.0-csprd01.html >> >> Because the OASIS rules (in particular) require the publication of >> three formats (Editable source, [X]HTML, PDF), we need the Spec URI >> block so that users can readily choose from among the three formats as >> suitable for their use (e.g., HTML is most easily navigated in a Web >> browser); >> >> Three formats: >> http://www.oasis-open.org/policies-guidelines/tc-process-2010-07- >> 28#quality-fileFormats >> >> See the rules for constructing the (prose) document cover page URIs: >> >> (note we have adjusted for multi-part by adding the partIdentifier >> element into the rule pattern) >> >> * Filename: >> ND: http://docs.oasis- >> open.org/specGuidelines/ndr/namingDirectives.html#nameConstruction >> ND: http://docs.oasis- >> open.org/specGuidelines/ndr/namingDirectives.html#filenameSyntax >> Rule: [WP-abbrev]-[version-id]-[stage-abbrev][revisionNumber].[ext] >> >> * Full URI for principal document identifier >> ND: http://docs.oasis- >> open.org/specGuidelines/ndr/namingDirectives.html#paths >> Rule: http://docs.oasis-open.org/[tc-shortname]/[WP-abbrev]/[version- >> id]/[stage-abbrev][revisionNumber]/[doc-id].[ext] >> >> >> >> >> 6a. Filenames: Ray, please review these >> >> >> >> For filenames (HTML, similarly for PDF/DOC) >> >> >> >> rule for "single-part": >> >> [WP-abbrev]-[version-id]-[stage-abbrev][revisionNumber].[ext] >> >> proposal to use: >> >> [WP-abbrev]-[version-id]-[stage-abbrev][revisionNumber]- >> >> [partIdentifier].[ext] >> >> >> >> >> >> searchRetrieve-v1.0-csd01-part0-Overview.html >> >> searchRetrieve-v1.0-csd01-part1-APD.html >> >> searchRetrieve-v1.0-csd01-part2-SRU1.2.html >> >> searchRetrieve-v1.0-csd01-part3-SRU2.0.html >> >> searchRetrieve-v1.0-csd01-part4-OpenSearch.html >> >> searchRetrieve-v1.0-csd01-part5-CQL.html >> >> searchRetrieve-v1.0-csd01-part5-Scan.html >> >> searchRetrieve-v1.0-csd01-part7-Explain.html >> > >> > >> > Robin - I don't understand the significance of filenames. Where are >> > these visible? Aren't the URIs sufficient? >> > >> > --Ray >> > >> > >> >> >> >> -- >> Robin Cover >> OASIS, Director of Information Services >> Editor, Cover Pages and XML Daily Newslink >> Email: robin@oasis-open.org >> Staff bio: http://www.oasis-open.org/people/staff/robin-cover >> Cover Pages: http://xml.coverpages.org/ >> Newsletter: http://xml.coverpages.org/newsletterArchive.html >> Tel: +1 972-296-1783 > > --
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]