Name
|
|
|
Description
| |
---|---|---|---|---|
| ||||
|
| - | ||
|
README.html
| 2009-09-10 20:07 | 4.6K | |
|
build.xml
| 2009-01-25 04:52 | 10K | |
|
build/
| 2009-04-22 16:18 | - | |
|
| 2009-04-22 16:15 | 1.0K | |
|
diffmk.xml
| 2007-06-05 18:10 | 4.9K | |
|
epr-note.html
| 2009-06-26 17:05 | 52K | |
|
extra/
| 2009-04-22 16:18 | - | |
namespace-if-source.xhtml
| 2007-06-05 18:10 | 2.3K | ||
namespace-source.xhtml
| 2008-01-17 21:21 | 2.3K | ||
participants.rdf
| 2009-04-22 11:19 | 1.3K | ||
previous-participants.rdf
| 2009-04-22 11:19 | 2.0K | ||
|
sample-model-source.xsd
| 2008-04-16 07:16 | 6.5K | |
sml-if-source.xml
| 2009-04-22 11:19 | 89K | ||
sml-if-source.xsd
| 2009-01-28 19:24 | 8.8K | ||
sml-source.xml
| 2009-04-22 11:19 | 153K | ||
|
sml-source.xsd
| 2009-04-17 22:42 | 6.0K | |
tests/
| 2009-10-13 18:03 | - | ||
|
tools/
| 2007-07-10 15:56 | - | |
xlink-note.html
| 2009-10-13 18:03 | 22K | ||
xmlspec.dtd
| 2007-06-05 18:10 | 80K | ||
xsl/
| 2009-04-22 11:17 | - | ||
|
Look
at
the
Eclipse
documentation
to
configure
your
editing
tool.
SML
XLink
Reference
Scheme
is
resolved
using
uses
the
following
steps:
public
CVS
Repository
(dev.w3.org).
You
want
to
check
out
2007/xml/sml
.
Let
U
be
the
URI
reference
that
is
the
content
of
xlink:href
.
Let
S
be
the
specification
that
defines
the
URI
scheme
of
U
.
An
XML
document
D
is
obtained
as
follows:
sml-source.xml
:
contains
the
main
source
for
SML
1.1.
If
U
is
a
same-document
reference,
then
D
is
the
document
containing
sml-if-source.xml
:
contains
the
main
source
for
SML
reference.
Otherwise,
D
is
determined
as
follows:
IF
1.1.
If
U
is
a
relative
reference,
then
let
U′
be
the
result
of
transforming
U
to
form
an
(absolute)
URI
using
the
[base
URI]
property
[
XML
Infoset
]
of
*.xsd
:
contains
the
XML
Schema
documents
associated
with
SML
reference
element
as
the
base
URI.
Otherwise,
let
U′
be
U
(i.e.,
the
URI
reference
itself).
The
computation
of
the
[base
URI]
property
is
implementation-defined.
and
SMLF
IF
Dereference
U′
as
defined
in
S
.
If
the
document
targeted
common.dtd
:
contains
values
used
by
U′
is
in
the
current
SML
model,
then
D
is
that
document.
Otherwise,
files
above.
Modified
this
file
if
you're
going
to
publish
a
public
version
of
the
document
is
not
in
on
/TR.
namespace*.xhtml
:
contains
the
current
namespace
documents
associated
with
SML
model,
then
the
and
SML
XLink
Reference
Scheme
instance
is
unresolved
(and
D
has
no
value).
IF.
Note:
If
*.rdf
:
contains
the
retrieved
object
is
not
list
of
XML
media
type
or
if
it
is
not
well-formed
XML
then,
per
the
definition
current
and
previous
participants
in
section
2.2
of
[
SML
],
that
object
is
not
a
document.
In
this
case,
the
SML
reference
scheme
instance
is
unresolved.
group.
xmlspec.dtd
:
the
DTD
for
xmlspec
documents,
avoid
touching
it.
If
no
fragment
component
extra/
:
This
directory
is
present
in
U
,
the
SML
XLink
Reference
Scheme
instance
resolves
to
used
during
the
root
element
building
of
D
.
the
specification,
you
can
safely
ignore
it.
xsl/
:
This
directory
contains
various
XSL
files
used
during
the
transformation
If
a
fragment
component
build/
:
This
directory
is
present
in
U
,
then
where
the
appropriate
case
among
final
documents
are.
build/ns
:
This
directory
is
where
the
following
applies:
final
namespace
and
schema
documents
are.
tools/
:
This
directory
contains
various
jar
files
used
by
ant.
Don't
touch.
If
build.xml
:
the
fragment
component
complies
ant
file.
Works
well
with
ant
1.7
at
least.
Most
of
the
smlxpath1()
XPointer
scheme
syntax,
then
time,
you
will
use
the
reference
target
is
obtained
by
applying
task
"
html
".
It
takes
the
fragment
component
to
D
,
as
defined
in
section
4.3.1.1
of
[
SML
].
If
sources
and
produces
the
fragment
component
complies
with
final
documents
(
build/sml.html
and
build/sml-if.html
).
The
"
main
"
task
does
the
shorthand
pointer
syntax,
then
same
except
that
it
updates
the
appropriate
case
among
acknowledgments
in
the
following
applies:
process.
The
"
clean
"
task
will
remove
all
generated
contents.
If
a
target
T
Note:
you
might
see
some
warnings,
generated
by
saxon,
indicating
you're
applying
XSLT
1.0
style
sheets
with
an
XSLT
2
engine.
You
can
be
identified
safely
ignore
those
here.
The transformation goes through several stages:
sml-source.xml
and
sml-if-source.xml
*.xsd
into
their
final
form
in
build/ns/*.xsd
(add
copyright
information,
remove
the
common.dtd
,
...)
sml-source.xml
and
sml-if-source.xml
into
XML
files.
It
applies
xinclude
and
a
build/sml.html
and
build/sml-if.html
).
The
following
example
illustrates
For
an
instance
of
the
XLink
Reference
Scheme:
editors'
copy:
you
want
to
check
in
sml-source.xml
,
sml-if-source.xml
,
*.xsd
,
build/sml.html
,
and
build/sml-if.html
.
Here,
the
EnrolledCourse
element
is
For
a
valid
instance
of
the
SML
XLink
Reference
Scheme
since
the
content
of
xlink:type
is
simple
and
the
content
of
xlink:href
is
of
type
xs:anyURI
.
It
is
also
an
SML
reference
since
the
content
of
sml:ref
is
the
string
true
;
publication:
you
want
to
check
in
particular,
it
is
a
non-null
SML
reference
since
the
content
of
sml:nilref
is
the
string
false
.
The
target
of
the
reference
is
the
root
element
of
the
XML
document
obtained
by
dereferencing
http://www.university.example.org/phy101.xml
.
sml-source.xml
,
sml-if-source.xml
,
*.xsd
,
and
*.rdf
.
First,
update
common.dtd
.
The
following
example
illustrates
an
instance
of
XLink
Reference
Scheme
where
the
content
of
xlink:href
has
a
fragment
component
that
follows
the
syntax
of
the
smlxpath1()
XPointer
scheme:
section
should
be
updated
and
UNcommented:
<!-- <!ENTITY draft.year "2007"> <!ENTITY draft.month "July"> <!ENTITY draft.mm "07"> <!ENTITY draft.day "4"> <!ENTITY draft.dd "04"> <!ENTITY status "wd"> -->
In
Then,
use
the
above
example,
task
"
publication
".
This
will
create
build/sml-specification.zip
and
build/sml-if-specification.zip
.
Check
the
target
trace
of
the
reference
is
the
element
identified
by
the
path
/u:Courses/u:Course[u:Name='PHY101']
in
the
XML
document
obtained
by
dereferencing
http://www.university.example.org/physics.xml
.
A.
References
[Back
to
Contents]
[RFC-3986]
Uniform
Resource
Identifier
(URI):
Generic
Syntax
,
T.
Berners-Lee,
R.
Fielding,
L.
Masinter,
Authors.
Internet
Engineering
Task
Force,
January
2005.
Available
at
http://www.ietf.org/rfc/rfc3986.txt.
[SML]
Service
Modeling
Language,
Version
1.1
,
Bhalchandra
Pandit,
Valentina
Popescu,
Virginia
Smith,
Editors.
World
Wide
Web
Consortium,
12
May
2009.
This
version
of
ant
process
closely
since
the
Service
Modeling
Language
Recommendation
is
available
at
http://www.w3.org/TR/2009/REC-sml-20090512/.
task
applies
several
tests
and
may
tell
you
if
something
could
need
your
attention.
The
latest
version
of
Service
Modeling
Language,
Version
1.1
is
available
at
http://www.w3.org/TR/sml/.
[SML-IF]
Service
Modeling
Language
Interchange
Format
Version
1.1
,
Bhalchandra
Pandit,
Valentina
Popescu,
Virginia
Smith,
Editors.
World
Wide
Web
Consortium,
12
May
2009.
This
version
of
zip
files
contains
the
Service
Modeling
Language
Interchange
Format
Recommendation
is
available
at
http://www.w3.org/TR/2009/REC-sml-if-20090512/.
The
latest
version
of
Service
Modeling
Language
Interchange
Format
Version
1.1
is
available
at
http://www.w3.org/TR/sml-if/
[XLink]
HTML
documents,
their
XML
Linking
Language
(XLink)
Version
1.0
,
Steve
DeRose,
Eve
Maler,
David
Orchard,
Editors.
World
Wide
Web
Consortium,
27
June
2001.
This
version
of
versions,
the
XLink
Recommendation
is
available
at
http://www.w3.org/TR/2001/REC-xlink-20010627/.
The
latest
version
of
XLink
is
available
at
http://www.w3.org/TR/xlink/.
[XML]
Extensible
Markup
Language
(XML)
1.0
(Fourth
Edition)
,
T.
Bray,
J.
Paoli,
C.
M.
Sperberg-McQueen,
namespace
documents
and
E.
Maler,
Editors.
World
Wide
Web
Consortium,
10
February
1998,
revised
16
August
2006.
The
edition
cited
(http://www.w3.org/TR/2006/REC-xml-20060816)
was
the
one
current
at
the
date
of
publication
of
Service
Modeling
Language
[
SML
]
as
schema
documents.
Note
that
a
Candidate
Recommendation.
The
latest
version
lot
of
XML
1.0
is
available
at
http://www.w3.org/TR/xml/
.
Implementations
may
follow
the
edition
cited
and/or
any
later
edition(s);
it
is
implementation-defined
which
editions
tests
are
supported
by
an
implementation.
[XML-Infoset]
XML
Information
Set
(Second
Edition)
,
John
Cowan,
Richard
Tobin,
Editors.
World
Wide
Web
Consortium,
4
February
2004.
This
version
of
done
on
the
XML
Information
Set
Recommendation
is
available
at
http://www.w3.org/TR/2004/REC-xml-infoset-20040204/.
The
latest
version
of
XML
Information
Set
is
available
at
http://www.w3.org/TR/xml-infoset/.
[XML-Schema]
The
XML
Schema
definition
language
(XSD)
is
specified
documents,
in
particular
the
following
Recommendations
from
the
Word
Wide
Web
Consortium:
[XSD-Structures]
XML
Schema
Part
1:
Structures
Second
Edition
,
Henry
S.
Thompson,
David
Beech,
Murray
Maloney,
Noah
Mendelsohn,
Editors.
World
Wide
Web
Consortium,
2
May
2001,
revised
28
October
2004.
This
version
of
the
XML
Schema
Part
1
Recommendation
is
available
at
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/.
The
latest
version
of
XML
Schema
1.0
Part
1
is
available
at
http://www.w3.org/TR/xmlschema-1/.
[XSD-Datatypes]
XML
Schema
Part
2:
Datatypes
Second
Edition
,
P.
Byron
pubrules
checker
.
I
should
take
unzip
in
a
temporary
web
location
and
A.
Malhotra,
Editors.
World
Wide
Web
Consortium,
2
May
2001,
revised
28
October
2004.
This
version
of
have
the
XML
Schema
Part
2
Recommendation
is
available
at
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/.
pubrules
checker
check
that
online
document.
The
latest
version
of
XML
Schema
1.0
Part
2
is
available
at
http://www.w3.org/TR/xmlschema-2/.
[XPointer]
XPointer
Framework
,
P.
Grosso,
E.
Maler,
J.
Marsh,
webmaster
will
run
the
pubrules
checker
in
any
case
and
N.
Walsh,
Editors.
World
Wide
Web
Consortium,
25
March
2003.
This
version
of
will
refuse
to
publish
until
the
XPointer
Framework
Recommendation
is
http://www.w3.org/TR/2003/REC-xptr-framework-20030325/
The
latest
version
of
XPointer
Framework
is
available
at
available
at
http://www.w3.org/TR/xptr-framework/.
problems
have
been
fixed.