inclusion for cdgroups (and semantics of nested) cdgroups.
kohlhase opened this issue · 2 comments
In #57 proposes to add a cdgroup
attribute to OMOBJ
as a catalog for default cdbases
. This works well, if we can build "the cdgroup of all things I care about". This would be made much much easier, if CDGroup
had an inclusion mechahism.
Concretely, I propose to add an element CDGroupInclude
with a href
attribute that specifies the URI of the CDGroup
to be included.
Acting on these inclusions would create "nested CDGroup", which we could flatten into an un-"nested CDGroup", which constitutes the meaning of the inclusion-extended CDGroup.
But if we want to use CDGroups as catalogs as suggested in #57, then
- we need
CDURL
children ofCDGroupMember
to be present (or defaulted). - we need to require uniqueness (see #60 for a discussions).
For 1. I would suggest that if a CDURL is not present, then its URL is derived from the CDGroup URL by replacing the file name with the value of the CDName
field and appending the .cdg
extension.
For 2. I propose that the last (we could equivalently also use the first, but last is more often used I think) URL for the CDName
determines the catalog CDURL.