Yes, this would make perfectly sense!
Only the version would be within a separated element, for instance
<groupId>org.oasis-open</groupId>
<artifactId>OpenDocument</artifactId>
<version>1.2-20110929-os</version>
I would have added the date to be certain the ordering works, see http://docs.codehaus.org/display/MAVEN/Versioning
- Svante
On 22.02.2012 14:30, wrote:
I see that the OOXML
versions were uploaded
with coordinates like:
<groupId>org.apache.poi</groupId>
<artifactId>ooxml-schemas</artifactId>
Would it make sense for this to
be consistent
across OASIS, like:
<groupId>org.oasis-open</groupId>
<artifactId>OpenDocument-v1.2</artifactId>
In other words, use the OASIS
naming
scheme for the artifactId. <versionID> would then have
the
stage identifier from the spec, like "os" for the OASIS Standard
version
-Rob
<> wrote on
02/22/2012
08:11:09 AM:
> From: Svante Schubert <>
> To: Robin Cover
<>,
> Cc: ODF TC List
<>
> Date: 02/22/2012 08:12 AM
> Subject: [office] ODF schema within public
source
repositories
> Sent by:
<>
>
> Hi Robin,
>
> I would like to add the ODF 1.0, 1.1 and 1.2 schema to a
public
> Maven repositories for the build process of the Apache
ODF Toolkit
> (incubating) project [1], similar as it was done before
for OOXML
schema [2]
> for the Apache POI project [3].
> The schema are being used for code generation. The
advantage to copy
> the schema to the trusted Maven repository is, the schema
would be
> downloaded only once by the Maven build tool, placed in a
trusted
> local environment and not downloaded with every build.
This would
> allow to build without Internet (e.g. in Café, Train,
Airport, etc.).
>
> Is there any legal process, I have to conduct with OASIS?
>
> Thanks in advance,
> Svante
>
> [1] http://incubator.apache.org/odftoolkit/
> [2] https://maven.nuxeo.org/nexus/content/repositories/public/org/
> apache/poi/ooxml-schemas/
> [3] http://poi.apache.org/
