Mark Diggory wrote:
> [snip]
>
> Based on your comments to Neil and on comments Stefano and others
> have made about maybe refactoring Longwell into a "Service" and
> separate "Clients". I'd say the important use-case for those of us
> who are already running java enterprise / web-applications is that we
> would like to have flexibility and configurability on the server side
> as much as possible. To be able to combine data-sets in one server
> and deliver multiple client configurations on that combined data.
> I.E. that managing the data and delivering a User experience on that
> are activities performed by separate but overlapping roles.
>
I hear you :) And I think "server-side" is where Stefano and Ryan have a
lot more experience than I do. I'm more focused on integration on the
client side, which is perhaps less mature than integration on the server
side.
>> Facets found in exhibits can actually be a lot more complicated than
>> facets in Longwell instances. In Longwell, a facet can only be defined
>> by a property (an RDF predicate). In Exhibit, it can be defined by an
>> Exhibit expression.
>>
> That would be a very powerful capability and one I wish was present
> in Longwell, It would not only allow us greater control the inclusion
> of fields into a facet (and thus possibly improved performance) but
> also would allow us to make conditional decisions about the inclusion
> of a value based on the state of of items that have > one degree of
> separation. To me this means less need to "shape" or "dumb down" the
> RDF going into the Longwell triple-store so that is renders in facets
> appropriately.
>
Yup, it goes along with my little silly slogan
your data, your mess, your business
meaning that however you model your data, we can make our tools adapt to
your data model. That's easier said than done. Exhibit does pretty well
on that front since we're not trying to scale. But it's not the same
story for Longwell (and Backstage).
> [snip]
> I hope you can glean from what I've said above, that what we are
> working to accomplish is much more than theme and branding HTML/CSS,
> we are actually trying to give the user greater ability to explore a
> metadata space that is managed by more than one role...
>
> For instance, with the following roles on a Digital Object (Admin,
> Manager, Submitter and Viewer) We may have one "Item" with statements
> made by the different users in those different roles, I.E. Users or
> Submitters may make a "Comment" about the "Item", while Managers and
> Admin would be able to change the "Item" more directly. And even
> then, we might retain a "History" of those changes that did happen to
> the "Item".
>
> After all these roles are creating statements in their various
> domains. We then need a expose the whole space in a way that can be
> both explored by both user choice and also have controlled access by
> users rights in the system.
>
As a seasoned professor here loves to say, "one bottomless pit at a
time!" :-) I think the most important thing now is to figure out the
order in which you explore these bottomless pits. What's your plan?
David
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
