You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2003/12/04 14:03:21 UTC

[RFP] Repository requirements

Hi Lenya developers,

on the cocoon-dev mailing list there is a thread
about converging the repository concept in Cocoon:

http://marc.theaimsgroup.com/?t=107022316500003&r=1&w=2

The basic idea is to define a repository API for Cocoon,
at a more application-oriented level than, e.g., JCR.
The API could be implemented for instance by a wrapper
around JCR.

Stefano invited the Lenya community to collect our
ideas and requirements regarding the repository
functionality. IMO we should seize this opportunity
to influence this development and to increase the
cooperation with the Cocoon community.

The question is whether we should discuss this here
or on cocoon-dev (I think the latter makes more sense).

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Andreas Hartmann <an...@apache.org>.
Rolf Kulemann wrote:

> May be I should setup a webpage for the list?

http://wiki.cocoondev.org/Wiki.jsp?page=LenyaRepositoryRequirements

Thanks for all your comments,

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Mon, 2003-12-08 at 09:59, Rolf Kulemann wrote:
> On Mon, 2003-12-08 at 09:35, Rolf Kulemann wrote:
> > On Mon, 2003-12-08 at 00:13, Stefano Mazzocchi wrote:
> >[...]
> > I will try to reflect this discussion in the requirements list. I think
> > I have to change priorites a little bit, because metadata is mandatory
> > when implementing workflow via metadata and workflow is a core
> > functionality in Lenya.
> 
> Here it is.

The used discussion links were broken, sorry.
Here is the list again. May be I should setup a webpage for the list?
Would reduce my trash posting :-)


Lenya requirements for a content repository ordered by priority
-------------------------------------------------------------------------------

Changes
--------------------
2003/12/08 - Changed 1.5.) to fullfill workflow req. Added 1.6.) and
3.4.). Moved 3.3.) to 1.7.). Changed 2.2.). 
Added Open Issues section. Added "relevant mailinglist threads" section

2003/12/07 - Moved 1.7.) to 3.3.), so the requirement of moving items in
the repository.


High priority
--------------------
1.1) open/save document

1.2.) create collection of documents

1.3.) open and save collections of assets

1.4.) *simple* versioning

1.5.) Extensible metadata in order to reflect things like workflow as
discussed here:
http://article.gmane.org/gmane.comp.cms.lenya.devel/2005
1.6.) Simple metdata queries in order to fullfill 1.5.)

1.7.) Moving of assets in the repository (without breaking contracts).
The moving of assets can be implemented via metadata see 1.7.). 
See discussion here:
http://article.gmane.org/gmane.comp.cms.lenya.devel/2005
This requirement serves as basis to implement staging of assets.


Medium Priority
--------------------
2.1.) Locking of docs. This is essential for concurrent actions on docs.

2.2.) Simple transaction features.Make sense when saving doc
collections. 
Is an image a doc? I propose to use the term asset for all type of
objects in the repository. 
Transactions seem to be useful for workflow if workflow is
reflected/implemented via metadata of an asset. 
See discussion here:
http://article.gmane.org/gmane.comp.cms.lenya.devel/2005

2.3.) If access control is a concern of the Repository I propose it to
be reflected in the rep. API, because otherwise Lenya has to deal with
it. 
This is an important decision.


Low Priority
--------------------
3.1.) Complex metadata queries

3.2.)  Observation - add listeners to specific events in the repository 
 based on both the type of event and on the location in the repository.
(I have borrowed this from the cocoon-dev)

3.4.) Implement OAI for metadata crawling???


Open Issues
--------------------


Relevant Mailinglist Threads
---------------------------------
	- http://thread.gmane.org/gmane.comp.cms.lenya.devel/1960






-- 
Rolf Kulemann

Underlying Principle of Socio-Genetics:
	Superiority is recessive.


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Mon, 2003-12-08 at 09:35, Rolf Kulemann wrote:
> On Mon, 2003-12-08 at 00:13, Stefano Mazzocchi wrote:
>[...]
> I will try to reflect this discussion in the requirements list. I think
> I have to change priorites a little bit, because metadata is mandatory
> when implementing workflow via metadata and workflow is a core
> functionality in Lenya.

Here it is.



Lenya requirements for a content repository ordered by priority
-------------------------------------------------------------------------------

Changes
--------------------
2003/12/08 - Changed 1.5.) to fullfill workflow req. Added 1.6.) and
3.4.). Moved 3.3.) to 1.7.). Changed 2.2.)

2003/12/07 - Moved 1.7.) to 3.3.), so the requirement of moving items in
the repository.


High priority
--------------------
1.1) open/save document

1.2.) create collection of documents

1.3.) open and save collection of documents

1.4.) *simple* versioning

1.5.) Extensible metadata in order to reflect things like 
<a href="http://news.gmane.org/gmane.comp.cms.lenya.devel">workflow as
discussed</a>.

1.6.) Simple metdata queries in order to fullfill 1.5.)

1.7.) Moving of assets in the repository (without breaking contracts).
The moving of assets can be implemented via metadata see 1.7.). 
<a href="http://news.gmane.org/gmane.comp.cms.lenya.devel">See
discussion</a>.
This requirement serves as basis to implement staging of assets.


Medium Priority
--------------------
2.1.) Locking of docs. This is essential for concurrent actions on docs.

2.2.) Simple transaction features.Make sense when saving doc
collections. 
Is an image a doc? I propose to use the term asset for all type of
objects in the repository. 
Transactions seem to be useful for workflow if workflow is
reflected/implemented via metadata of an asset. 
<a href="http://news.gmane.org/gmane.comp.cms.lenya.devel">See
discussion</a>.

2.3.) If access control is a concern of the Repository I propose it to
be reflected in the rep. API, because otherwise Lenya has to deal with
it. 
This is an important decision.


Low Priority
--------------------
3.1.) Complex metadata queries

3.2.)  Observation - add listeners to specific events in the repository 
 based on both the type of event and on the location in the repository.
(I have borrowed this from the cocoon-dev)

3.4.) Implement OAI for metadata crawling???


Next step is to order priorities within the single sections, so within
high priority section for example.



-- 
Rolf Kulemann

"The National Association of Theater Concessionaires reported that in
1986, 60% of all candy sold in movie theaters was sold to Roger Ebert."
		-- D. Letterman


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Tue, 2003-12-09 at 10:49, Andreas Hartmann wrote:
> Rolf Kulemann wrote:
> 
> [...]

> >>At the moment, only documents can have a workflow,
> >>images etc. can not. Therefore I still used the term
> >>"document".
> > 
> > 
> > Ok, but do you think wf for all assets should be supported by Lenya in
> > the future? IMHO, yes. Here we start talking about "content lifecycle",
> > which is a key requirement for content management.
> 
> Very +1.
> 
> I didn't yet work with a system that supports workflow for all
> assets. Doesn't this become quite complex from a user's point
> of view?

Ok, *all assets* is maybe oversized, but images and snippets of markup,
sounds, movies should be supported by a wf.


-- 
Rolf Kulemann

	Murray and Esther, a middle-aged Jewish couple, are touring
Chile.  Murray just got a new camera and is constantly snapping
pictures.  One day, without knowing it, he photographs a top-secret
military installation.  In an instant, armed troops surround Murray and
Esther and hustle them off to prison.
	They can't prove who they are because they've left their
passports in their hotel room.  For three weeks they're tortured day
and night to get them to name their contacts in the liberation
movement..  Finally they're hauled in front of a military court,
charged with espionage, and sentenced to death.
	The next morning they're lined up in front of the wall where
they'll be shot.  The sergeant in charge of the firing squad asks them
if they have any lasts requests.  Esther wants to know if she can call
her daughter in Chicago.  The sergeant says he's sorry, that's not
possible, and turns to Murray.
	"This is crazy!"  Murray shouts.  "We're not spies!"  And he
spits in the sergeants face.
	"Murray!"  Esther cries.  "Please!  Don't make trouble."
		-- Arthur Naiman, "Every Goy's Guide to Yiddish"


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Andreas Hartmann <an...@apache.org>.
Rolf Kulemann wrote:

[...]

>>>I prefer to use the term asset instead of document, because when
>>>managing assets in Lenya, each asset (version) is connected to a wf
>>>instance.
>>
>>At the moment, only documents can have a workflow,
>>images etc. can not. Therefore I still used the term
>>"document".
> 
> 
> Ok, but do you think wf for all assets should be supported by Lenya in
> the future? IMHO, yes. Here we start talking about "content lifecycle",
> which is a key requirement for content management.

Very +1.

I didn't yet work with a system that supports workflow for all
assets. Doesn't this become quite complex from a user's point
of view?

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Tue, 2003-12-09 at 10:21, Andreas Hartmann wrote:
> Rolf Kulemann wrote:
> 
> [...]
> > 
> >>At the moment, several active versions of a document in
> >>different locations can share one workflow state. This
> >>would mean the workflow state information would be a
> >>metadata entry in each of these document versions.
> > 
> > Can you give me an example for two document versions sharing the same wf
> > state?
> 
> If there are two versions of a document:
> 
>      /authoring/foo.xml
>      /live/foo.xml
> 
> The XML of these two can differ (when /authoring/foo.xml was
> changed after the last publishing), but oth of them share the
> same workflow instance which is in the state "authoring".

Ok, I see. Thank you to help me understand.

> 
> > I prefer to use the term asset instead of document, because when
> > managing assets in Lenya, each asset (version) is connected to a wf
> > instance.
> 
> At the moment, only documents can have a workflow,
> images etc. can not. Therefore I still used the term
> "document".

Ok, but do you think wf for all assets should be supported by Lenya in
the future? IMHO, yes. Here we start talking about "content lifecycle",
which is a key requirement for content management.

Imagine the lifecycle of an advert, which is created and designed by an
employee and approved by his manager.


-- 
Rolf Kulemann

	THE LESSER-KNOWN PROGRAMMING LANGUAGES #10: SIMPLE

SIMPLE is an acronym for Sheer Idiot's Monopurpose Programming Language
Environment.  This language, developed at the Hanover College for
Technological Misfits, was designed to make it impossible to write code
with errors in it.  The statements are, therefore, confined to BEGIN,
END and STOP.  No matter how you arrange the statements, you can't make
a syntax error.  Programs written in SIMPLE do nothing useful.  Thus
they achieve the results of programs written in other languages without
the tedious, frustrating process of testing and debugging.


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Andreas Hartmann <an...@apache.org>.
Rolf Kulemann wrote:

[...]
> 
>>At the moment, several active versions of a document in
>>different locations can share one workflow state. This
>>would mean the workflow state information would be a
>>metadata entry in each of these document versions.
> 
> Can you give me an example for two document versions sharing the same wf
> state?

If there are two versions of a document:

     /authoring/foo.xml
     /live/foo.xml

The XML of these two can differ (when /authoring/foo.xml was
changed after the last publishing), but oth of them share the
same workflow instance which is in the state "authoring".

> I prefer to use the term asset instead of document, because when
> managing assets in Lenya, each asset (version) is connected to a wf
> instance.

At the moment, only documents can have a workflow,
images etc. can not. Therefore I still used the term
"document".

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Mon, 2003-12-08 at 14:03, Andreas Hartmann wrote:
> Rolf Kulemann wrote:
> 
> > +1. I love metadata. IMHO Lenya already uses special markup to express
> > workflow states, so it stays the same, but at the mom Lenya does staging
> > by copying/moving? 
> 
> This leads again to the question how assets and workflow
> instances are mapped to each other.

Maybe not really.

> 
> At the moment, several active versions of a document in
> different locations can share one workflow state. This
> would mean the workflow state information would be a
> metadata entry in each of these document versions.

Can you give me an example for two document versions sharing the same wf
state? I prefer to use the term asset instead of document, because when
managing assets in Lenya, each asset (version) is connected to a wf
instance.

> 
> If we introduce the concept of multiple active workflow
> instances per document, we have to find a solution for
> addressing these versions.

Thats right. So I will make the requirements list reflect this.
We need to store a set of metadata per asset version and we need to
retrieve those asset version and related metadata.


-- 
Rolf Kulemann

Stop searching.  Happiness is right next to you.  Now, if they'd only
take a bath ...


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Andreas Hartmann <an...@apache.org>.
Rolf Kulemann wrote:

> +1. I love metadata. IMHO Lenya already uses special markup to express
> workflow states, so it stays the same, but at the mom Lenya does staging
> by copying/moving? 

This leads again to the question how assets and workflow
instances are mapped to each other.

At the moment, several active versions of a document in
different locations can share one workflow state. This
would mean the workflow state information would be a
metadata entry in each of these document versions.

If we introduce the concept of multiple active workflow
instances per document, we have to find a solution for
addressing these versions.

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Mon, 2003-12-08 at 00:13, Stefano Mazzocchi wrote:
>[...]
> now, in order for the publishing layer to be able to retrive this 
> content at any time and at any stage, there must be a solid and 
> never-changing resource locator for that asset.

+1 for a *never-changing resource locator*.

> 
> Moving things around breaks this, unless your repository is able to 
> perform resource links and it is transactional.... so you have
> 
>   - begin transaction
>   - move article to another stage
>   - modify symlink to the new stage
>   - commit transation

+1 for transactional.

> 
> It is *much* better to implement the above using external metadata and 
> to keep the article in the same location, just changing its metadata. 

+1. I love metadata. IMHO Lenya already uses special markup to express
workflow states, so it stays the same, but at the mom Lenya does staging
by copying/moving? 

> So, from a workflow implementation perspective, repositories could have
> 
>   - moving
>   - transactions
>   - linking
-1

> 
> or
> 
>   - extensible external metadata
>   - metadata querying
> 
> and be equivalent in functionality.
> 
> I personally like the second approach much more.

+1.

I will try to reflect this discussion in the requirements list. I think
I have to change priorites a little bit, because metadata is mandatory
when implementing workflow via metadata and workflow is a core
functionality in Lenya.



-- 
Rolf Kulemann

			*** NEWSFLASH ***
Russian tanks steamrolling through New Jersey!!!!  Details at eleven!


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Stefano Mazzocchi <st...@apache.org>.
On 7 Dec 2003, at 07:24, Rolf Kulemann wrote:

> What is an example for a contract, which gets broken when moving docs?

A poor-man way to do workflow is to move stuff around, for example

  /articles/edit/ <- contains articles being edited
  /articles/pending/ <- contains articles pending approuval
  /articles/live/ <- contains articles approuved and visible from the 
home page
  /articles/archived/ <- contains articles approuved but not visibible 
anymore

something like this *seems* nice and easy, but there are major issues 
with this: suppose you has a simple workflow like this

  [new] -(save)-> [edit]              creates the article from template
  [edit] -(submit)-> [pending]        submits for approval
  [pending] -(approve)-> [live]       article goes online
  [live] -(time expires)-> [archived] article is archived

now, in order for the publishing layer to be able to retrive this 
content at any time and at any stage, there must be a solid and 
never-changing resource locator for that asset.

Moving things around breaks this, unless your repository is able to 
perform resource links and it is transactional.... so you have

  - begin transaction
  - move article to another stage
  - modify symlink to the new stage
  - commit transation

It is *much* better to implement the above using external metadata and 
to keep the article in the same location, just changing its metadata. 
So, from a workflow implementation perspective, repositories could have

  - moving
  - transactions
  - linking

or

  - extensible external metadata
  - metadata querying

and be equivalent in functionality.

I personally like the second approach much more.

--
Stefano.

Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Sun, 2003-12-07 at 16:24, Rolf Kulemann wrote:
> [....] 
> On 5 Dec 2003, at 23:58, Rolf Kulemann wrote:
> I think the *moving* requirement is not that
> important for Lenya. I will change the requirements list in order to
> reflect this low prio.
> [....]

In the following you will find an updated requirements list for a
content repository. I have also added a changes section to the doc/list.
I think we should try to discuss in more detail the prios I have given
the list items.

Have fun:-)



Lenya requirements for a content repository ordered by priority
-------------------------------------------------------------------------------

Changes
--------------------
2003/12/07 - Moved 1.7.) to 3.3.), so the requirement of moving items in
the repository.


High priority
--------------------
1.1) open/save document

1.2.) create collection of documents

1.3.) open and save collection of documents

1.4.) *simple* versioning (yes, I think it is high priority)

1.5.) Retrieve Meta data, so a very simple query only and no complex
searches at the first step. I think Lenya depends somehow on a docs meta
data and so I think it is high prio.


Medium Priority
--------------------
2.1.) Locking of docs. This is essential for concurrent actions on docs.

2.2.) Simple transction features. Like metioned in cocoon-dev by
Stefano, I can also imagine transactions make sense when saving doc
collections. 
Is an image a doc? I propose to use the term asset for all type of
objects in the repository. Alternative the term doc could also fit for
all objects. An Asset then can be aggregated composed by other assets.
Some assets are atomic like images sounds for example. Ok stop this
discussion here.

2.3.) If access control is a concern of the Repository I propose it to
be reflected in the rep. API, because otherwise Lenya has to deal with
it. This is an important decision.


Low Priority
--------------------
3.1.) Complex metadata queries

3.2.)  Observation - add listeners to specific events in the repository 
 based on both the type of event and on the location in the repository.
(I have borrowed this from the cocoon-dev)

3.3.) Moving of assets/items/objects in the repository (without breaking
contracts)



-- 
Rolf Kulemann

Those who can't write, write manuals.


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Sun, 2003-12-07 at 03:31, Stefano Mazzocchi wrote:
> On 5 Dec 2003, at 23:58, Rolf Kulemann wrote:
> 
> > 1.7.) Moving of docs.
> > I have a question to this req. Stefano mentioned the moving of docs.
> > What do you exactly mean? The need of a moving functionality depends on
> > how a document is referenced via the repository interface. What is a
> > *primary key* for a document to be retrieved? Have you already sth. in
> > mind? I saw some discussion in cocoon-dev related to an URI like key?
> > Maybe I misunderstood.
> 
> Be careful not to mix concerns. We are talking about the repository 
> level. moving things at the repository level means to break contracts. 
> <snip/>

Ok, I understand. So I think the *moving* requirement is not that
important for Lenya. I will change the requirements list in order to
reflect this low prio.

Another question:

What is an example for a contract, which gets broken when moving docs?


-- 
Rolf Kulemann

Who needs friends when you can sit alone in your room and drink?


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Stefano Mazzocchi <st...@apache.org>.
On 5 Dec 2003, at 23:58, Rolf Kulemann wrote:

> 1.7.) Moving of docs.
> I have a question to this req. Stefano mentioned the moving of docs.
> What do you exactly mean? The need of a moving functionality depends on
> how a document is referenced via the repository interface. What is a
> *primary key* for a document to be retrieved? Have you already sth. in
> mind? I saw some discussion in cocoon-dev related to an URI like key?
> Maybe I misunderstood.

Be careful not to mix concerns. We are talking about the repository 
level. moving things at the repository level means to break contracts. 
Some repositories, for this very reason, forbid moving stuff around 
(CVS for example). But history shows that while moving is considered 
bad, you need it. Just like the delete key in your keyboard... you wish 
you could do without it, but hey, shit happens.

--
Stefano.

Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Sat, 2003-12-06 at 08:58, Rolf Kulemann wrote:
> 
> Ok, let me give it a try, but I'm new to Lenya and on an apprenticeship
> in the Lenya (and Coocon) community. I hope you all help me grow.
> 
> Lenya requirements for a content repository ordered by priority
> ---------------------------------------------------------------
> 
> High priority
> -------------
> 1.1) open/save document
> 1.2.) create collection of documents
> 1.3.) open and save collection of documents
> 1.4.) *simple* versioning (yes, I think it is high priority)
> 1.5.) Retrieve Meta data, so a very simple query only and no complex
> searches at the first step. I think Lenya depends somehow on a docs meta
> data and so I think it is high prio.
> 1.7.) Moving of docs. 
> I have a question to this req. Stefano mentioned the moving of docs.
> What do you exactly mean? The need of a moving functionality depends on
> how a document is referenced via the repository interface. What is a
> *primary key* for a document to be retrieved? Have you already sth. in
> mind? I saw some discussion in cocoon-dev related to an URI like key?
> Maybe I misunderstood.
> 
> Medium Priority
> ---------------
> 2.1.) Locking of docs. This is essential for concurrent actions on docs.

2.2.) Simple transction features. Like metioned in cocoon-dev by
Stefano, I can also imagine transactions make sense when saving doc
collections. 
Is an image a doc? I propose to use the term asset for all type of
objects in the repository. Alternative the term doc could also fit for
all objects. An Asset then can be aggregated composed by other assets.
Some assets are atomic like images sounds for example. Ok stop this
discussion here.

> 2.3.) If access control is a concern of the Repository I propose it to
> be reflected in the rep. API, because otherwise Lenya has to deal with
> it. This is an important decision.
> 
> Low Priority
> -------------
> 3.1.) Complex metadata queries
> 3.2.)  observation - add listeners to specific events in the repository 
>  based on both the type of event and on the location in the repository. (I have borrowed this from the cocoon-dev)
> 
> 
> I know this list is simple and primitive, but I think other people will enhance it.
> 
> Have a nice weekend.


-- 
Rolf Kulemann

Proof techniques #1: Proof by Induction.

This technique is used on equations with "_n" in them.  Induction
techniques are very popular, even the military used them.

SAMPLE: Proof of induction without proof of induction.

	We know it's true for _n equal to 1.  Now assume that it's true
for every natural number less than _n.  _N is arbitrary, so we can take _n
as large as we want.  If _n is sufficiently large, the case of _n+1 is
trivially equivalent, so the only important _n are _n less than _n.  We
can take _n = _n (from above), so it's true for _n+1 because it's just
about _n.
	QED.	(QED translates from the Latin as "So what?")


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Fri, 2003-12-05 at 20:12, Stefano Mazzocchi wrote:
> On 4 Dec 2003, at 05:03, Andreas Hartmann wrote:
> <snip/>
> My suggestion would be for lenya-dev to come up with a solid list of 
> functional requirements, listed by their order of importance, then have 
> cocoon-dev decice what is the best way to implement this in the cocoon 
> architecture so that everybody (lenya included) can benefit. 

Ok, let me give it a try, but I'm new to Lenya and on an apprenticeship
in the Lenya (and Coocon) community. I hope you all help me grow.

Lenya requirements for a content repository ordered by priority
---------------------------------------------------------------

High priority
-------------
1.1) open/save document
1.2.) create collection of documents
1.3.) open and save collection of documents
1.4.) *simple* versioning (yes, I think it is high priority)
1.5.) Retrieve Meta data, so a very simple query only and no complex
searches at the first step. I think Lenya depends somehow on a docs meta
data and so I think it is high prio.
1.7.) Moving of docs. 
I have a question to this req. Stefano mentioned the moving of docs.
What do you exactly mean? The need of a moving functionality depends on
how a document is referenced via the repository interface. What is a
*primary key* for a document to be retrieved? Have you already sth. in
mind? I saw some discussion in cocoon-dev related to an URI like key?
Maybe I misunderstood.

Medium Priority
---------------
2.1.) Locking of docs. This is essential for concurrent actions on docs.
2.2.) If access control is a concern of the Repository I propose it to
be reflected in the rep. API, because otherwise Lenya has to deal with
it. This is an important decision.

Low Priority
-------------
3.1.) Complex metadata queries
3.2.)  observation - add listeners to specific events in the repository 
 based on both the type of event and on the location in the repository. (I have borrowed this from the cocoon-dev)


I know this list is simple and primitive, but I think other people will enhance it.

Have a nice weekend.


-- 
Rolf Kulemann

Bubble Memory, n.:
	A derogatory term, usually referring to a person's
intelligence.  See also "vacuum tube".


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Stefano Mazzocchi <st...@apache.org>.
On 4 Dec 2003, at 05:03, Andreas Hartmann wrote:

> Hi Lenya developers,
>
> on the cocoon-dev mailing list there is a thread
> about converging the repository concept in Cocoon:
>
> http://marc.theaimsgroup.com/?t=107022316500003&r=1&w=2
>
> The basic idea is to define a repository API for Cocoon,
> at a more application-oriented level than, e.g., JCR.
> The API could be implemented for instance by a wrapper
> around JCR.
>
> Stefano invited the Lenya community to collect our
> ideas and requirements regarding the repository
> functionality. IMO we should seize this opportunity
> to influence this development and to increase the
> cooperation with the Cocoon community.
>
> The question is whether we should discuss this here
> or on cocoon-dev (I think the latter makes more sense).

My suggestion would be for lenya-dev to come up with a solid list of 
functional requirements, listed by their order of importance, then have 
cocoon-dev decice what is the best way to implement this in the cocoon 
architecture so that everybody (lenya included) can benefit. It 
separate concerns well and allows parallelization and non-lenya 
content-oriented projects to help as well.

So, for example:

-critical--------

   create/get/move/copy/delete documents and collections
   add/remove/list custom namespaced metadata to documents and 
collections
   query metadata

-planned for the future-----

  document versioning/rollback
  transactional observability

-nice to have but not critical---

  fulltext searches
  document symlinking

don't get to crazy with the last section ;-)

--
Stefano.

Re: [RFP] Repository requirements

Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann wrote:
[...]

> Workflow happens at the publication-specific operations
> layer:
> 
>     WorkflowInstance instance
>         = WorkflowFactory.buildInstance(document);
>     instance.invoke(event);

[...]

> It could also be handled inside the publication layer:
> 
>     document.invokeEvent(event);
> 
> but I don't know if this makes sense.

I think to answer this questions we have to
decide if workflow is an implicit feature of
a publication.

The advantages are:

- Code is moved from the publication-specific operations
   (PSO) layer to the publication layer. This makes it easier
   to write tasks.

- The PSO layer doesn't have to deal with getting workflow
   instances for documents.

- At the moment, there is a CMS-specific workflow engine
   wrapper. I'm not sure if this is the best practise. Maybe
   it would make more sense to access the workflow engine
   interface directly from the publication layer. This way,
   CMS-specific code would be reduced to the publication
   layer.

The disadvantages are:

- The publication API becomes more complicated.

At the moment, I don't think it's worth changing these
things.

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Andreas Hartmann <an...@apache.org>.
Rolf Kulemann wrote:

> 
>> > 3) attach metadata to documents (externally to them!!
>>
>>ATM metadata are stored inside the document
>>(I'm not quite sure how metadata for images etc.
>>are handled). Is it OK with us to use the repository
>>metadata concept? +1 from me.
> 
> +1
> The fact that that matadata is externally attached should be transparent
> to the client of the repository API.

Yes.

> Some additional thoughts and questions.
> 
> Andreas provided a nice ascii art for the Lenya cms architecture:
> 
> +----------------------------------------------+
> | Presentation Layer (Cocoon)                  |
> +----------------------+-----------------------+
> | Publication-specific |                       |
> | Operations Layer     |                       |
> +----------------------+-----------+           |
> | Publication Layer                |           |
> |                                  |           |
> |               +------------------+-----------+
> |               | Site structure management    |
> +---------------+------------------------------+
> | Filesystem                                   |
> +----------------------------------------------+
> 
> I think Filesystem should be repository?

Yes (see the "Designing the publication API" thread).

> Andreas: Where does the workflow and access control located in that
> architecture? Can you zoom the architecture a bit for me ?
> How is workflow and access control related to the repository?

ATM, access control happens in the Cocoon layer. Maybe it
would make sense to attach it to the publication layer ...
This would prevent the integrator from implementing
pub-specific operations which allow users to manipulate
documents they are not allowed to access.

Workflow happens at the publication-specific operations
layer:

     WorkflowInstance instance
         = WorkflowFactory.buildInstance(document);
     instance.invoke(event);

It's a little difficult to draw :)

 > +----------------------------------------------+
 > | Presentation Layer (Cocoon)                  |
 > +----------------------+-----------------------+ +----------+
 > | Publication-specific |.........................| Workflow |
 > | Operations Layer     |                         | Engine   |
 > +----------------------+-----------+           | +----------+
 > | Publication Layer                |           |
 > |                                  |           |
 > |               +------------------+-----------+
 > |               | Site structure management    |
 > +---------------+------------------------------+
 > | Repository Layer                             |
 > +----------------------------------------------+

It could also be handled inside the publication layer:

     document.invokeEvent(event);

but I don't know if this makes sense.

Thanks for your comments,
-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Rolf Kulemann <ma...@rolf-kulemann.com>.
On Fri, 2003-12-05 at 11:02, Andreas Hartmann wrote:
<snip>
>  > 1) open/save document
Sure +1.

> 
>  > 2) create collection of documents

If a document can be any type of asset i.e. images, sound, xml +1.

> 
> I recently introduced the collection concept in the
> publication API (o.a.l.c.publication.Collection).
> I think it would make sense to support the visitor
> pattern, but this is has to be implemented in the
> publication API anyway (the client wants to visit
> documents and not repository ressources).
+1
> 
>  > 3) attach metadata to documents (externally to them!!
> 
> ATM metadata are stored inside the document
> (I'm not quite sure how metadata for images etc.
> are handled). Is it OK with us to use the repository
> metadata concept? +1 from me.

+1
The fact that that matadata is externally attached should be transparent
to the client of the repository API.

> 
>  > 4) query the repository against document metadata

An OAI interface should be provided for the rep, but of course this it
not important in the first step. Remember DSpace also meets the
requirements discussed to this point.

> 
>  > 5) versioning (autoversioning on saving and version update)

+1. This is essential.

> 
> I guess we need at least the same versioning features
> as we have now. Could someone summarize these? Are we
> aware of further versioning requirements?

Dunno.


Some additional thoughts and questions.

Andreas provided a nice ascii art for the Lenya cms architecture:

+----------------------------------------------+
| Presentation Layer (Cocoon)                  |
+----------------------+-----------------------+
| Publication-specific |                       |
| Operations Layer     |                       |
+----------------------+-----------+           |
| Publication Layer                |           |
|                                  |           |
|               +------------------+-----------+
|               | Site structure management    |
+---------------+------------------------------+
| Filesystem                                   |
+----------------------------------------------+

I think Filesystem should be repository?
Andreas: Where does the workflow and access control located in that
architecture? Can you zoom the architecture a bit for me ?
How is workflow and access control related to the repository?


-- 
Rolf Kulemann

Don't take life too seriously -- you'll never get out of it alive.


PGP/GPG public key:
	 http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6B4EA7EA


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org


Re: [RFP] Repository requirements

Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann wrote:

> on the cocoon-dev mailing list there is a thread
> about converging the repository concept in Cocoon:

OK, I'm starting with some thoughts.
Stefano's basic functional requirements are:

 > 1) open/save document

 > 2) create collection of documents

I recently introduced the collection concept in the
publication API (o.a.l.c.publication.Collection).
I think it would make sense to support the visitor
pattern, but this is has to be implemented in the
publication API anyway (the client wants to visit
documents and not repository ressources).

 > 3) attach metadata to documents (externally to them!!)

ATM metadata are stored inside the document
(I'm not quite sure how metadata for images etc.
are handled). Is it OK with us to use the repository
metadata concept? +1 from me.

 > 4) query the repository against document metadata

 > 5) versioning (autoversioning on saving and version update)

I guess we need at least the same versioning features
as we have now. Could someone summarize these? Are we
aware of further versioning requirements?

-- Andreas


---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org