>> A great part of qi4j's vision is about components and their reuse.
>> But what about finding the component, which fits best to the developers
>> needs (given that the future will bring us lots of those reusable
>> components)?
>
> Well, there is a library functionality to "express" an entire
> application as an RDF network graph. All the way from the Application
> down to the methods in fragments. The long term idea is that this RDF
> is published on RDF search servers and tools can query for all kinds
> of stuff.
My knowledge about this RDF library functionality is limited to the
information, which was published in this list previously.
So far as I understood is this RDF stuff a kind of introspection tool
which can be used at application runtime, i.e. the components have to be
at least assembled (if not instantiated), unless it's possible to dig in
to meta-information which is provided from the runtime. [That's my
current picture of how it works, correct me if I'm totally wrong]
What I meant is some kinde of 'static' analysis on the physical package
level (the jar) instead of performing it on the qi4j specific packaging
levels (module, layer) which are application specific and only available
at runtime.
And what my post was mainly about, attaching <em>additional</em> meta
information to components in a <em>standard</em> way. Let's say somebody
designed an interface for a tax calculation service and want's to
provide some tags for it before 'publishing':
@Tag ( { "domain:financial" , "domain:tax", "country:DE" }
interface TaxCalculationService {
...
}
Given that and some appropriate RDF generation + RDF search server
feeding, someone could find this service interface with the keywords
"financial && DE". That's not possible without this additional tagging.
So it's all about 'semantic qi4j' from a component consumer view.
Perhaps the easiest way is not an annotation (like in the sample above),
but an explicit RDF for a component using qi4j specific vocabulary?
Georg
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
