On 2018-10-08T13:16:25 +0000 "BJ Hargrave" <hargr...@us.ibm.com> wrote:
> Did you try > > <?xml version='1.0' encoding='UTF-8'?> > <repo:repository xmlns:repo="http://www.osgi.org/xmlns/repository/v1.0.0"; > name="example"> > <resource> > <capability namespace="osgi.identity"> > <attribute name="osgi.identity" > value="org.apache.felix.framework"/> > <attribute name="type" > value="osgi.bundle"/> > <attribute name="version" > value="6.0.1" > type="Version"/> > </capability> > </resource> > </repo:repository> > > Note the use of the local name on the main repository element (I picked > "repo" for my example). Hm, that validates. That's somewhat odd... What is the reasoning behind having resources, capabilities, and attributes effectively live in a different namespace? I have some interest in, for example, accepting documents that have a single <resource> root element, and I'd like to validate those against the schema. That doesn't seem possible. -- Mark Raynsford | http://www.io7m.com
pgp0zlOe75CAF.pgp
Description: OpenPGP digital signature
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
