> {<module-name>:<pub-id>:<area>:<doc-id>:<doc-lang>:<p1>:<p2>:<...>:<px>}
> {<module-name>:<pub-id>:<area>:<doc-lang>:<doc-id>:<p1>:<p2>:<...>:<px>}
I prefer extendable parameters after defined parameters, so I prefer
the last, but this is a cosmetic decision.
The pub-id should be before the module name. A publication can
override a global module, and can have publication-specific modules.
I hope "area" will soon be replaced by modules. Are there any modules
that care about both "live" and "authoring"? Admin modules do not
care about either. Editing modules care about "authoring".
Functional modules (Search, Sitemap, Summaries) care about "live". If
a module does care about both, it can default to "live" unless a
module-specific parameter specifies "authoring".
I suggest:
{<pub-id>:<module-name>:<doc-lang>:<doc-id>:<p1>:<p2>:<...>:<px>}
> This raises the question if we should even use the URL snippet for
> the document locator, or rather a globally unique ID (either generated
> by the system, or assigned upon document creation). This would allow
> to match the document locator using a single asterisk, which would
> probably simplify pipelines.
Other platforms wrap global identifiers in braces {}. So a document could be:
/hr/benefits_en.html
or
{2005120120070766} (Global identifiers are usually time-based to
prevent duplicates.)
Using braces could be a problem if the braces in this proposal are
meant to be the specification.
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
